Jump to content

howdytom

Members
  • Posts

    57
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Heidelberg Germany
  • Interests
    Music, Design, Technology.

Recent Profile Visitors

1,561 profile views

howdytom's Achievements

Full Member

Full Member (4/6)

32

Reputation

  1. Indeed, you are right. FANTASTIC, it is working now. Thank you so much!
  2. Yeah, this is what I had in mind too. I never touched /wire/core/admin.php. I have edited /site/templates/admin.php. When I open the ProcessWire Admin url a Internal Error shows up below the input fields. It is happening with PHP 7 and PHP 8.2
  3. @Robin S Thanks for sharing. Using the code above throws an unknown error when I login into ProcessWire. Is it still valid for ProcessWire 3.0.229? Fatal Error: Cannot redeclare _hookSessionRedirectModal() (previously declared in wire/core/admin.php:36) (line 36 of wire/core/admin.php)
  4. @taotoo, @bernhard, @Jan Romero Thanks for your clarification. Regarding 300dpi file size I was wrong. I did experience this kind of slowness and high CPU usage with a client project that I recently migrated. It turned out the previous owner did not define any image scaling. They used to export 300dpi files from Indesign with 20MB file sizes and users uploaded multiple images to the ProcessWire project. Approx. 100MB were loaded on every page refresh. After taking a closer look I managed to resolve the issue. Thanks again.
  5. You are right. 72dpi or 96dpi files do not matter. I do not see any difference choosing between client-or server-side resize. I am using a max width and height dimension. PW scales and compresses the original image from 7MB to 916KB. However the dpi a remains untouched. 300 dpi images cause bigger file size, bigger network payload with long load times. The CPU usage is noticeable higher instead of using 72/96 dpi files.
  6. How can I globally limit the max. dpi image size in ProcessWire? I have set max width and height for uploaded images and I also added a description with additional information. The image field is cropped and scaled in various sizes. However the image dpi remains untouched. Some users still managed to upload large 300dpi images, which causes massive server CPU spikes on every page reload. I tried to teach those users, but they simply don't care. 300dpi images should not be uploaded to PW in the first place. What is the best option to prevent users from uploading 300dpi images? What is your recommendation?
  7. Thank you. This is exactly what I was looking for! ...Way better UI experience
  8. Did you enable any PHP caching on your server?
  9. Using PNG compression for pictures might generate large files. Even with your black gradient try to export the original image as JPEG instead. The file size should be considerable smaller for all variations including webP files.
  10. My site paragraph format are barely readable and always cut off. How can I adjust the width for drop down? I tried to overwrite editor.css from the CKEditor moono-lisa skin by coping it to sites/modules/InputfieldCKEditor/ckeditor-4.19.0/skins/moono-lisa/editor.css .cke_combo__format .cke_combo_text { width: 275px !important; } However it doesn't work. This is not a solid solution due to changes or updates to CKEditor. width: auto; would be much better. What is the right way to fix the format width?
  11. Wow, This bug has been fixed with PW 3.0.200 !! ? ? @ryanThank you so much.
  12. Done. Thank you for your reply. Hopefully there will be a solution.
  13. Thanks for getting back to this issue. So far I did not find a solution. When I select and delete all or single variations, WebP files remain in the asset directory. This issue occurs with RepeaterMatrix and also in single PW image field. I think it is a ProccessWire bug? ?‍♂️
  14. @Adam Thank you for your in-depth reply. Perfect. That is a solid solution, even though I have never experienced any issue with your TfaU2F and TfaWebAuthn module and 3 Yubikeys. I do prefer the native ProcessWire way :-)
×
×
  • Create New...