Jump to content

adrian

PW-Moderators
  • Content Count

    8,940
  • Joined

  • Last visited

  • Days Won

    303

Everything posted by adrian

  1. Maybe I could programmatically replace mtime with modified. Can you think of any reason why mtime would actually be needed vs modified?
  2. @PWaddict - I have managed to solve the problem you are seeing, but there is another issue when using $file->mtime in the rename rule for images in repeaters that I am having trouble fixing. The problem is that when you save an image, the mtime changes and there is an order problem with the mtime changing before or after the renaming of the pagefile which is causing problems. I noticed though that it all works fine if you use $file->modified instead. Would that work ok for your needs instead of mtime?
  3. Ok, I think I have narrowed it down - if you don't have "overwrite" checked and you use $file->mtime it doesn't know how to name the file at the correct point it needs to. It's also necessary to have "Rename on Save" checked to have this problem. Let me see if I can fix.
  4. Does it help if you use $filePage instead of $page for the rule? What about "name" instead of "title"? What about if you don't have the $file->mtime component?
  5. I am testing on a multi-language site and just changed to max files 1 and it's still all working as expected. Sorry, I am not sure what else to look at right now. I am curious what Tracy's PageFiles panel reports after the initial saving of the page.
  6. @PWaddict - I feel like I have replicated your described workflow and I am not seeing any problems so I will need more troubleshooting from you. Why doesn't the image display on the frontend - is the code trying to display an image with a non-existant path? What code are you using to display the image? What are the image settings - anything related to the max files or overwrite settings that are relevant? Anything you can do to narrow it down further would be very helpful.
  7. So the $pages->find finds the page in the 3rd url segment and displays the content of that page? I guess I don't understand why that is better than having a template file for the document template - I am sure I am missing something, but maybe if you could better explain what you are actually trying to accomplish by doing it this way we might be able to offer some other/better alternatives.
  8. @Mike-it - it's due to this new bug in the core: https://github.com/processwire/processwire-issues/issues/979 Please add a comment there to get Ryan's attention about this.
  9. Glad you got things working again, but I can't imagine why a base64 encoded string would cause a problem. I just tried here and it looked ok. Maybe that wasn't really the issue but somehow the exceptions.txt was corrupted in some other way?
  10. Keep in mind that these two lines do exactly the same thing, so you only need one of them.
  11. Note sure - would you mind finding out what contents of $logLinesData is just before line 44 of ProcesswireLogsPanel.php and also $data before and after the json_encode() on line 449 of wire/core/WireCache.php Hopefully one/both of those will help to identify the problem. Thanks!
  12. You probably have "dev" in your hosts file pointing to localhost.
  13. https://web.dev/native-lazy-loading/
  14. All I see is this: but it's almost completely hidden until you hover over it. Anyway, as I think we all agree - this is all a PITA and I think we should interrupt the user as little as possible.
  15. I don't see it at all - using Brave Browser, but thanks for pointing out that there is actually something there when it works.
  16. I have also built a site on Knownhost - it's fast enough, but I did come across the nginx reverse proxy errors quite a lot - I think I managed to tweak things such that they aren't a problem now, but still found it painful initially. Also, they are just so much more expensive than Digital Ocean, so it depends on budget vs time/skills to manage the server I guess.
  17. For many years I was fortunate to host all my sites on my own dedicated University servers. These days I also use unmanaged Digital Ocean VPS servers whenever I can, but obviously these are not for everyone. The one thing I steer clear of is FastCGI / nginx as an apache reverse proxy - PW always gives me errors on these setups.
  18. Sorry, @guenter55 - I don't see anything in that example at osana.com that looks like a way to revoke consent after they have already given it. In my mind the link to revoke after initial accepting isn't something that can really be part of the module because where it should physically appear is specific to every different website - it's not something that can be in an overlay banner like the initial accept/deny option.
  19. adrian

    SeoMaestro

    I think this is probably just a side-effect of this recently introduced core bug: https://github.com/processwire/processwire-issues/issues/979
  20. Your mileage might be different, but I found Webfaction hosting quite slow, not to mention a very strange and overly complicated control panel 🙂
  21. Not sure, but I think my fork/branch does take care of that: https://github.com/adrianbj/MarkupSEO/tree/various-fixes-enhancements
  22. Thanks everyone for the recent discussion on this - the intricacies of GDPR are not my forte. Sorry, I don't really understand what you are looking for here - I don't think the module should always output a "Manage Your Cookies" - I think this needs to be something that the site developer decides where it should go and how it should be styled. Or maybe I am confused by what you want?
  23. I agree with @teppo - I recently discovered a colleague who was using phpc extensions on a site and he'd left debug mode on. I changed a URL query string value to something invalid which threw an error in a phpc file and I could simply load that file in the browser and view its contents - turns out it contained a payment gateway API secret key. All this because of a non-standard extension that PW's default htaccess file doesn't prevent access to.
  24. I know I am getting OT, but I almost never use target="_blank" anymore. Here are a few thoughts: https://css-tricks.com/use-target_blank/ I think the key thing for me is that it's really hard to prevent opening a new tab when it is used, but it's really easy for the user to choose to open in a new tab if they want, so my rule is that unless the user will lose unsaved form data as a result of opening a link in the same tab, I never force a new tab.
×
×
  • Create New...