Jump to content

Recommended Posts

My bad the cropping functionality works...  I didn't recognized (again..) the Apply button on the left corner xD. 

  • Like 1

Share this post


Link to post
Share on other sites

Ok i solved the video problem with setting the maximum allowed size of uploaded files.

; Maximum allowed size for uploaded files.
upload_max_filesize = 100M

; Must be greater than or equal to upload_max_filesize
post_max_size = 100M

I had 10M before and was trying to upload a 40M video..

  • Like 1

Share this post


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

@Nukro...Nice. Glad you got them sorted. Any pending issues?

The only issue left is, when I click "save as copy" without cropping or changing the dimensions. It somehows loses the original:

copysave.png

Share this post


Link to post
Share on other sites
On 27/09/2016 at 9:39 AM, kongondo said:

Hi @spacemonkey95. Thanks for the purchase.

Media Tags: The purpose of 'media tags'...is the same purpose as in ProcessWire (please note: all media can be tagged; not just images); namely, to group related media (images, documents, video or audio) to fulfil any number of functions - easier organisation, finding related things, etc. 

Filtering media by tags: Yes, it is already possible to filter images (or any other media) by tags both in the API and in your Media Manager Library (the Process Module). Please see the gif below.

What is pending is the ability to tag multiple media in one go. Currently, one can only tag one media at a time as shown in my post above. This can be tedious, hence the need for multi-tagging capability. I have started work on this new feature but it won't be ready this week but soon. It is also not possible, currently, to sort media by tags (i.e. the display of media in the Media Library - currently sorted by title). I am also working on implementing this.

Hope I've answered your questions.

Filtering media by tags

media-manager-media-tags-filter.gif

Hi, thanks for your reply.

The options shown in your gif aren't visible to me, so I'm unable to filter by tags. Do I have an older version installed? I only added it a few days ago.

 

I have another question that's just arisen too. I have superuser rights to my site, but I've assigned limited 'author' rights to another user. When they click on the Media Manager button in a CKEditor field, they get an 'Unrecognized path' error message with 'The process returned no content' underneath it. But it works fine for me. Do you know why this might be? Is it a permissions thing? If so how would I solve it?

Thanks

Share this post


Link to post
Share on other sites

@spacemonkey95

Apologies, I should have been clearer that the gif in my post is for a dev version of Media Manager (i.e. Settings will move to its own menu). However, even with the current version, the one you downloaded (version: 006), you should still be able to filter by tags. I suspect that you did not enable tags for all your media templates. Your 'author user' not being able to access the media library via the CKEditor icon seems like a permission issue. For both issues, please follow the instructions provided in the 'Getting Started' documentation first and let me know if you still have issues.

Thanks.

Share this post


Link to post
Share on other sites

Thanks for your quick reply. Sorry I missed those parts in the documentation! That has solved the problems.

This seems to be a really cool module, I'm glad I tried it. I have just one more question: is it possible to upload images to the Media Manager from within the CKEditor button?

  • Like 1

Share this post


Link to post
Share on other sites

Ah, I think maybe you misunderstood my question. I have already been able to insert images from Media Manager using a button on CKEditor, that works fine.

What I'm asking is whether it's possible to click on the CKEditor menu button and be able to UPLOAD new images from my computer to Media Manager. Otherwise I have to upload all the images I need before starting the page, or have a 2nd tab open with Media Manager in it.

Share this post


Link to post
Share on other sites

Oops, my bad. Currently no. I decided to disable that. I could make the feature configurable though or just leave it on. Thoughts? Let me have a think...

 

Share this post


Link to post
Share on other sites

For my particular project it would be a fantastic feature, at least to have the option to enable it.

I have a number of people adding documents to the site, almost all of which will require images as you go along, so it would make it so much easier.

Let me know what you think. That aside, it's a fantastic module and has made the process of creating my project so much easier than using the standard PW images. Thanks for your hard work and continuing support on it. :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi @kongondo

Does this functionality scan all Image and File Fields for new media and create new media-manager-image/file pages? I think it scans the assets/files folders? I have a couple of image and file fields with media in it but the scan functionality can't find any media. Or do I missunderstand the use of this scan functionality?

scan.png

Greetings Nukro

Share this post


Link to post
Share on other sites
On 29/09/2016 at 4:39 PM, spacemonkey95 said:

For my particular project it would be a fantastic feature, at least to have the option to enable it.

I have a number of people adding documents to the site, almost all of which will require images as you go along, so it would make it so much easier.

Let me know what you think. That aside, it's a fantastic module and has made the process of creating my project so much easier than using the standard PW images. Thanks for your hard work and continuing support on it. :)

Hi. Just to let you know that I will be including this feature in the next version of Media Manager. At the moment I don't have an ETA due to a couple of competing demands from my other commercial modules. I am hoping for a release in about 3 weeks's time. I hope that is not too late for your project? Thanks.

Share this post


Link to post
Share on other sites
22 minutes ago, Nukro said:

Hi @kongondo

Does this functionality scan all Image and File Fields for new media and create new media-manager-image/file pages? I think it scans the assets/files folders? I have a couple of image and file fields with media in it but the scan functionality can't find any media. Or do I missunderstand the use of this scan functionality?

