adrian

Hey @flydev - I was debugging some Notices in my code and had Tracy in strict mode (via the Panel Selector) and came across this. Let me know if you need any help reproducing.

http://modules.processwire.com/modules/admin-restrict-page-tree/

@neosin - not sure how ML imports work with this module, but thanks to sponsorship by @bbeer BatchChilldEditor supports it, although it work differently to the way you described - you need one CSV file per language.

There is now $config->tracyDisabled = true;

Actually something interesting to note is how slow the Debug Panel actually is: 262ms. Typically mine shows somewhere between 15 and 35ms. Not sure if that's a contributor on your site, or indicative of the problem.

Sorry @kongondo - me again I am noticing that the renderMarkup() method is called many times on the currently edited page and it's also called on page reference fields on the page being edited. This makes for a lot of calls to this method that don't seem necessary as far as I can tell. Do you think this can be improved? As an example, I put: bd($page->id); at the top of that method and saw this: I am currently editing page 1100, but there are a few page reference fields which are also showing up in that list. Thanks for taking a look!

I still think it's nice to have even for short snippets, but maybe that's just me? If nothing else it lets you actually use the tab key to indent which you can't do in a normal textarea.

It would also be good to have: $f->rows = 20; or even make it configurable. One other thing - because InputfieldAceExtended is not in inline mode, you need <?php to force code highlighting, but your module doesn't allow this. Would you mind stripping out any <?php that is added so that this works? This should do it: $str = eval(str_replace('<?php', '', $this->runtimeFields)); $str = eval(str_replace('<?php', '', $field->runtimeFields)); One each for FieldtypeRuntimMarkup and InputfieldRuntimeMarkup. Thanks!

Hey @kongondo - would you consider adding this to the module please? $f = $this->modules->isInstalled('InputfieldAceExtended') ? $this->modules->get('InputfieldAceExtended') : $this->modules->get('InputfieldTextarea'); in the ___getConfigInputfields method? Thanks!

Hey @flydev - did you manage to look into the issue I had with Google Drive not adding more backups after the defined max limit was reached? Thank you!

Hey @kixe - curious if there is a reason you chose to fix this rather than switch to jumplinks? http://modules.processwire.com/modules/process-jumplinks/ Is there something you prefer about this module, or just that you didn't know about the new one?

Just came across this need for the SEO module as well. I have posted this request: https://github.com/processwire/processwire-requests/issues/170 Until there is some progress on that, here is my hacky solution. I am sure it could be improved, but it works for now. $this->addHookBefore('ProcessModule::executeEdit', function($event) { if(!$this->wire('user')->isSuperuser() && $this->wire('input')->get->name !== 'MarkupSEO') { throw new WirePermissionException('You do not have permission to configure this module.'); } }); $this->addHookAfter('ProcessModule::executeNavJSON', function($event) { if(!$this->wire('user')->isSuperuser()) { if($this->wire('input')->get->site === '1') { // note \/admin\/module\/ - if your site admin is at /processwire/, then use: \/processwire\/module\/ $event->return = '{"url":"\/admin\/module\/","label":"Modules","icon":"plug","list":[{"url":"edit?name=MarkupSEO","label":"MarkupSEO","icon":"gear"}]}'; } else { $event->return = null; } } }); That results in this - Modules > Site contains just the SEO link and all the others are empty. Thanks @Robin S for the headstart on this!

Thanks @neosin - it should be fixed in the latest version. Let me know if you find any issues.

Hey @teppo - no idea why, but logins are now showing fine in Chrome. It's weird because yesterday it wasn't just my login attempts that were showing JS disabled and no flash info. I'll keep an eye on it. Sorry to bother you!

Yeah it really is an incredible improvement when you don't need all the stuff associated with a full PW page object.

Hey @bernhard - new version is much better - thanks. I tested with 5000 pages and it is an order of magnitude faster than a regular find()

Hey @teppo - I just noticed that with Chrome, it is reporting that JS is disabled: It's fine with Firefox though.

If you go to a field's settings in the admin and then open the Request Info panel in TracyDebugger you'll see this. It's most of the settings available, but some like "required" doesn't show unless you have it checked for the field in question. Alternatively, also while visiting a field's settings, you can do this in the Console Panel:

Best way to search the modules directory is via the PW Info panel in TracyDebugger:

Just playing around with it now - so far looks fantastic in implementation. The only catch is that I am actually seeing slower response times. Take these two examples: VS Note that I am using the Console panels ability to only run the selected code. The ms values don't look good though for some reason - any ideas why?

That module is excellent and works great in PW 3 - if you look at the support thread, @netcarver has been active very recently.

Not sure, but this one does: http://modules.processwire.com/modules/process-email-to-page/ - not sure if it suits your needs or not, but might be worth a try.

Thanks for that - I have commented on your request and also provided a very simple hack this get it working right now by including the tracy core file in the index.php at the root of your site. It seems to work brilliantly - great for debugging PW core files even. Would be great if others could add their +1 to this please!

array( 'name' => 'markup', 'label' => 'Markup', 'description' => '', 'notes' => '', 'type' => 'markup', 'value' => '<strong>Test Markup</strong>' ),

Maybe post a link here so others coming across this can go give it a thumbs up!