Jump to content

Recommended Posts

Just now, Lutz said:

Media Manager for storing the images?

Each media is a PW page, hidden in admin part of the tree. Non-supersusers never get to see them :-).

Share this post


Link to post
Share on other sites
27 minutes ago, David Karich said:

Apropos: I never received a download link for the update to 012 by mail. Or do I have to buy a new license?

Subscriptions (update + VIP support) are valid for 1 year. After that you can renew for a fraction of the original price. Otherwise, I don't send out update reminders but post here in the forums. If you have a valid subscription, you can use the resend download links form to get an email with the download link to the latest version (or use the link in the original email you received after purchase). For renewals, please use the renewal form. Any problems, please PM or send me an email.

  • Like 1

Share this post


Link to post
Share on other sites
47 minutes ago, kongondo said:

Each media is a PW page, hidden in admin part of the tree. Non-supersusers never get to see them :-).

@kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?

Share this post


Link to post
Share on other sites
33 minutes ago, Lutz said:

@kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?

Sorry I wasn't clear.

Media = $page

Media has one MM field. In the case of images, it is an multi image field. So $page->image_field will give you the image

Media has a title field: $page->title;// title of your media

If you had own fields to Media, you can access them using $page->your_field, as usual.

However, we don't use the variable $page. Instead what you get is a MediaManager Object.

So, Media page object is $mm.

Echo $mm->id: id of the media

Echo $mm->title;

// this is the image field

foreach($mm->media) {

}

Hope this makes sense.

 

Share this post


Link to post
Share on other sites
31 minutes ago, kongondo said:

Hope this makes sense.

 

@kongondo Yes, thank you, this is what I had expected and hoped for. My question was in terms of scalability, regarding file system limits. In PW, files are stored in subdirectories under /site/assets/files, therefore we normally have to deal with max directory limits (e.g. 32k). We have $config->pagefileExtendedPaths, but it's marked as beta. So as you mentioned +500k, I hoped for an info regarding the stability of pagefileExtendedPaths (or another way to avoid collisions with max directory limits). When they manage +500k, did they enable pagefileExtendedPaths?

Share this post


Link to post
Share on other sites
1 hour ago, Lutz said:

When they manage +500k, did they enable pagefileExtendedPaths?

I have no idea. I never asked. I could try and find out.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for this awesome module! Here is some feedback after some hours of testing: When using MediaManager along with Ryan’s ProDrafts, I had to manually disable ProDrafts support for the MediaManager specific templates. Otherwise, inserted images from the MediaManager would not display in the saved pages (neither drafts nor published versions). I figure this was because the images in MediaManager were by default also handled as drafts. After disabling ProDrafts for the MediaManager templates, everything – including working with drafts – works just fine.

  • Like 1

Share this post


Link to post
Share on other sites
11 hours ago, tb76 said:

Thanks for this awesome module!

Glad you like it.

11 hours ago, tb76 said:

I figure this was because the images in MediaManager were by default also handled as drafts. After disabling ProDrafts for the MediaManager templates, everything – including working with drafts – works just fine.

Thanks for testing and reporting back. I guess it doesn't make much sense to have a draft media (i.e. using ProDrafts). However, if you have added other fields to your Media Manager templates, you might want those to work with drafts. Hmm. I've never used ProDrafts before but you've given me something to think about.

Share this post


Link to post
Share on other sites

Hi kongondo,

one of our customers asks, if it would be possible to write out not only the usage amount of media manager items, but also all usages as list with concrete info about field, page etc. I know, this isn't going to be easy, but maybe it's worth the effort, if other users reported the same idea?

Greetings,

Thomas.

  • Like 1

Share this post


Link to post
Share on other sites
On 6/21/2019 at 3:57 PM, xportde said:

one of our customers asks, if it would be possible to write out not only the usage amount of media manager items, but also all usages as list with concrete info about field, page etc. I know, this isn't going to be easy, but maybe it's worth the effort, if other users reported the same idea?

Hi Thomas,

I'll have a think. The interface will need careful thought as it would need to be separate from the tooltip.

Share this post


Link to post
Share on other sites
On 5/10/2019 at 3:09 PM, kongondo said:

However, two people have reported an error about class ProcessMediaManager not found in line 20 of MediaManagerUtilities.

Three people now! haha

Any news on this bug?? Thanks!

I rolled back but now I am having issues with JqueryUpload version 008 working, tried rolling back to 002 but I still can't open when I click on Add Media on any of the pages, getting:

 Uncaught Error: Class 'ProcessWire\JqueryFileUpload' not found in /srv/users/serverpilot/apps/ladosis/public/site/modules/ProcessMediaManager/ProcessMediaManager.module:209