scan.png

Greetings Nukro

Hi. It does not scan your assets/files folder. Instead...

  • It scans all media uploaded to a particular directory (see below)
  • The media could be 'loose' or zipped, in nested folders, etc..
  • Thorough checks (validation) are conducted: allowed extensions, mime_types, minimum and maximum file sizes, and for images minimum/maximum width and height. Any media failing any validation will be deleted
  • To use the function, FTP or upload media to the directory: /site/assets/MediaManager/uploads/
  • That folder should be created automatically when you access Media Manager if folder permissions allow. Otherwise, you'd have to create one
  • Each media will be correctly identified and added to the correct media type (audio, document, image, video) in your Media Library
  • Once added to the Library, the files uploaded to ..../uploads/ will be deleted

Hope this answers your question. Please also have a look at the 'help' tab under the menu 'Upload' in Media Manager.

Thanks.

Share this post


Link to post
Share on other sites

EDIT: solution found, thanks @kongondo

Hi!
I have a problem with this Module.
I cannot select a single image to make changes in the description, etc, because it is always the FIRST image in the array selected (seen as the big image on the right).

if i choose another one (yes, even, if i only select one instead of more) , i can INSERT it, but impossible to get it "selected" and shown on the right side to make changes.

i have to use the filter to search for the image so that it will be in FIRST position on the left, only after this it is possible to select it.

i'm on PW2.7.2
 

Bildschirmfoto 2016-10-03 um 11.13.47.png

Share this post


Link to post
Share on other sites

@vanderbreye,

Many thanks for using Media Manager.

Apologies, documentation is seriously lagging behind. I am trying my best to complete it. 

To select a media for editing and preview, please click on its title. The module will remember the last clicked media and if it was being previewed or edited. The media currently on preview will be highlighted with a greenish/yellow box as seen in your image above and its title will be white text against a black background. For other manipulations such as inserting or applying bulk actions (e.g. publish, lock, etc), please click on the thumbnail itself. 

Hope this answers your question.

Cheers.

  • Like 2

Share this post


Link to post
Share on other sites

hey @kongondo, that does the trick. Thank you! 
maybe it is an option to make the selection obsolete, when the field is set to 1 Image only, and select it directly on click of the thumb?
also, i would suggest to let the "add Media" Link be visible if the maximal image count is reached - and then simply replace the image instead of first having to select & delete & save the image /page to add another media. :) i know, its not THAT simple, but i guess this would be a big improvement!

great module, though!
 

  • Like 1

Share this post


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

Hi. Just to let you know that I will be including this feature in the next version of Media Manager. At the moment I don't have an ETA due to a couple of competing demands from my other commercial modules. I am hoping for a release in about 3 weeks's time. I hope that is not too late for your project? Thanks.

Hi, that's great! I think we'll manage until then, but that will definitely help us in the long term. Thanks again

  • Like 1

Share this post


Link to post
Share on other sites
On 03/10/2016 at 4:40 PM, vanderbreye said:

and one more question: i might be wrong, but shouldnt it be possible to have multilanguage-descriptions? 

To be honest, I haven't tried this.  The editor grabs what PW returns as the description. I am so ignorant when it comes to multi-lingual setups. Do files/images have multiple inputs for tags and descriptions in such cases?

Share this post


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

To be honest, I haven't tried this.  The editor grabs what PW returns as the description. I am so ignorant when it comes to multi-lingual setups. Do files/images have multiple inputs for tags and descriptions in such cases?

i set it up by myself, to be honest, more like hacked it.
PW stores ML-Description as JSON {"0":"defaultlangtext","1022(aka LanguageID)":"anotherlangtext"}, and handles this internally. 

i added a textarea-field for each language in the "edit" template, and hide your default "description" textarea.  In the "save"-event in JS i simply create the json out of the contents of the different textareas and copy it over in the default-textarea before saving the $page. ;) Not the best way, but it's working.
you could also add different Fields like ("year", "artist", etc.) with this solution very quickly - by using other "ids" in the JSON.

the only problem i have right now is to populate the fields correctly, but i will try it by bypassing the language-hook today.

 

Share this post


Link to post
Share on other sites

Hi @kongondo

I have a question about uploading images/files with umlauts in the filename. When I upload a image like this for example:

umlaut in imagenames.png

It converts the filename to this:

Bildschirmfoto 2016-10-13 um 14.08.13.png

Is it possible to change this, that it takes the filename as it is? I'm also confused why it adds underscores since the filename doesn't have empty spaces? My Customer needs this, because he has many photos with french/german filenames (which has umlauts). 

 

Greetings

Orkun

Share this post


Link to post
Share on other sites

I think this is a PW issue in general. I think there has been some discussion on it (but can't find it right now), so I am not sure why it was decided to not support utf8 filenames but that was before PW supportedUTF8 page names, so maybe it is time to revisit?

  • Like 2

Share this post


Link to post
Share on other sites

Hi @kongondo Great job with the module!

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

It works fine on the standard CK Editor theme.

Thx

Rudy

Screen Shot 2016-10-13 at 3.06.44 PM.png

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