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.

Share this post


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...

Share this post


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

Share this post


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

Share this post


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

Share this post


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.

Share this post


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.

Share this post


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

Share this post


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

Share this post


Link to post
Share on other sites

+1 for the feature requests above. I'm not yet a happy Media Manager owner, but it is highly probable that one day I will be :)  

  • Like 1

Share this post


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

Share this post


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

Share this post


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

Share this post


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

Share this post


Link to post
Share on other sites

@Nukro

 I am hoping next week, or the week after at most. Your client can go ahead and upload images. Updating should not affect existing media.

Share this post


Link to post
Share on other sites

:) sounds good!
one question: is it somehow possible to search for image-descriptions through $pages->find("mm_image%=asmallpartofdescription") somehow?

i would like to get my descriptions available in my general page search..

 

Share this post


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>';

 

Share this post


Link to post
Share on other sites

@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

Share this post


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? 

Share this post


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

Share this post


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

Share this post


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

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...