adrian

New tab/panel isn't hard to do at all, but I wonder whether just having that section always expanded would be ok/better? There are so many options and ways to present info that I am not totally sure the best option yet. I'd really love some thoughts from others about what they think they would use/access most often. Perhaps I could add several PW tabs/panels with different elements on each. Anyone have any ideas on what else they would like to have accessible and what should be grouped with what? EDIT: I have just made the Page Info section open by default so a hover over the PW tab is enough to see that info. Still amenable to making separate tabs/panels if that is the consensus though.

Actually I am, and have been for 18 years now, but that is a very different kind of love

Sorry, this is just too much fun Just added a Current Page Info section, with links to edit the page (from the name), edit the template, and open the page tree with this page expanded to show the children (from the number of children).

Thanks everyone for the great interest in this module! I have just added 2 new sections to the PW panel that shows details of all fields on the current page. I would love to hear from you if you have any ideas for other sections/info that you would find useful to have in the PW panel. List View Shows basic details with the name linked to the edit page for that field: Object View Shows the fields object - for details of each field, expand the "data" section:

Thanks Ivan, there are several options - Firebug is actually something I haven't implement yet in this module. It requires an additional package which I haven't included. I figure that most of us are on Chrome, so didn't bother with it yet. But if there is interest, I will definitely take a look. I should have pointed to the best of the Tracy docs: https://doc.nette.org/en/2.3/debugging - for some reason the ones on the main page don't include the barDump() option yet. You can use: TD::dump(), TD::barDump(), TD::log() I also implemented some aliases - d(), bd(), l() as very short options for lazy typists, but not sure about keeping these due to possible name conflicts. Anyway, let me know if that links helps and if you have any specific questions.

This should do it - just change "body" to the name of the existing field that you want to insert before. You can of course change insertBefore to insertAfter if that is easier/needed. if($page->template == 'service-type') { $f = new Field(); $f->type = $this->modules->get("FieldtypeRangeSlider"); $f->name = 'servicetype_' . $page->name; $f->label = 'Service-Type ' . $page->get('title')->getDefaultValue(); $f->set('suffix','%'); $f->set('tags','servicetype'); $f->set('icon','fa-sliders'); $f->save(); $existingField = $page->template->fieldgroup->fields->get("body"); $template = $page->template; $template->fieldgroup->insertBefore($f, $existingField); $template->fieldgroup->save(); } Here's a relevant section from the core ProcessField module that shows this in action: https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/modules/Process/ProcessField/ProcessField.module#L1850

Thanks to a bug report from horst I just committed a new version that fixes a Windows directory path issue. He also pointed me to another problem which is turns out means that this module currently only works with the 3.x branch of PW. I will look into supporting 2.x, but for the moment if you want to test, you will need 3.x or you can probably make it work on 2.7 if you uncheck "Show ProcessWire Panel" in the config settings. You'll miss out on that functionality, but hopefully everything else should work.

I love SVG Take a look at caniuse.com for the list of browser support: http://caniuse.com/#search=svg - I agree with @Mike Rockett - if a browser doesn't support SVG, then I don't support it. If you are going to allow your editors to upload SVG files, be sure to install the SVG validator: http://modules.processwire.com/modules/file-validator-svg-sanitizer/ because they can be a security risk.

Tracy Debugger for ProcessWire: https://processwire.com/talk/topic/12208-tracy-debugger/

Tracy Debugger for ProcessWire The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger Modules Directory: http://modules.processwire.com/modules/tracy-debugger/ Github: https://github.com/adrianbj/TracyDebugger A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.

I think I just modified the ImageExtra module to add it there. Have a go and if you are still having trouble I'll take a closer look.

I don't think it was ever in the modules directory, was it? You can get it from here: https://github.com/ryancramerdesign/ProcessWireConfig

Thanks to a stack trace from @tpr the warning has been fixed in the latest version. I also corrected an issue with the content protection check that may not have been working as expected for child pages with completed field content, so you may find that you need to check that config setting now where you may not have before, depending on your use case. I also added some more detailed notes about what this default mode means. To be honest, I always check to disable it, because otherwise it limits deletion of pages in edit and replace modes in many situations, but I still think it is an important default setting.

Thanks - any chance you can do a debug_backtrace() to see what is calling that line in Page.php

Ok, I have tried with a ML setup and still can't reproduce. Could you please confirm what link 780 of Page.php is? Is it this commit: https://github.com/ryancramerdesign/ProcessWire/blob/e3d6b894c27b5fed8d1ffd088b79d9c79b7e79ec/wire/core/Page.php#L780 I think that is the version from 3.0.6 - it was last updated 5 days ago, which should be before the 3.0.7 changes. Thanks!

I'm not seeing that here - is this in edit mode? Are you deleting with the trashcan icon next to a page, or using the modal edit and deleting there? Or are you using a different BCE mode?

Thanks for the report - can you please try the latest version I just committed and let me know.

Quite possibly - have you checked that the $eventpages array is containing the pages you are wanting to delete? What about if you add "include=all" to the selector?

A really cursory look suggests it's because of $pages->trash - remember $pages is not available inside a function. Try wire('pages') like you have above.

It sounds like it is an allow_url_fopen issue. Edit your php.ini to set it to "On" and the module should work fine.

Not specifically - I thought about that, but AFAIK, only superusers can see/edit the Admin page tree anyway, so I don't think it should matter, but please let me know if you discover otherwise.

Thanks for the report and sorry about that - looks like I introduced a bug in my commits from yesterday. Should be fixed now in the latest version. Please let me know if you still have any problems.

Yes they are disabled by default, but I just added a new option under Content / Deletion / Protection to enable BCE editing of the Admin page branch. Obviously this has the potential to completely break a PW install so use carefully at your own risk

Just incorporate one of these: https://gist.github.com/jakebellacera/635416 https://github.com/hising/ics-generator Have a go and drop a line if you have any problems.

No problem at all. Welcome to the forums btw. I am sure it will all start to make sense very soon!