Jump to content

Recommended Posts

5 minutes ago, Rudy said:

Downgraded my site to 2.8.35 and still experienced the issue. A note, the MediaManager field is called inside a repeater, if that makes any different.

Update: Tested MediaManager on its own (without repeater) and the modal window works fine.

@Rudy. Sorry, my bad. ProcessWire 2.8 and 3.x are one and the same thing, save for namespacing. What I meant was please test in any PW 2.5 up to 2.7.  Oops, didn't take note that you were in a repeater. There have been other bugs reported about MM in repeaters in PW 3.x. So, I will file this under that, but just in case, if you can, please test in a PW pre-2.8 and let me know, just to be sure it's not an environment issue.

Link to post
Share on other sites
55 minutes ago, Michael van Laar said:

I know, images differ from the other media types a little bit.

......

@Michael van Laar...sorry if I sounded a little bit blunt...Just wading through a ton of 'todos' :)...so short on time...Let's hear if there are other ideas on how this could be achieved...

Link to post
Share on other sites

The issue is with repeater's ajax dynamic loading. It works fine when ajax option is turned off. If you can find the hook that gets called after the add new repeater child is clicked, you can probably get it to initialize the magnific call after that click.

I will leave it for now since there is a workaround. I know you've got many things on your checklist ;-)

Thx

Rudy

  • Like 3
Link to post
Share on other sites
2 minutes ago, Rudy said:

The issue is with repeater's ajax dynamic loading. It works fine when ajax option is turned off. If you can find the hook that gets called after the add new repeater child is clicked, you can probably get it to initialize the magnific call after that click.

Thanks for pinning this down Rudy.

  • Like 2
Link to post
Share on other sites
1 hour ago, kongondo said:

Thanks for pinning this down Rudy.

This function here listens for repeater's events and initialize jQuery Magnific inside a repeater. Tested on my site only though. EDIT: Also need to check if repeater is being used or not.

// magnific
$(document).ready(function(){

	// If repeater field 
	if ( $('.InputfieldRepeaterAddItem').length ) {
		//console.log('Repeater is being used');
		$(document).on('click opened openReady repeateradd', function(){
			initMagnificPopup();
		});
	} else {
		//console.log('Repeater is NOT being used');
		initMagnificPopup();
	}

});//end jquery

// Initialize Magnific
function initMagnificPopup() {
	$('a.add_media').magnificPopup({
		type:'iframe',
		callbacks: {
			close: function() {
			// will fire when popup is closed
				window.location.reload(true);// force parent page refresh on modal close
			}
		}

	});
}

 

Edited by Rudy
Add conditional to check for repeater usage
  • Like 2
Link to post
Share on other sites

Hiya, I'm looking forward to seeing the newest version of Media Manager with the upload directly from CKEditor feature. 

Having used the module on my site for a few weeks, it's becoming clear that with the number of images I'm using (it's a document library so there are hundreds and hundreds already), it's becoming unmanageable to use Media Manager, even with the ability to filter by tags. There are a number of different people using the system so it's chaos at the moment.

With this in mind, would it be possible to add the ability to create folders for various groups of images? That way people could upload to a folder specific to their document. Obviously they would still be able to filter globally by tags or titles or whatever, but it would make the starting point so much easier to manage.

Link to post
Share on other sites

Hi @spacemonkey95,

I am not sure I follow. Tags are specifically what you need to group media. Creating subfolders (aka sub-media pages) would essentially mean a re-write of the module (unless am not thinking this through clearly). I also don't understand what you mean by starting point? Maybe if you could (graphically, if possible) explain your work flow? Thanks.

On the other hand, if what you need is the ability for users to be able to only see the media they uploaded, that I can add easily (in fact I have already tested and it works fine). Basically we would use 'created_users_id' to filter out other users' media. I could add this to the upcoming settings.

Link to post
Share on other sites
2 hours ago, kongondo said:

On the other hand, if what you need is the ability for users to be able to only see the media they uploaded, that I can add easily (in fact I have already tested and it works fine). Basically we would use 'created_users_id' to filter out other users' media. I could add this to the upcoming settings.

+1 for this capability

Link to post
Share on other sites

Hi @kongondo

I wanted to ask if its possible to have this list view change for the media manager fields also for the media manager process page? My Customer wants to see the filename of every image/file without clicking on it.

And have you thought about integrating this fixed filters(like Lister Pro) for the media manager? My customer needs them since it's a big company with many workers, and it would be just time consuming to build the filters every time when the user is logged in. 

Greetings Orkun

  • Like 1
Link to post
Share on other sites
24 minutes ago, Nukro said:

Hi @kongondo

I wanted to ask if its possible to have this list view change for the media manager fields also for the media manager process page? My Customer wants to see the filename of every image/file without clicking on it.

And have you thought about integrating this fixed filters(like Lister Pro) for the media manager? My customer needs them since it's a big company with many workers, and it would be just time consuming to build the filters every time when the user is logged in. 

Greetings Orkun

@Nukro

 

1. List view: Yes, that's on my todo list right here

2. I need to dispense with version 7 first. Then I will look into if/how I can integrate custom filters

  • Like 2
Link to post
Share on other sites

Hey kongodo!
I still don't get how the form for the variation-description is rendered..

i need to implement a multilanguage-solution, like i did for the original image...:

 

$languages = $this->wire('languages');
            $this->wire('user')->language = $languages->get("default");
                        foreach($languages as $lang) {
            $this->wire('user')->language = $lang;
                $this->wire('user')->language = $languages->get($lang->id);
                            $out .= '<label for="media_description_'.$lang->id . $mediaID . '">' .$lang->title . '</label>';
                            $out .= '<textarea class="lang" id="media_description_'.$lang->id . $mediaID . '" name="media_description_'.$lang->id.'">' . $m->description . '</textarea>';
            }
            

 

but i have no clue...

Edited by kongondo
code formatting
Link to post
Share on other sites

haha. WTF. ok! :) 

 for now i simply copy-from-image-media  and overwrite the description for variations on save, which works... but it would be REALLY great, to have native multilanguage-support in the image-description (like it is in the core), i think. maybe, its something for the roadmap.

