Jump to content
adrian

Custom Upload Names

Recommended Posts

Hi adrian,

Is there a way to use your module when images are uploaded via API (through a custom upload form)?

Share this post


Link to post
Share on other sites

Not at the moment, although that is a great idea. I'll look into it and see what I can come up with.

Share this post


Link to post
Share on other sites

Ok, sorry for the delay on this. I have added the ability to rename files uploaded via the API. It works on my testing using something simple like:

$page->images->add("/local_path_to_image/image.jpg"); 

$page->of(false);
$page->save();

I have attached a revised version of the module, rather than pushing to github for the moment. Please let me know if it works ok for you.

I am not sure how your upload form is working, but at the moment the module will rename the file in its original uploaded location before copying it to the final ID based folder under /assets/. I am not sure if this will work in all scenarios, but I had to use a "before" hook on "Pagefile::install" so that I could still change the filename using: 

$event->setArgument(0, $newFilename);

Using a before instead of after hook means that I am working with the file in its original location. It also means the module can't handle images from remote servers with full http:// paths. Does anyone have any ideas how I might be able to rename after it has been move to the assets/xxxx/ folder? None of the InputfieldFile hooks get called with API uploads, so they are out. I am thinking maybe I might need Pagefile::setFilename hookable, but I'd love to hear any ideas on how to do this.

On an unrelated note, I have also added the ability to drag/drop sort the rules in the module settings, making it easier to change the order as needed, which can be important if you have a lot of very specific rules that need to take precedence over more general ones later in the order.  

CustomUploadNames.zip

  • Like 2

Share this post


Link to post
Share on other sites

One more tweak this morning. There is now the option to 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.

I am not sure if this is what @peterfoeng was looking for in his post above, but hopefully people will find it useful regardless.

For the moment, this new version is only available as the attachment here.

CustomUploadNames.zip

  • Like 1

Share this post


Link to post
Share on other sites

Adrian, thanks for these updates. Are you going to be updating the GitHub repo for these changes as well?

Share this post


Link to post
Share on other sites

Hey Ryan,

I will update the GitHub repo for sure.

I was hoping to improve the hook for uploading via the API first though - I'd really like to delay the rename until after the file has been copied into the assets/xxxx folder so I am not messing with any file manipulation code that a front-end form might use. If it uploads the file to a temp directory and then makes the api call to install the file, eg: 

$page->images->add("/local_temp_path_to_image/image.jpg");

then the form won't know the new filename and so won't be able to delete the file from the temp location. Also, some of the front-end upload scripts posted to this forum suggest moving the file to the final assets/xxxx folder before using ->add, in which case the Pagefile::install won't even be triggered. I'd also like to be able to support images being added from an external URL.

Any thoughts on how best to achieve all these requirements? My post #28 above talks more about the issues with Pagefile::install and the need to run it as a before hook, but the problems that also causes. I am sure I must be missing an obvious option.

Share this post


Link to post
Share on other sites

Adrian, what about just using the Pagefile::rename function from a hook after Pagefile::install ? I may not be understanding the issue in full. But couldn't you just do something like this:

public function hookAfterPagefileInstall($event) {
  $pagefile = $event->object;
  $pagefile->rename('filename.' . $pagefile->ext); 
}
  • Like 1

Share this post


Link to post
Share on other sites

Thanks Ryan - very easy and effective. I didn't think about the rename function - was wondering how to rename the file as well as the pagefile in one easy process.

I have pushed a new version to GitHub which uses this for API uploads and as a result can now support renaming files that are added from remote URLs.

I think this should now work in all API / form scenarios, but if anyone comes across any issues, please let me know.

  • Like 1

Share this post


Link to post
Share on other sites

Hi everyone,

Another overhaul today. A few bug fixes and a bunch of new features. I have updated the first post here to detail them better, but key things are the ability to make use of the following variables in the filename format: $page, $template, $field, and $file.