Ok this took me through a tour of namespacing issuer all over the MediaManager modules and got it working back. 

Share this post


Link to post
Share on other sites
On 7/31/2019 at 6:23 AM, elabx said:

Three people now! haha

Any news on this bug?? Thanks!

I rolled back but now I am having issues with JqueryUpload version 008 working, tried rolling back to 002 but I still can't open when I click on Add Media on any of the pages, getting:

 Uncaught Error: Class 'ProcessWire\JqueryFileUpload' not found in /srv/users/serverpilot/apps/ladosis/public/site/modules/ProcessMediaManager/ProcessMediaManager.module:209

Ok this took me through a tour of namespacing issuer all over the MediaManager modules and got it working back. 

Hey @elabx,

Sorry for the delay in responding. I have just tested in a new PW install with only 3 modules: MM, JFU and Tracy. I had to click on Clear Compiled Files 3 or 4 times for it to finally work. Here's what I did.

  1. Upgrade JqueryFileUpload by overwriting the existing files
  2. Delete MediaManagerTabs.php and pocketgrid.css in the current (old) Media Manager install
  3. Overwrite MM version 011 files with version 012 files
  4. Access Media Manager
  5. You might see Class not found error (either MediaManagerUtilities or JqueryFileUpload
  6. Access Modules (on same tab in #4) and click on Clear Compiled Files
  7. Once step #6 is finished, click browser back button to go back to Media Manager.
  8. If you get class error again, repeat steps 6 - 7 as necessary

Please let me know if this works for you. Thanks.

  • Like 1

Share this post


Link to post
Share on other sites

@kongondo Finally managed to updated!! But you know what, now I didn't have to clear anything, it just worked after a module refresh!! Just so you have more info, the only difference was that I namespaced the old modules (in a desperate attempt to bring back everything to work because it kind of broke after I rolled back from my first install failure). honestly don't have very clear what happened, but indeed the new version works flawlessly.

Questions/issues: 

  • I don't seem to be able to drag and drop over the Inputfield. I can give you access to my site if you need to debug.
  • I cannot seem to find the edit button for the image description now, the one that was placed at the top right? Is there a new way to edit the descriptions? Appending how my images look when I click on them.   Jut realized now this is done in a normal, maybe you could enable an Edit link right on the Inputfield? At least on my site it's not showing, I'd guess that's the most practical for editors, instead of opening the Media Manager Popup.
  • I cannot get the alt text on images placed in CKEditor to update accordingly, I also have the setting updated in the Inputfield configuration, have you had any issues with this?

All my questions crossed where solved configuring the Inputfield :)

This is a GREAT update kongondo! I know this has been mentioned before but the improvement in the UI is a huge plus! I see you mentioned you have a lot of users that had never mentioned this, but in my case as with other PW users, all my clients complained about the lack of polish in UI, but this update really solves a lot of the inconveniences. 

Share this post


Link to post
Share on other sites
Posted (edited)
10 hours ago, elabx said:

Just so you have more info, the only difference was that I namespaced the old modules

Aah, nice workaround. I never thought to do that 😊.

10 hours ago, elabx said:

This is a GREAT update kongondo! I know this has been mentioned before but the improvement in the UI is a huge plus! I see you mentioned you have a lot of users that had never mentioned this, but in my case as with other PW users, all my clients complained about the lack of polish in UI, but this update really solves a lot of the inconveniences. 

Glad you like it :-).

10 hours ago, elabx said:

I cannot get the alt text on images placed in CKEditor to update accordingly, I also have the setting updated in the Inputfield configuration, have you had any issues with this?

I don't follow. What is this alt text please? Please clarify which inputfield configuration, CKEditor or MM?

Full documentation is available here, by the way :-).

Thanks.

Edited by kongondo

Share this post


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

I don't follow. What is this alt text please? Please clarify which inputfield configuration, CKEditor or MM?

 

When you insert an image through CKEditor, ideally I'd want to grab the description from the image's description field. CKEditor Inputfields fields have an option called "Image management" that should enable this:

https://processwire.com/docs/fields/textarea-fieldtype/#markup-html-option

I just can't get this to work well, if I add a new image to the text fields, their descriptions are not pulled from the images. 

My bad again man, I kept on reviewing this on the CKeditor source and just realized this is done on runtime. 

Share this post


Link to post
Share on other sites
21 minutes ago, elabx said:

My bad again man, I kept on reviewing this on the CKeditor source and just realized this is done on runtime. 

😀

  • Like 1

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 Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      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)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      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 nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...