tpr

Sorry, I missed that part, then it's not an option for you.

FYI I have added this plugin to AdminOnSteroids module and will be available in the next update. Works fine in the admin with the latest PW, on the frontend it needs manual initialization (of course).

Some really smart time-saving techniques here! And lazy-loaded as well, nice.

No harm done of course but on mobile there's usually no "hover".

Geil! Why the arrow icon when hovering the expanded mobile menu?

Ok, thanks for InputfieldFileSorting this out ☺️

I think @WebMaster is looking for a way to sort (order) items and not to filter them. There is a solution by @bernhard that is not merged into aos, you can find it somewhere in this topic too.

As I remember there was (is?) an issue with tooltips feature set to Overlay type. Could you check if this is the culprit?

I wasn't sure but after checking I can say that AOS supports additional fields added by Image Extra module

Perhaps it would, I will check if this would work as intended in my adminonsteroids module, unless someone has something against.

Nice! Perhaps it's only me but I like the triangles better than the photos

Yes, having a separated DOM inside the main DOM, with its fully separated CSS.

Shadow DOM sounds like the ideal treat for Tracy bar encapsulation headaches, when it will widely supported: https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM

Offtopic: if you happen to use adminonsteroids module you can enable a simiar tweak: https://github.com/rolandtoth/AdminOnSteroids/wiki/Misc

No, they ruined it.

Looks nice and handy, thanks! Don't wanna steal the focus but when I bardump long (bdl) an object, eg. a field, the dump looks like this - the pink text should be above the filename:linenum I guess.

In the upcoming 1.7.4 version there will be a new tweak for the Logs page. The helpers field on top can be expanded by default, and the select box of Actions replaced with radios. I don't really get why the actions are in a select, radios are easier to use. I've requested this change in the core on GitHub (and got a few likes there too) but so far there's no response.

I will check the procache forum, thanks! (I need a different account there). Seems like I missed the - 1 for the indexOf, thanks for the help.

Yesterday I've fixed a few things mentioned earlier. Some remarks: For me it works fine. Does it happen on other sites too? Others? Yep, navItems are hacky because there is no hook to add menu items properly. To add items only to specific pages would require to rewrite the whole thing, but my biggest concern is how to make the admin for it simple. I don't remember why it's there Sure, when the time comes.

I meant CMSes that can output the whole site to a different server. One example is WordPress + Simply Static plugin.

No, things are not that obvious. We are using other tools that allow separating admin and frontend to different servers, so even if fronted gets hacked they can't get hold of sensitive data but only static html files. This is something pw can't do afaik, perhaps with procache but I haven't tried that workaround so far.

No, I haven't dealt with every detail yet, mostly only with the issues you reported here and on github. I do not use pw nowadays too much and even if I do I use the Reno theme so I cannot spot all the issues. But I think the majority of them are easy to fix, apart from the fact that now 3 admin themes are there to check which slows down things. I plan to iron out the known issues in the following weeks.

Thanks, I'll check all the issues and fixes when I finally get out of this less productive holiday season

Thanks! Use the code you find there with caution, it doesn't always follow the best practices Plus unfortunately your quote is also valid when changing a word in it: When your site is doing something weird and you can't remember for the life of you how you did it, check AOS first

Check out AutoSmush module for image optimization, with that you can easily optimize images that google pagespeed accepts in most of the time. Usually I can get pagespeed "green" values and that's where I stop optimizing, unless there's something trivial I can solve easily. The more optimization trick or workaround you make the less maintainable your site will become, so there is a point you better stop. Page speed analyzers are only indicators, not standards, this is something the so-called SEO experts usually get wrong