Jump to content

Recommended Posts

1 hour ago, Rudy said:

I am using Reno theme with Lightwire CK Editor theme. The MMImage and MMLink icons did not appear (see screenshot)

AFAIK it's a CSS issue, the LightWire theme hides the original icons and replaces them with its own icons, but unfortunately it hasn't got icons for third party plugins. To display them, use !important for the icons, at least that's why I've done in AdminOnSteroids module.

  • Like 2

Share this post


Link to post
Share on other sites

@kongondo

@adrian

When I change the code from the WireUpload::validateFilename method like this, it doesn't add any underscores more:

//$value = $this->wire('sanitizer')->filename($value, Sanitizer::translate); 
$value = $this->wire('sanitizer')->filename($value); // removing Sanitizer::translate

But I don't know how big this affects other code areas of ProcessWire. Do you know an other way how i could turn off adding of underscores to the filename?

Share this post


Link to post
Share on other sites

Hi @Rudy,

Glad that you are liking Media Manager. I have not used that theme before but will look into it. However, it seems @tpr has nailed down the issue to CSS. If that's true, don't know how to get around that since MM plugins don't come with their own CSS files.

Share this post


Link to post
Share on other sites

@Nukro

Changing core files is never recommended. Have you tried to play around with the settings in the module InputfieldPageName as stated in the $sanitizer docs (please see below)? Does that help? That core module is found at /your-pw-admin/module/edit?name=InputfieldPageName

 

$beautify (optional) bool or int

Should be true when creating a file's name for the first time. Default is false. You may also specify Sanitizer::translate (or number 2) for the $beautify param, which will make it translate letters based on the InputfieldPageName custom config settings.

 

 

Share this post


Link to post
Share on other sites

This is what I was using for the oEmbed plugin:

.cke_top .cke_button_icon.cke_button__oembed_icon {
  background-image: url('CKE/plugins/oembed/icons/oembed.png') !important;
}

 

  • Like 1

Share this post


Link to post
Share on other sites

 

