Soma

I changed to addHookBefore('Page::render',.. It still doesn't load the script.

No luck. :/

Still, the add error is gone but script isn't added. Any Ideas? <?php public function init() { $this->addHookAfter('Page::render', $this, 'loadJS'); } public function loadJS($event) { if($this->process == 'ProcessModule') $this->config->scripts->add($this->config->urls->ModulesSectionCollapse . "ModulesSectionCollapse.js"); }

Thanks Ryan, that's great. I thought there must be something like this, but couldn't figure it out yet (was too lazy). Now I'm trying this and It doesn't work with addHookAfter Page::render: Fatal error: Call to a member function add() on a non-object in /var/www/domains/zueblin.update.ch/site/modules/ModulesSectionCollapse/ModulesSectionCollapse.module on line 65 This error message was shown because the site is in DEBUG mode. SO I thought the hook must be different but can't get it work. addHookAfter Page::loaded etc... Can you give me a hint? Thanks.

Thanks Pete. Yes, I also thought about this after I've done the TOC. Here's a even more simple module that collapses the sections, and uses the sections titles to toggle the module table. The new ModulesSectionCollapse Module is attached. Edit: updated first post with github repo.

I think it's possible to override tooltips, not sure anymore. I just thought something custom that's delayed ~1 second and use a span or div that can be styled... you're right they can be very annoying. But then I just step back and think, but hey! they already can be displayed by using custom label fields in the template advanced settings... PW is a dream come true.

Hey, my first, just a little module to generate a TOC with links on top of modules page for overview and easing navigation. Not sure if there's already something similar planed already for the Modules page in the core. But none the less, it was fun to try out captain Hook Just cleaned and checked this baby in: https://github.com/somatonic/ModulesSectionCollapse

I just wished the page tree label link would have a tooltip that shows id and path/name when hovering... just figured it has a title attribute that acutally already shows the path. It just seems it takes ages in chrome to display them (2-3 sec). May a tooltip function to progressively enhance to show the html title attr would help for consistency and additional control? Now thinking , I would like to have it display the id aswell. (i know it's in the url of the edit toolbar link, but for the normal unexperienced user it could be handy) And why not have have all important ui links have short hints as to what they might do? Those of course should then be translateable (is that even a word? ) when having multilanguage admin.

Just installed, nice idea! Thanks for sharing. But, wouldn't it be an bit of a issue to redirect visitors to the PW login page? It's not what I would expect, the /processwire/ path that's usually something you want to hide. Nice would be to just not render the page and put the put a message instead (that can be customized), or maybe even define a custom page/path to redirect to. And let the /processwire/ still accessible for those who know.

Very cool module! Thanks a lot Ryan! I'll have a look and try out soon.

Thanks Ryan for the good news! Keep up the good work, and congratulations on pw21! So far I'm really starting to love PW! I've done quite some things now and I just love how simple but very powerful this nice little software is. I'm prototyping a new website and it's just amazing how simple and fast the PW part is, so I can concentrate on the html, js and css. Building this way is actually fun! github is great , I'm quite using it alot and I've just submited an issue to PW21. I wish you and PW all the best for the future, and I hope many many other developer and designer will join "us"... let the crowd in

Thanks Ryan, I will inform you when it's going live again.

Hey cool, I'm from Schaffhausen and do work in Zurich. So yes, we're neighbours. Nice to meet you here on a "US" forum!

what about moving pages in the tree?

Sounds great, this can be very helpful for creating multilanguage sites. Many thank for working on that. I surely would like to help test when a first release candidate is ready. I'm working here in Switzerland. Having 4 native languages, most projects require multilanguage sites.

That looks great so far, seems very useful for prototyping... thanks for this great new inputfield, I will try out and help test.

Ryan is an animal Also wanted to say thanks, I will surely check this out soon.

It's not live yet I'm still working on it at some parts, but I'm porting a selfmade online art gallery I did for my mom to PW21. I'm loving it how easy I could transfer all the images/content via bootstraping the API. Even the guestbook is imported using "comments" module. http://dev.urlich.ch

Maybe I'm missing something, but whether I turn on or off the option "Show filtering options in Fields list?" under /processwire/module/edit?name=ProcessField I can't see it makes any difference in the setup field list... the "Filters" are there always.

I understand your point and agree, but are you really making assumptions if the user encounters the page tree as it was as he left it? If, then it should be not overriding the breadcrumb navigation behaviour, just when the user goes back or klicks on "Pages". I think it may best to have it as an option.

Again, although it seems obvious and makes sense to use breadcrumb, but still it's something that's "hidden" (that tree open functionality) to the user until he knows how to best navigate in pw. I'm just thinking if there could be a way to make it more obvious... (lol may it's really just poor me failing to see the most obvious)

Just looked at the ProcessPageList.js and seen that there's already something: // ID sof the pages that we want to automatically open (default none) openPageIDs: [] I thought it's especially useful in general at the page tree in the admin, everytime the user returns from editing a page to the page tree he often needs to do something in the same place or edit the next page in a sublevel or create a new page below... now going back and thinking about it again... now as you mentioned it, I discovered that clicking in the bradcrumbs parent link it gets me back to the page tree and opens it... really nice! Haven't payed enough attention to that yet I guess - I must be dreaming, cause I thought last time I klicked on the breadcrumb parent it got me to the parent page's edit page!?.. Anyway this puts it in a different light. I'm not sure anymore if state saving would really help as much as I thought, or as to not support this bad behaviour of returning to the admin page tree via top menu or breadcrumb "Pages"... and forcing the user to use the breadcrumb may makes sense. What are your thoughts? Would it be distracting from the "good practices"? Edit: It may sometimes comes in handy, many people (as me) are used to use browser back intuitively ( you may enter a page editing just to look and use browser back button, or backspace)... it's just people are so used to something it's hard to train them differently... Also seeing it from a end user perspective it could help.

I think the admin page tree would benefit from a state saving feature. In jsTree for example you can on state saving which uses cookies to save a hash with open nodes. If there's already a option somehwere I missed, I'm sorry. Else do you think we can implement this feature?

what if one could specify "editable pages" and "working dirs" on a user and or role basis? I've yet to come across a user management system that's simple to understand, logic, enough flexible and still working bugfree/solid... , so i'm excited about what is there already even I understand, ... buuut maybe also there could be a little more... I work with a CMS that does allow to define access controlls on a per user, role, page and template basis. Whilst it gives great power it can get very complicated and out of control quickly... something's always not working... I think there should be at least a way to additionally give single pages users acces or give users access to single pages/dirs, without the need to create duplicates of templates just for single users.

I encountered a similar problem when putting a local codeigniter project to a server. I think I had to generate a new user pwd, although using same name/pw... and it worked again. but never couldn't make up what the problem was,must have been a encryption key / salt problem somehow...