adrian

That setting doesn't affect Tracy's behavior, but if Tracy isn't working it will provide info that you wouldn't have otherwise. Let me know how you go with reinstalling, or looking at those bullet points.

@ryanC Do you have PW's debug mode on? Any php errors being displayed or logged? Any errors on the dev console's Network tab regarding Tracy files not being loaded? Any issues with file permissions on the files within the Tracy folder after moving to new site? Any files missing from the Tracy folder? Can you replace with a fresh set from Github?

Try the purify() sanitizer. Also, in the Tracy Console, check out the testAll() sanitizer - very handy! d($sanitizer->testAll($str)):

@bernhard - the problem with the wiki is that you can't do a PR, which is why I went with Github pages (as discussed in the Tracy thread). The problem with Guthub pages is that don't support custom jekyll templates so you can't have a sidebar, which is really annoying. I could code up a page from scratch, but then we're getting into more work again. Honestly I am thinking about just putting all the docs in the ReadMe - that way they would also be available via @netcarver's module release notes. I would store the screenshot images in the /docs/ folder because I have that excluded via .gitattributes so the download would still be light, but the ReadMe within PW would looks really nice. Also, really easy to accept PRs for changes to the ReadMe file.

I think it's probably just because the changelog file for wireMailSMTP uses + 0.3.0 fixed code that broke backward compatibility for PW 2.4 and 2.5, brought in with the config cosmetics (0.2.6) + 0.2.7 @abdus fixed smtp password not saving whereas other modules seem to use: ### 1.7.0 (2017-12-12) - fix suppressing the "required" icon in the template editor (by reported by Robin S) ### 1.6.9 (2017-12-12) - PR merge: Different size buttons when editing a page #80 (by gmclelland) Yep, looks great now - thanks!

Absolutely - the best way to learn something is when you have to teach it to someone else!

Hi SamC - sorry you find it so confusing. I would love to revamp the "docs" in that blog post into a proper set of docs, but I just don't have the time. If you come across things you don't understand, please ask in the Tracy support thread. It has a huge number of tools, but the key things are the automatic reporting of errors, the dumps panel using bd() calls, and the Console panel. If those are all you get familiar with, that will be of great help.

It's a fantastic way to give editors a way to control page content without mangling things into an RTE. Also, if you happen to have any sites around where you have used PageTable fields for this and feel like an upgrade to RepeaterMatrix, take a look at the one click converter included in AdminActions.

Really minor, but sometimes the order of local vs Google drive packages is switched. Maybe it would be nice if they were always consistent?

Not sure if you can do anything about this. wireMailSMTP's changelog is not being parsed properly is it? Also, you have a Tracy bd() call on line 702. OT, but any reason you prefer: \TD::barDump() to bd() ?

No worries - it's changed in the latest version. Thanks for the feedback!

Just saw this when upgrading AOS. Doesn't seem right. I see that @tpr is using integer versions again, but 168 was also an integer, so not sure why it would be reporting like this.

https://www.google.ca/search?q=p+logo&source=lnms&tbm=isch&sa=X&ved=0ahUKEwif9PSKrIXYAhUZ0IMKHZ-3AZoQ_AUICigB&biw=1680&bih=930 There are so many similar looking "P" logos - what can you do

Once again another great use for a brilliant module! I am sure we haven't yet touched the surface of what can be done with it

I'll have a think about this one - thanks for the idea. I have implemented this in the latest version - please take a look and let me know what you think.

Do you feel like sharing your version at some point? Others might find it useful also!

Hi @tpr - thanks for your idea. I almost did that when building this feature the first time, but struggled to come up with the right UX. Been going around in circles for way too long on this and I am still not sure how it should look. I am attaching a version of Tracy that includes the admin ajax search feature embedded into the PW Info panel. It's rough in look, but it works and returns exactly the same results as the admin version. Please note that it actually only works in the backend of your site at the moment - some missing dependencies. I know this is not really what you asked for, but I am wondering what the best combo would actually be. Would you guys make use of an ajax search? Would it make sense to combine the ID and page search into one feature? Do we want edit and view links for results searched by name, rather than ID. Anyway, I am happy to implement something here - just looking for feedback on what you guys would find useful. TracyDebugger.zip

Don't forget about us non-webGL folks! Otherwise a blank page is definitely a sign of a very tiny agency

Thanks for considering the undo/review option. As for CustomUploadNames, I have adjusted the hook priority in that so you don't need to consider it now in AutoSmush.

@erikvanberkum - turns out @lpa had the same issue so I have added a workaround to handle that bug in the older version of PW.

Hey @kongondo - lots of warnings and notices. I am running php 7.2. I don't see any issue with The requested process does not exist - that sounds to me like the Process module wasn't installed properly, or the Admin > Blog page somehow has an incorrect Process assigned to. @Sebastian - can you check those?

Depending on how complex your needs are, the core does offer some support. Use something like this for the selector value for a page field: parent=page.otherpagefield That allows for ajax population of one select based on the selected value of the otherpagefield

If you want a non-default theme, I would recommend setting the config variable in your config.php file. $config->defaultAdminTheme = 'AdminThemeReno';

I have similar issues with this - they're all already so small, but I get the feeling that google penalizes based on possible percentage reduction, rather than actual bytes saved.

Sorry for taking so long to get back to you @matjazp - I just tested your svgo implementation and it's awesome! The only catch I have is with svgo itself. Sometimes it can break svgs - elements can get moved, etc. I am wondering if you have any thoughts about building in an "Accept Compressed Version" ? Maybe another alternative would be a "Restore Original Version" button that would removed the optimized version and replace it with the backed up one? The other thing I noticed is that if you are running my CustomUploadNames module the backed version keeps the original filename - would you mind changing it to use the new name instead please?