StanLindsey

Merry Christmas/Happy Holidays to everybody in the PW Community!

tpr, this is awesome stuff.

I've just submitted a pull request to you Rudy, based on Robin's code, to add the ability to compile all updated sass files. You then include your style sheets as you normally would, pointing to the generated .css file. You can now either use the SassifyAll() function anywhere or head to the admin and click 'compile sass' to compile all your assets at once. This is my first input to a Processwire Module so let me know if I've done anything wrong, or if I've stepped on anybody's toes!

Thanks Apeisa, great work!

Also - does anybody using Padloper have any reviews or thoughts regarding it?

Any update on Padloper for PW3? I've got a project I'm looking forward to using it with =D

I just did it on a fresh install and have the same problem. It places the NavItems not on "Pages", but on the first page item in the admin page tree. I want to add something above "Pages" (a dashboard), but keeping these navItems in under "Pages", as designed. (I love AOS otherwise, great job)

Ah that makes sense, wondered what was happening with </body>. I might take a look too then. Just to note that I'm not using any other plugins enabled at the time of that screenshot, the dashboard is simply a standard page in the tree.

Anybody tested this on v3 yet? Looking at purchasing for a new project. Also @apeisa - may I ask what is on the roadmap? As the last release was in January.

Hi @tpr - loving the module. I'm trying to figure out how you append the NavItems with this line: $event->return = str_replace('</body>', $items . '</body', $event->return); As it puts those quick links as a child to the top most admin navigation, when I'd like them to appear in the Pages submenu. On another note, the style of the parent menu is odd when a sub-child is open. (See Modules in the image) This is due the classes 'current' and 'open' being added to the css. Great work though!