howdytom

@zoeck Thanks for sharing. A paid module would be okay, unless it is well maintained. A media manager is an essential tool. In case the module support dies, you can’t easily replace it, which is a huge drawback. @TomPich Thanks. Actually this is how I set things up. It’s okay for a small landing page. It get’s easily messy to collect images in a media page. How do you structure an artist page with repeating images, e.g. a hero image on the front-page, artist profile page with the same image, artwork sub pages and a related article section? I have uploaded the same image multiple to the Repeater Matrix. What is best way to implement a partner logo section which is re-used across the site but in different order and combinations? E.g. 5 partner logos are displayed on page A, page B, page C, page D. But on page E and F 2 more partner logos should be displayed, besides the previously uploaded images? From a content editor point of view, I would like to add or select images to the page I am working on. Ideally re-using a repeater matrix and select an image I do use across my site. Maybe I don’t get ProcessWires Page concept, yet.

How do you structure repeating content in ProcessWire without uploading images multiple times? Let’s say I would like reuse an image field multiple times on my front page in various section e.g. in a blog post, within a image slider, image gallery page and also as variation on sub pages. e.g. author box. Since ProcessWire does ship with a media manager, I don’t know how to deal with repeating elements. Currently, I am using a Repeater Matrix. How do you organize fields for editors? Any replies are highly appreciated.

Does anyone use a Yubikey with Safari or NFC on iOS? Something must have been changed with the latest Safari 17.4 or iOS Update. When I try to log-in using macOS Safari or NFC on iOS Safari/iOS Chrome, there is no longer an option to select Security keys. Whereas the Security key option still shows up on Google Sign or GitHub. Security key shows up on GitHub: Security key option is missing on a PW site using the WebAuthn two-factor authentication module.

Indeed, you are right. FANTASTIC, it is working now. Thank you so much!

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

@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)

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

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.

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?

@dynweb Thank you. perfect! Issue solved

Thank you. This is exactly what I was looking for! ...Way better UI experience

Did you enable any PHP caching on your server?

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.

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?

Wow, This bug has been fixed with PW 3.0.200 !! ? ? @ryanThank you so much.