adrian

Thanks for spotting the left over LIVE reference. Actually between 2.6 dev and the releases version of 2.6 of the Tracy core, they actually changed LIVE to LAZY. LIVE still exists as a separate option but it still has some downsides. In most cases LAZY is better. You can read more about it here: https://github.com/nette/tracy/issues/344#issuecomment-468123490 Your data is still truncated because of the default maxDepth of 3 which is tweakable in the module settings. With lazy it's possible to have a much greater depth without performance issues so maybe I will up that at some point. You can of course still use db() or bdb() or bd($var, [10]) or one of the other combinations to up the depth. You'll find that with the new LAZY approach you can actually do a bd($page, [10]) and it won't cause an out of memory error like it would with Tracy 2.5. Hope that helps. If you have any more technical questions let me know, or perhaps address them to @dg at Nette.

@Pete - maybe you have already noticed this, but https://processwire.com/talk/discover/unread/ has black rather thank pink links.

Looking at one of my Process Modules, I use: 'page' => array( 'name' => 'admin-actions', 'parent' => 'setup', 'title' => 'Admin Actions' ), The parent has no slashes and will be relative to admin.

Your link to Cerberus is incorrect: https://tedgoas.github.io/Ce vs https://tedgoas.github.io/Cerberus/

They're not actually uninstalled - just do a Modules > Refresh and you'll be back in business with all modules settings as they were.

I assume you have uninstalled and reinstalled your module? This is needed to create the admin pages. Sorry if this is obvious and you've already done it.

Not much time to respond, but I bet the pages are created - check under Admin in the tree. It's probably a caching issue - do a modules refresh and logout and back in again. If you have Tracy installed, you can also just use the "Clear Session & Cookies" option in the PW Info panel. Hope that helps. PS I would definitely recommend using the module info pages approach - it handles everything for you, including uninstalling.

Thanks for pointing to that module @Sergio - I use it on every site. It would be hard enough for me to remember to change the page name to match a new title, let alone expecting a client to do it. Given that PW has the core Page Path History functionality, I rarely see the need to not change the name when the title changes.

Glad it all worked out - we've all done similar things ?

Home > Settings - color and icon stretching.

Soma and Robin S are missing their avatars - I am sure there are many more also.

Color for "ipsMessage ipsMessage_info" class is old:

Thanks Pete! Avatars are also stretched in the Notifications panel. Another thing I noticed is that all out locations have "Location" prepended - eg: "LocationBuckley, Wales"

bd() will work in site/init.php and site/ready.php - your OP code works for me in both of those files. You mentioned you had tested there already, so I didn't think about it, but I think @Robin S might be correct about what the problem is.

This is all @tpr's hard work - he has just added a search/filter implementation using his awesome filterbox.js - be sure to check it out and Star it! Note that in addition to filtering, if you hit "Enter" it will load the first matched file. Thanks again Roland - this is very cool!

Sorry, I wasn't suggesting setting everything up again - just a clean PW install with no modules, pages, templates etc just to see if it works. I imagine it will, but thought it might be a good sanity check in case there is some weird server setting somehow interfering - although I can't imagine what and you mentioned that you tried on your local dev as well and it still doesn't work.

I think you need to try disabling all autoload modules - Tracy's Module Disabler panel make this easy. If that still doesn't work, then try a fresh PW install just to rule out anything else.

What page are you viewing to test this? I don't think it should matter, but just curious. Other than that, I wonder if you can try updating to the latest PW version, just in case.

Those numbers are line numbers in the Page.php file. It suggests you are running an older version of PW. Page::render is a unique hook in that it actually comes from the PageRender.module file. Perhaps you could try hooking into PageRender::renderPage and see if that works.

You could make use of http://modules.processwire.com/modules/process-admin-actions/ and build a custom action that lets you choose a Page Table field and then a page to add to that field. Or you could use http://modules.processwire.com/modules/fieldtype-runtime-markup/ and build a page selector field just above or below the Page Table field and on pag save, process the selected page and add it to the PT field. You could also hook into InputfieldPageTable::render and add the page selector interface there. Lots of options really ?

The code in that link I posted hooks into the rendering of the page table field in the backend and automatically adds existing child pages. Is that not what you are looking to do?

You could try Page::path or maybe one of the other page hooks. Don't forget Tracy's Captain Hook panel for easily finding hooks for a particular PW variable / object / class.

No problem here with your code. I'm actually not sure what to suggest at the moment. Do other hooks behave any better?

See at the bottom? I just realized that you need to have $config->advanced = true; set in your config.php file to see this. Perhaps that also affects Tracy's ability to delete it?

You can remove the permanent flag on the advanced tab of the field's settings. The other option is Tracy Admin Tools panel - open the field settings page for the problem field, and click the delete field button - this handles removing it from the fieldgroup/template and deleting it, all in one action.