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

@vanderbreye, it's created on the fly :). Have a look at lines #677-718 and the function makeTable() (lines 60-85) in ProcessMediaManager.js

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

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   1 member

  • Similar Content

    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
×
×
  • Create New...