To accommodate some of possibilities this opens up, eg: $file->description, there is new logic to handle renaming after page save if the filename format can't be properly evaluated at upload because the field isn't available yet, or is still blank. If possible, renaming will still occur during upload - "on save" is just a fallback if needed.

Another key addition is the ability to give each rule the option to rename the file again each time the page is saved. There are obvious issues with this if images or files are being linked directly by their URL, so care is needed with this option checked. It does allow for some incredible flexibility though. You could even have a field in your template called "Filename" allowing the user to rename the file whenever they want. In most scenarios of course this would not be at all desirable, but it suited my needs, so thought it might come in handy for someone else as well :) If nothing else, it might be useful during development, but could be disabled once the site is live.

Let me know if you find any bugs with this new functionality.

  • Like 3

Share this post


Link to post
Share on other sites

How should this be modified to have Datetime field in its output format instead of Unix timestamp in "Filename Format"?

Share this post


Link to post
Share on other sites

How should this be modified to have Datetime field in its output format instead of Unix timestamp in "Filename Format"?

I have just committed an update that makes this work as expected.

Because in the admin panel outputformatting is off by default, it needed to be manually turned on. I don't think there should be a problems with doing this in Custom Upload Names and some quick testing shows that it seems to be working fine, but please let me know if you discover any weird side-effects.

  • Like 1

Share this post


Link to post
Share on other sites

I also just added another formatting option that allows you to include the current date time in the filename, eg:

{$page->name}-[Y-m-d_H-i-s]-suffix

Anything inside square brackets will be treated as a php date format string and will be applied to the date/time when the file is uploaded and renamed.

You could instead use $page->created or $page->modified, but since these don't have a configurable output format, this seemed like a more flexible approach.

I think this should be a useful addition in several scenarios.

Share this post


Link to post
Share on other sites

Thank you for the quick response and feature implementation! It works for me as expected.

Yesterday I spent a few hours thinking how I could do renaming like this and then I discovered your module already existed :rolleyes:

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

I think I found another little thingie.

Yesterday I've decided to use an image-field in a repeater, custom name was enabled. I think you already know where I'm going :-)

The image didn't get saved, disabling did help.

Greetings.

Share this post


Link to post
Share on other sites

Hi,

I think I found another little thingie.

Yesterday I've decided to use an image-field in a repeater, custom name was enabled. I think you already know where I'm going :-)

The image didn't get saved, disabling did help.

Greetings.

Yeah, unfortunately I do know about this already - was just hoping it wouldn't come up :)

I made an initial attempt to fix it, but couldn't figure out a solution at the time. Then the new PageTable field was developed which Ryan recommends over repeaters in almost all scenarios so I didn't worry about it too much.

I'll take another look and see what I can do, but you really should try PageTables - so much nicer (and less problematic) than repeaters :)

Share this post


Link to post
Share on other sites

Oops... sorry....

I've heard/seen a lot of buzzing about the PageTables [and extended] but I haven't found the time to try it out...

Soon... so don't worry about it... it's fine...

Share this post


Link to post
Share on other sites

Supposed I upload multiple files at a time and want them to be rename to the following format format:

mysite-[Y-m-d]-{$file->description}

The problem is that all the files get renamed immediately (before hitting the save button) like this:

tmp-filename.pdf
tmp-filename-1.pdf
tmp-filename-2.pdf
...

Now, how can I tell which tmp-filename belongs to which original file? Sure, I could still open the files by clicking on their filename. But what if the new file format would only be applied after hitting the save button?

Share this post


Link to post
Share on other sites

Hi charger - sorry, I am not sure what the problem actually is. Because you have chosen to use $file->description the module has to use the tmp-filename option until the page is saved, when the description field is available. If you used $page-name or something else that is already available when the file is uploaded, it will rename fully as soon as it is uploaded. Maybe you have already figured that out though? 

Why do you need to know which file is which before you save the page? Once the page is saved the names will match the entered descriptions. 

Perhaps if you could explain your usage scenario I might be able to come up with a solution for you.