Somehow the InputfieldPageName settings doesn't have any effect on the filename of images (i changed "ö=o" to "ö=owww" to test and it only affected the pagename when creating new pages). Perhaps I should start a new topic since this isn't a Media Manager issue furthermore it is a pw-general issue (I know it isn't really an issue since its just validating the filename, but it still adds underscores when using umlauts, which i think is a issue, since it is nowhere declared how i can change this behavior) . Sorry for hijacking this thread Mate. But still thanks for your help @kongondo. :)

Share this post


Link to post
Share on other sites

Are you sure you have Multi-byte string support compiled with PHP (mbstring)?

Share this post


Link to post
Share on other sites

Hi @kongondo

I have a couple of Questions:

1. Is it possible to save the filter interface configuration (like in ListerPro)?

2. Filtering tags by words (it should ignore the order) doesn't work as expected.

I have this image with the following tags: Eintritt Formular Event

Bildschirmfoto 2016-10-26 um 11.18.39 3.png

But when I try to filter with "Contains Words" it doesnt't work as expected, it doesn't find anything.

filtered.png

So I tried it also to search with the listerpro and there I get this error:

lister.png

Do you have any ideas why this doesn't work?

Share this post


Link to post
Share on other sites

I tried the Lister Pro 1.0.8 with Media Manager 0.0.6 on localhost on a fresh install. It works well with the "contains words" option. Looks like it's a issue from some code snippets(hooks etc..) I wrote. I will search through the code to look if I find something which causes this problem.  Sorry for blowing up the thread @kongondo...

Share this post


Link to post
Share on other sites

Hi everyone,

Is the module compatible with PW 3.x ? I tried to update an installation yesterday but it all broke down :) The noticed the files in the module had been deleted! (one of the errors said it couldn't find a module file). Tried to reinstall de module, but had no effect. Sorry I didn't bring the complete error log, I did it in a production site so I had to restore quickly.

Thanks for the great support!

Share this post


Link to post
Share on other sites

@Nukro

 

1. Is it possible to save the filter interface configuration (like in ListerPro)?

No it's not. But the filter should remember the filters you set up last. The filter interface as it is is generated by a core module InputfieldSelector (even in ListerPro). Saving the configuration bit is something extra ListerPro does and Media Manager doesn't.

2. Filtering tags by words (it should ignore the order) doesn't work as expected.

I have experienced some weirdness myself but I probably have an older version of InputfieldSelector. The 'OR' filter has not been working for me, i.e. find image media or document media or video media tagged as 'travel'. It is something am looking into and thanks for raising this.

@elabx

Is the module compatible with PW 3.x ?

Officially, not yet although some people have been using MM in PW 3 without any issues, certainly not files being deleted ???. I am currently working through a requests queue after which I will deal with compatibility issues

@all

I was hoping to release the version 7 of MM by next week but there have been delays (external factors, etc) so there will be a bit of a delay am afraid, sorry. Just to remind you what I am working on:

  1. Multi-tagging (and bulk removal of tags as well
  2. Media replacement (part of a setting on what to do when MM detects a duplicate media is being uploaded )
  3. Sorting media by tags (and sort order)
  4. Uploading of media via the CKEditor plugins
  5. Bug where CKEditor plugin MMLink is conflicting with PWLink (e.g. takes over double click)
  6. List view of media (especially useful when dealing with documents with long file names)
  7. A couple of other enhancements (including CSS Fixes)

Thanks

  • Like 4

Share this post


Link to post
Share on other sites

Looking forward to version 7 @kongondo! Uploading from CKEditor would be sweet. 

Are you able to fix the CKEditor buttons issue when used with Reno/Lightwire theme as well? Looks like the css fix is pretty straight forward.

Thx

 

Share this post


Link to post
Share on other sites
On 28/10/2016 at 5:52 PM, Rudy said:

Looking forward to version 7 @kongondo! Uploading from CKEditor would be sweet. 

Are you able to fix the CKEditor buttons issue when used with Reno/Lightwire theme as well? Looks like the css fix is pretty straight forward.

Thx

 

Yep, that too :)...edited post above, thanks..

Share this post


Link to post
Share on other sites

Great module from what I could see in the videos. Definitely something I want to use in my upcoming projects.
 

Only one question regarding the handling and output of images

Is there a way to make any kind of pre-defined crop-settings (like in the Croppable Image 3 module) or something like the focus area from the (unsurpassedly useful but unfortunately not PW 3 compatible) ImageFocusArea module available with Media Manager?
 

Why I ask

In my websites I use responsive images wherever possible, usually using the picture element because I often need its art direction feature.

So my workflow in PW 2.x was:

  1. Use the ImageFocusArea module’s input field to upload an image.
  2. Define the important region (= “focus”) of the image which must be fully visible in all cropped image variations.
  3. Have ProcessWire create all required sizes of all required image variations directly from the original image using the image sizing options (extended by the ImageFocusArea module) in the template files.

The two big pros of this workflow were that the user only had to define the important area of the image once – and was not bothered with any cropping settings (like finding a good-looking image section for an extremely wide horizontal format) – and that all required variations and sizes (I usually use about 10 different images per picture element) were created directly from the original image (which ensures best quality because no unnecessary compression steps were included).

In PW 3.x I had to change this due to the new image field which makes the ImageFocusArea module incompatible with PW 3:

  1. Use the Croppable Image 3 module’s input field to upload an image.
  2. Use the input field’s settings to define the biggest (in pixels) version of each required aspect ratio variation of the image.
  3. Let the user define the best looking image sections for the different crop variations (let’s say we need a 2:1 aspect ratio version and a 4:3 aspect ratio version of the image for one picture element).
  4. Have ProcessWire create the required downscaled versions of the “source images” (i. e. the variants created using the pre-defined crop settings of the Croppable Image input field) using the standard image sizing options in the template files.

While it works, the two big cons here are that the user has to define the different aspect ratio variations manually (assuming that the automatically created default cropping around the image’s center isn’t the best-looking option) and that the downscaled variations of each aspect ratio variations are created from an already processed image (so this includes at least one unnecessary compression step). And of course changing aspect ratio variations later (because of a website layout revision) can result in a lot of manual work to adapt cropped image variations.
 

What would really be a great extension for Media Manager in my opinion

It would be great if the ImageFocusArea module’s functionality would be available in Media Manager under PW 3. This would make using different image variations a no-brainer – without the website editor having to know anything about image variations, aspect ratios, sizes, cropping, etc.:

  1. The website editor uploads an image in Media Manager.
  2. The website editor defines the important area of the image which may never be cut away.
  3. The website editor selects the image on the respective page using Media Manager’s input field.
     
  4. That’s it. The template files take care of the rest. And even if the website layout completely changes the selected image needs not to be touched, since all required image variations are created from the original, centrally available image, making sure that the image’s main motive is always presented in the best possible way.

Of course, when inserted into a CKEditor field, the editor can apply an individual cropping if desired.

Unfortunately I’m not a backend developer at all. So I can’t make any code suggestions on how to make this work.

  • Like 1

Share this post


Link to post
Share on other sites

@kongondo, is the Add Media link supposed to open in a modal window rather than opening to its own page?  

On mine, it opens to a new page. I have to click on the back button to go back to the entry page.

Share this post


Link to post
Share on other sites
52 minutes ago, Rudy said:

@kongondo, is the Add Media link supposed to open in a modal window rather than opening to its own page?  

On mine, it opens to a new page. I have to click on the back button to go back to the entry page.

Should be modal...that's strange. Any JS errors? PW version?

Share this post


Link to post
Share on other sites

JS error appeared after I clicked the Add Media. See attached anim GIF.

 

mediamanager-addmedia.gif

Share this post


Link to post
Share on other sites
Quote

No it's not. But the filter should remember the filters you set up last. The filter interface as it is is generated by a core module InputfieldSelector (even in ListerPro). Saving the configuration bit is something extra ListerPro does and Media Manager doesn't.

Would it be possible to integrate this config saving feature also in the Media Manager? It would be a very nice addition to it and it would very speed up the workflow of the users.

Share this post


Link to post
Share on other sites

@Rudy. Hmm, not sure that's it though. I have been having a pesky JS 'uncaught' error in MM that I haven't been able to catch myself! :) I don't know what it's about. What version of ProcessWire is that? No changed files? 

