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 Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...