taotoo

With method 2 htaccess should rewrite it from webp to jpg shouldn't it? Assuming that is what you're expecting it to do, I found the example htaccess code didn't work for me. But I found that the code below did work (of course YMMV). RewriteCond %{HTTP_ACCEPT} !image/webp RewriteRule (.+)\.webp$ $1.jpg [T=image/jpeg,E=REQUEST_image]

FYI it works fine for me on my Android phone in both Chrome and Stargon (not sure which engine the latter uses).

Maybe you could see if the control panel also displays the output of php.ini somewhere, and see if it matches those values. You could also create a php.ini file, and see if those values match. I might also try uploading files of various sizes around 75mb, have the browser inspector open to see if there's any indication of when it fails, and time the failure point to see if it's something like 30s, or perhaps a multiple of 5 or 7.5 in case it's related to CPU time and the server has a multicore CPU. I have a similar issue when creating variations - I get the endless spinner if the creation takes longer than 15s on a dual core server.

I think "n" is simply an instruction to type the number of results that you would like to have per page in place of it.

I had something similar when using the Title field in a repeater. I'm not sure if it's the same issue or not, but I think I solved it by going to the field's Access tab, turning on access control, and assigning the view permission to guests.

Annoyingly I've just revisited the website and it's no-longer doing it! I'll check it again later. The GPU is a GTX750, and the display is low pixel density, with no scaling involved.

On Chrome (and Firefox) on Win10 I do notice that with the browser window wider than about 1,000 pixels my mouse cursor slows down. The wider the window, the slower it gets. At 2560px wide, the mouse is at about half speed. This is with a modern CPU and also a GPU.

This works great, thank you so much! I noticed that your code is based on a a PW v2.7 Pages.php file. My existing PW v3 Pages.php file had in it only this cloning code: public function ___clone(Page $page, Page $parent = null, $recursive = true, $options = array()) { return $this->editor()->_clone($page, $parent, $recursive, $options); } I just pasted your code in below this, and it works. Not sure if that's what I'm meant to be doing or not. Where does PW v3 keep all its cloning code? I found that I could just add the code below to the hook - it seems to prevent the contents of the field being copied over to the new page: $clone->image = null; $clone->save();

Ah - that's how to do it! I was looking in ProcessPageClone.module and couldn't figure out how the files were being copied... Thank you very much for the comprehensive answer, I'll try it out!

I'm using a hook (similar to @bernhard's below) to add a Clone button when editing pages. Is it possible to clone the page, but without also copying over the image files? I tried adding this code towards the end of the hook: $clone->image = null; $clone->save(); This successfully prevents the contents of the image field being cloned, but PW still copies the image files themselves into the new page's directory. I also looked at the API documentation, but it doesn't seem to provide an option for this. I want to avoid copying the images as there are typically about 20 files that get copied, which takes about 10 seconds on the shared server. Additionally, the first thing the client will do after cloning the page is delete the images as they will be unneeded.

Might you make your module available @Noboru? I'd love to give it a try.

Is it trying to display thousands of pages and timing out? If so maybe an input type such as Page Auto Complete, which doesn't load all of the pages at once might work.

If using server side resize, a webp version of the uploaded image is automatically created (at least if the uploaded image is larger than the field's max dimensions). But when using client side resize this doesn't happen. Is it possible to have a webp version automatically created while using client side resize (without resorting to creating a variation)?

Not that I know of, though maybe it's possible to create a module to do this. You could instead consider using Lister. If you go to Pages > Find, you could save various searches as bookmarks, then add shortcuts to those bookmarks which would be used instead of the Page Tree. You can have different columns for each bookmarked search.

You can add more fields to display by editing the templates for the relevant pages, clicking the Advanced tab, scrolling down to "List of fields to display in the admin Page List", then entering multiple fields such as {title} {a_field} {another_field}. You can also mix in other text, such as {title} | {a_field} > {another_field}.