beside that, it's a pretty solid work!

 

  • Like 1
Link to post
Share on other sites

Hi @kongondo

Could you say a period when you release the version 7 of the media manager? My Customer urges me, that he wants to start uploading images. I think it shouldn't be a problem to update the module when there are uploaded images?  

Greetings Orkun

Link to post
Share on other sites

@vanderbreye. Of course :). Remember this is ProcessWire..., the ProcessWire.

// This will search even in image variations
$media = $pages->find("template=media-manager-image, media_manager_image.description%=blue");
#echo count($media);
// first() in our case is always the main image/media.
foreach ($media as $m) echo $m->title . ': ' . $m->media_manager_image->first()->description . '<br>';

 

Link to post
Share on other sites
2 hours ago, Rudy said:

@kongondo, not sure if this has been requested in the past...

It would be nice to be able to edit the title, description and tags once media have been selected. 

Thx

Rudy

Rudy, am totally clueless about what you mean :). Please clarify. Selected where? In Inputfield/FieldtypeMediaManager? 

Link to post
Share on other sites

Media Manager version 007  (released (23/11/2016))

Happy to announce the latest release of Media Manager. Download via your purchase link.

Changelog

  1. Multi-tagging: Added to the list of actions to apply to selected media. Tick the checkbox to replace rather than append to existing tags. 'Un-tagging' also available in the list of actions.
  2. Uploading now possible when in CKEditor context.
  3. Settings moved to own menu item.
  4. New settings added: Media title format; Handling duplicate media (all 4 media types); Display current users' media only; Media sorting + sort order
  5. Replace/Rename/Skip Duplicate media: When new media loaded and a duplicate is found in the library, this setting tells MM what to do. If using 'Replace' mode, existing tags and descriptions are preserved. There is also a setting to preserve or delete existing image media variations. @note: Might need a couple of refreshes (browser and/or MM before replacement media is shown).
  6. Media Sorting: Set via settings (@see #4).
  7. Live Media Sorting: In your Media Manager Library, select sort criteria (dropdown select) and sort order (checkbox). These override the sort settings in 'Settings' (@see #3).
  8. List and Grid View: Click on respective icons to switch to list versus grid view. In list-view, the current media (displayed on the right pane) remains in view as you scroll the page. @note: currently there is a bug where your media image will remain fixed at the top of the window when you scroll back up in cases where it is taller than your monitor. Please see this post.
  9. Insert Link and Insert Image: Streamlined insert link and insert image in CKEditor. MMLink and MMImage plugins are now obsolete! Go ahead and delete them please. Instead, we use and extend ProcessWire's inbuilt PWImage and PWLink. 
  10. Code refactoring, bug fixes, CSS fixes.

@note:

As previously announced, this version is still not yet certified as compatible with ProcessWire 2.8 and 3.X. This means the repeater matrix bugs will still be present. Next version of MM will be compatible with these versions of PW.

media-manager-insert-link-ckeditor.png

media-manager-insert-image-ckeditor.png

media-manager-insert-image-replace-ckeditor.png

media-manager-multi-tagging.gif

media-manager-media-replace.gif

media-manager-list-view.gif

media-manager-live-sort.gif

  • Like 5
Link to post
Share on other sites

Thank you for the great update, kongondo. I will try the new version out very soon.

I use Media Manager extensively on the project I'm currently working on and trying to do - let's call it - context-based image descriptions.

I have many images that will be displayed on different product pages in a slideshow. So the same image/file will be used in different contexts and need a different description depending on the page.

The reason is that multiple products are shown on the same image.

  • a) The obvious solution would be uploading the image multiple times as needed and give them different descriptions, but I really don't like this solution since a visitor would have to download more data than needed. That's not really optimized since the project already uses responsive images and lazy loading etc. yadda yadda ;-).
     
  • b) I thought about using a repeater, but I can't use one since the site is already running on ProcessWire 3.0 and Media Manager isn't working in Processwire 3.0 repeater fields. If there would be a quick fix, I'll bet Francis would have included the fix in the latest update.
     
  • c) Maybe there is another way. Any suggestions?


Thank you so much.

Regards

Link to post
Share on other sites

@kongondo

How do I have to update the Media Manager? Just overwrite the whole folder with the new one? It shouldn't affect any media manager fields that are assigned to templates or other related stuff with the media manager? Do I have to pay attention to some steps before replacing the old module folder with the new one? I just want to be careful and I dont want to break anything. :)

Greetings

Orkun

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
×
×
  • Create New...