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

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

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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      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 If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      Please have a look at the screenshots to get an idea what I'm talking about (open spoiler):
      (Please note: these screenshots are from an early development state of SnipWire. To see actual screens please have a look at later posts below!)
       
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...