I am on vacation for the next two weeks though, starting in a few hours, so I might not be able to do anything until then, unless a clear idea emerges and it is easy to implement.

I guess I could go with renaming on page save, but that always seemed less elegant - shouldn't be too hard to make it an option though.

Share this post


Link to post
Share on other sites

The problem is that if I upload 10 files at a time and they all get renamed to tmp-filename.pdf before saving, then I have no chance to see the original filename and thus write the according description to it.

An example: I upload a file that is originally named 30_10_2014_EventHappyMonday.pdf. In order to know what to fill in in the description field (in this case it would be "Event Happy Monday"), it helps a lot if I still see the original filename and not tmp-filename.pdf.

Enjoy your holidays!

Share this post


Link to post
Share on other sites

Sorry now I understand - it's the writing of the description that is the problem - makes total sense :)

I often use this module with images (so not an issue), and when I do it with PDFs and other files I haven't ever used $file->description so I haven't had this issue yet.

The tricky thing about trying to fix this is that filename formats that use fields that aren't available at upload (like description) need to be renamed on save, but if you don't want the name to also change on each future file save (which you wouldn't given that you are including the date in the filename), the module needs to know it is the first time the file has been saved, which is why I use the tmp-filename intermediate renaming. Only files named tmp-filename get renamed on save. All others are ignored unless the "Rename on Save" option is checked.

It's almost 2am here and this is not a simple fix, so I am sorry, but I think it will have to wait a couple of weeks, but I'll definitely put it on my list and I'll let you know when I have a solution.

Share this post


Link to post
Share on other sites

Hey charger - woke up with an obvious solution. I just committed an update that should take care of your needs.

Now the temporary filename is: original-filename.upload.tmp.pdf

Hope that works well for you.

Thanks for letting me know about this.

  • Like 3

Share this post


Link to post
Share on other sites

Just tested it and works like a charm. Thanks a lot for the quick support!

  • Like 1

Share this post


Link to post
Share on other sites

Not sure about actually dreaming, but definitely in that blurry time while falling asleep and then lying there after just waking up - brain seems more clear and tries to actually figure out the problem, rather than the trial and error approach that can sometimes happen when you're at the computer trying to get something to work.

  • Like 2

Share this post


Link to post
Share on other sites

Here it's works the same. Recognise it as a whole.

But I do remember I'm programming in my dreams...

Edited by Martijn Geerts
one of the most inspiring movies i've seen: Pi

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By horst
      Croppable Image 3
      for PW 3.0.20+
      Module Version 1.2.0
      Sponsored by http://dreikon.de/, many thanks Timo & Niko!
      You can get it in the modules directory!
      Please refer to the readme on github for instructions.
       
      - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - 
      There is a new Version in the pipe, that supports WebP too: 
       
      - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - 
       
       
      -------------------------------------------------------------------------
       
      Updating from prior versions:
       
      Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:
      In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.
      -------------------------------------------------------------------------
       
      For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.
       
      -------------------------------------------------------------------------
       
    • By Robin S
      Inspired by a recent question.
      Image Crop Ratios
      Allows preset aspect ratios to be defined per image field for the ProcessWire image crop tool.
      The module adds a select dropdown to the crop tool. Choose an aspect ratio and the crop area will be fixed to that ratio.
      Screencast

      Installation
      Install the Image Crop Ratios module.
      Configuration
      Default aspect ratios for all image fields can be defined in the module config. Aspect ratios for specific image fields can be defined on the Input tab of the field settings. You can override the ratio settings in template context if needed. Insert a hyphen as the first item in the ratio settings unless you want to force a ratio to be applied to the crop tool. The hyphen represents a blank option that allows a free crop area to be drawn. Usage
      Click the "Crop" link on the details view of an image thumbnail. Click the "Crop" icon at the top of the editor window. Choose an option from the "Ratio" select dropdown.  
      https://github.com/Toutouwai/ImageCropRatios
      https://modules.processwire.com/modules/image-crop-ratios/
×
×
  • Create New...