adrian

https://www.meuter.de/blog/wieso-processwire-als-content-management-system-cms-oft-die-bessere-alternative-ist/

https://processwire.com/api/ref/session/force-login/

It should be easy enough to remove the first one when adding a new one by stripping off the ? and everything after it. You can hook into Pageimage::crop

Sorry for the delay in response to the CustomUploadNames issue - I am on semi-vacation, but I will try to take a look at that soon so maybe that will address your needs?

I am not seeing any issues here visiting the modules page (or any other), but I am curious what Tracy panels you have enabled. Perhaps it is one in particular that is causing the slowdown. Also, is it just the modules page that is slow?

Please!

A couple more settings to help out those of us with "tired" eyes ? These will be pushed in the next few days. I am still messing around with the code completion stuff. Unfortunately I don't think showing the doc comments like I posted above is going to be a good idea - it's a 2MB payload and even though I am not really seeing a slowdown here on local dev, it still feels wrong and will probably impact performance on a live server. I do like the idea though of an API learning interface like this, so maybe it's something for a dedicated panel where speed doesn't matter. Any thoughts?

I am happy including all the themes - only the selected one is loaded, and they only add 135kb to the Tracy module package so it's really not an issue. Here's what will be coming soon. You can see I have selected your desired iplastic theme in the config settings and the Console panel is styled accordingly. This will also control the File Editor panel's theme as well.

Thanks but it's super easy. Just before I do I need to decide how to facilitate the various Ace settings like I mentioned above.

Is this going too far having the doc comment displayed? It's a good learning tool. Maybe make it optional, or do you guys think just leave it out completely?

I haven't packaged the other themes with Tracy yet, but I can do so if you guys are interested. I initially went with just one theme (my favorite) because I wasn't sure how much use the Console and File Editor panels would get, but given their popularity I think it probably makes sense to include all the themes so you guys can choose what you prefer. I guess the next question is to figure out whether you guys want to be able to adjust all ACE editor settings via a textarea with key:value pairs or whether I should provide the key settings I think you might want to adjust as dedicated fields in the module settings like I have with the tab size, type and show invisibles settings. What does everyone think?

If you hook after Page::render you can assign $event->return to a variable and use that.

Agreed - I don't want either the Console panel or FileEditor panel to slow down at all - I'll make sure that any autocomplete/snippet stuff I add doesn't cause any slowdown. Glad that in general you enjoy using these tools. The best way to change the editor color is to use the built in themes. I actually haven't included any other themes with the Tracy package, but I could easily add these and create a new module config setting so you can choose the theme - there are a lot of options - check out the kitchen sink demo (https://ace.c9.io/build/kitchen-sink.html) and try out the Theme dropdown.

I am curious what you discover testing this. I haven't ever played with the noFields option. If is doesn't work out fast, you might be better off with direct DB manipulation of parent_id field, but if you do take that approach be aware that you'll also need to update the pages_parents table as well. Sorry I missed your more recent posts about the discovered bug. Thanks for digging into that!

"parent" is not the name of a field. If you are trying to set the parent of the page you'll need to do this: $page->parent = 'x'; $page->save();

Also just got this working, all generated automatically from the currently PW install, so it's always up-to-date. Do you guys think you'd make use of this?

@cosmicsafari - please check out my fork of the AssistedURL module: https://github.com/adrianbj/processwire-fieldtype-assisted-url It stores links as IDs so links are updated if names are changed.

Or perhaps this is even cleaner for the plain PW variables when they are not actually snippets:

Yeah, already done on my dev copy - all PW variables are automatically added to the autocomplete. Agreed - I am working on this - I don't necessarily want to disable php autocompletions completely, but trying to tweak the triggering so it's not invasive when you don't want it.

What do you guys think of me adding things like this:

Ok, I have implemented the ability to link to your own custom snippets file: If you're using a Github Gist, make sure you use the https://rawgit.com/ service because the raw file from Github is served without the correct mime type and won't work. The format of the custom snippet file is like this. Note the getCustomCodeSnippets() compared with the core snippets file which uses getCodeSnippets() var getCustomCodeSnippets = function() { return [ { name: "pwfind", content: "d(\\$pages->find(\"template=\${1:basic-page}\")->each(\"\${2:title}\"));", tabTrigger: "pwfind" }, { name: "pwforeach", content: "foreach(\\$pages->find(\"template=\${1:basic-page}\") as \\$p) {\n\td(\\$p);\n}", tabTrigger: "pwforeach" } ] }; At the moment the custom snippets file is PHP only. I don't think we will ever need other languages for this. I have also added in the ACE core snippet files for other web related languages so if you use the File Editor panel for JS, CSS, etc, there will now be a bunch of useful snippets for those languages as well. If you want to peruse the available ACE core snippets, the best way is probably here: https://github.com/ajaxorg/ace/blob/master/lib/ace/snippets/php.snippets You can also check out the snippets for other languages in the parent folder of that file.

I'd need to look into this a little more to figure out how to get the label if you have defined a manual value, but if you don't define a value, then it automatically returns the label: Would this work for you, or do you need to specify a value for each option? Got to sleep here, but this shows that you could parse this yourself by grabbing the field's colnoptions setting. Not exactly elegant, but it'll work..

I was actually thinking along those lines as well, but I do want to encourage PRs to main file that comes with Tracy as well. But yeah if you want to add support for pointing to a Github gist URL, or any other URL I suppose, I think that would be a nice addition.

OK, just released a major new version: 4.12.0 1) New Title/View link in Dump tabs, so ID is edit link and title/name is view link 2) New PagePermissions section added to PW Info panel: 3) New PHP and custom PW autocomplete snippets added to the Console and File Editor panels. Here's one example, but there are others in the posts prior to this one showing general PHP snippets. Currently there are two custom PW snippets: pwforeach and pwfind - I'd love to hear what you guys want to see here. If you have new snippet ideas, please take a look at: https://github.com/adrianbj/TracyDebugger/blob/master/scripts/code-snippets.js and feel free to send PRs with new additions. 4) Ability to dynamically resize the font in the Console and File Editor panels with: Increase: CTRL + +/= Decrease: CTRL + -/_ Reset: CTRL + 0 5) Changes to the way the Console panel divs are structured and resized - please let me know if you see any issues with the results panel protruding beyond the bottom of the panel or any other issues. It's still not perfect, but it's breaking my brain ? 6) Some minor Tracy core updates and also general cleanup of many of the custom panels. Please let me know if you have any problems with this new version, or ideas for improvements!

Hey @bernhard - sorry I forgot to respond to this before. This is certainly a possibility if there is demand. The advantage of course is that panel authors can maintain the codebase for their panel completely without relying on me to handle PRs etc. The downside is that new Tracy users needs to hunt around to find third-party panels so if we take this approach we'll want to make sure to list them all on a dedicated page on the docs site. Let me know if anyone out there is interested in this.