Jump to content

PWaddict

Members
  • Content Count

    730
  • Joined

  • Last visited

  • Days Won

    1

PWaddict last won the day on December 7 2018

PWaddict had the most liked content!

Community Reputation

349 Excellent

About PWaddict

  • Rank
    Hero Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,399 profile views
  1. @MaierGrem I have already posted in the module's forum, and problem solved by @adrian. Thanks anyway :) Can a moderator please delete this topic, as it's useless. I didn't knew when created it that the issue was from a third-party module.
  2. modified: Unix timestamp of when Pagefile (file, description or tags) was last modified. mtime: Unix timestamp of when file (only) was last modified. Taken from Pagefile API Reference.
  3. Thanks a lot. I switched from mtime to modified and the problem is gone :) Maybe you should add a note on the Rename rules to avoid using mtime.
  4. Yep, I'm getting the same results with you.
  5. Hm, after I checked the "Overwrite existing files?" on image field the problem is gone. So, the module to properly work needs that option checked?
  6. Tracy displays them in orange color as orphans.
  7. The structure on my template is in this order: various fields Image field Repeater field Repeater field various fields The image doesn't display on frontend because it seems that it doesn't get saved in database??? I'm checking if the image exists like this: if($page->image) etc. There is nothing wrong in the code on template cause if I save the page AGAIN then this time the image is properly getting saved and displayed on frontend. Image Maximum files allowed: 1 Formatted value: Automatic EDIT: It's a multi-language site.
  8. Hello @adrian Today I noticed a very strange behaviour with the module. If I upload an image on the Image or CroppableImage3 field and then add a new repeater item on a repeater field and publish / save the page, the image doesn't display on front-end. The image and its variations are visible on back-end and on the related folder in assets. If I first add a new repeater item on a repeater field and then upload an image on the Image or CroppableImage3 field then there is NO problem. WTF? I verified that this is caused by the module cause when I temporarily disable the rule there was NO problem. My rule is: {$page->title}_{$file->mtime} with Rename on Save checked. I'm using PW 3.0.135.
  9. Hello. Today I noticed a very strange behaviour. If I upload an image on the Image or CroppableImage3 field and then add a new repeater item on a repeater field and publish / save the page, the image doesn't display on front-end. The image and its variations are visible on back-end and on the related folder in assets. If I first add a new repeater item on a repeater field and then upload an image on the Image or CroppableImage3 field then there is NO problem. WTF? I'm using PW 3.0.135. Can PLEASE someone help me? EDIT: It seems the issue is caused by Custom Upload Names module. I will post on the related topic.
  10. @Robin S It works. Thanks a lot!
  11. LimitRepeater can't lock repeater items.
  12. I would like to lock a specific repeater item with the id 1553 to prevent editing from non-superusers but none of the above work. Can you please help?
  13. @adrian I found a small bug. Using slashes for example on the title field the image doesn't rename properly. For example on title field I have: Poster/Flyer and the image renamed to flyer.jpg where it should be poster_flyer.jpg.
  14. Is it possible to prevent optimizing on upload on specific field via hook? Nevermind, don't need it anymore.
×
×
  • Create New...