@Nukro. I'll have a think about that request.

@Michael van Laar. Thanks for your interest in MM. You got some cool ideas there ^-^. However, MM itself is not a media editor and there are no plans to make it one:). Unfortunately, I have never used Croppable Image 3 nor ImageFocusArea. I really have no idea how they work and/if how they could be integrated into MM. I'll try to put aside some time to look into this further, but I can't promise when, unfortunately. If such an extension ever came to light, at this point in time, it looks like it would have to be its own module, packaged and sold or distributed separately from MM.

  • Like 2

Share this post


Link to post
Share on other sites

@kongondo, I am running PW 3.0.38 with Reno admin theme. For curiosity, I switched back to the default admin theme and was able to reproduce the issue as well.

Share this post


Link to post
Share on other sites

@Rudy. Thanks for the update.

So it seems to be a PW 3 issue then. I have not been able to reproduce in PW 2.x. Could you please try in a PW 2.x and let me know? Thanks.

Share this post


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

However, MM itself is not a media editor and there are no plans to make it one.

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

As an alternative to the above described I could think of input field types which work like Croppable Image 3 or ImageFocusArea, but use a Media Manager image instead of a directly uploaded image. I know this is not something which can be done with Media Manager itself. It would rather be a concept of being able not just to extend the standard image field but to extend a king of “remote image” fieldtype the same way. But I think this would have to be in the core, so that every module which extends or uses the standard (direct upload) image field could use this “get an image from Media Manager and apply the module’s magic to it” image field.

  • Like 1

Share this post


Link to post
Share on other sites

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.

Edited by Rudy
Added more info

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   0 members

    No registered users viewing this page.

  • Similar Content

    • 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-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 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 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • 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/
×
×
  • Create New...