Jump to content

Module: MediaLibrary

Recommended Posts

( Sorry again @kongondo, you're right I'll be more careful in the future )

So, Some time, I do not understand why, the modulo deletes some images.

I notice when a user enters these pages and in the backend appears the 404 error, I go to check inside the media library page and in fact the images inside the media manager are gone.

Someone knows why and what can I do?

Share this post

Link to post
Share on other sites
On 7/2/2018 at 2:37 PM, MarcoPLY said:

Someone knows why and what can I do?

Sorry, I missed this question. I hope this has meanwhile been solved. This looks more like a generic ProcessWire issue, since the upload uses core functionality and the symptoms sound familiar from regular image upload (memory issues or PHP limits).

Share this post

Link to post
Share on other sites

Status update: Release 0.1.3

I finally managed to implement hiding libraries from the page tree as requested in the issue tracker. This can be enabled in the module configuration and optionally extended to superuser. Deletion of libraries is now possible through the Media admin page.

  • Like 1

Share this post

Link to post
Share on other sites

Thank you @BitPoet, the problem still unsolved. The images are loaded inside the folder, I checked via ftp. But after a few hours/day they are deleted. This only happens in a folders with lots of images inside, if I create a new one and reload the images this problem is solved. There are no notice about the memory issues, could it always be this?

Share this post

Link to post
Share on other sites


after installing the modul MEDIA LIBRARY, i get this Messeage when i click on the button Media:


Schwerwiegender Fehler: Uncaught Error: Call to undefined function ProcessWire\_() in /site/modules/MediaLibrary/ProcessMediaLibraries.module:51
Stack trace:

#0 /wire/core/ProcessController.php(337): ProcessWire\ProcessMediaLibraries->execute()
#1 /wire/core/Wire.php(380): ProcessWire\ProcessController->___execute()
#2 /wire/core/WireHooks.php(813): ProcessWire\Wire->_callMethod('___execute', Array)
#3 /wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessController), 'execute', Array)
#4 /wire/core/admin.php(150): ProcessWire\Wire->__call('execute', Array)
#5 /wire/modules/AdminTheme/AdminThemeUikit/controller.php(15): require('/volume1/Projek...')
#6 /site/templates/admin.php(15): require('/volume1/Proj (Zeile 51 in /site/modules/MediaLibrary/ProcessMediaLibraries.module)


Can anyone help me?
Thanks, Detlef

Share this post

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

Can anyone help me?

Looks like the plain _() translation method is not available anymore for some reason (perhaps something to do with the changes in the function API that I didn't catch). Could you try out the version at this link and let me know whether that fixes it for you?

  • Like 1

Share this post

Link to post
Share on other sites
On 10/7/2019 at 4:05 PM, felted said:

Now it runs.
Thank you!

Thank you for the feedback. I have merged the change into the main branch, so once 0.1.4 hits the module repository (should be within the next 24 hours) it will be fixed the official package too.

  • Like 2

Share this post

Link to post
Share on other sites

Next Feedback 🙂

After hit the button Delete library i get this error:



Call to undefined function _(), did you mean processwire\_n()? fix it► search►
File: .../ProcessMediaLibraries.module:133

123:                $frm->append($hidden);
125:                $hidden = $this->modules->get("InputfieldHidden");
126:                $hidden->attr('name', 'modal');
127:                $hidden->attr('value', 1);
128:                $frm->append($hidden);
130:                $f = $this->modules->get("InputfieldMarkup");
131:                $f->attr('id+name', 'trash_msg');
132:                $f->label = $this->_("Procceed?");
133:                $f->attr('value', sprintf(_("Really move library <strong>%s / %s</strong> into the trash bin?"), implode(' / ', $page->parents->explode('title')), $title));
134:                $f->description = sprintf(_("Library contains %d images and %d files"), $page->media_images, $page->media_files);
135:                $f->notes = $this->_("Any files/images contained in this library will be deleted.");
136:                $frm->append($f);


  • Like 1

Share this post

Link to post
Share on other sites
On 10/11/2019 at 10:04 AM, felted said:

Next Feedback

Thanks for letting me know. Fixed in 0.1.5, already on GitHub and soon in the module repo. I'm pretty sure I caught all translation call issues now.

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

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 eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild.  
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Min/max values Precision (number of decimals) Steps (Read more) Manual override of the selected value (will still adhere to the rules above) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant If it's usable for others I'll add it to the Modules list  
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional 
      - Initial release
    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

  • Create New...