adrian

Just wanted to say a special thanks for this comment - I am very glad to hear it's been so useful to you - several of you have also been instrumental in making Tracy as useful as it is, so thanks to you all as well!

Firstly, thanks to everyone who has suggested a Donate button - I am still thinking about this - not sure what my thoughts are yet. Just a quick update on the ProcesswireUpgradeCheck module and the Modules Disabler panel. Ryan has fixed the problem in the latest PW core commits today, although he is still warning (https://github.com/ryancramerdesign/ProcessWire/issues/1990#issuecomment-243401979) about disabling modules. See my next comment about @tpr's approach of storing module settings when uninstalling - as I mention, I am not sure this is without problems as well. I'd like to see a bullet-proof solution, although I am not sure there is one. At least for now, this panel should be a little safer than it was, but I am definitely keen to improve the approach used if anyone has any great ideas!

I'd love to see this - I don't think it is taking away from PW branding - in fact I'd be happy to see the PW logo in the footer instead. I think as well as making the client feel like it's a system customized for them, I think the actual key benefit is providing another key visual trigger to let you know what site's admin you are currently looking at.

Not to be a feature stealer :), but I wonder if an icon/label on the Tracy debugbar might be a decent approach for this? Maybe not if you don't have the debugbar enabled in the backend? Or maybe if you typically don't want it on in the backend, then you could just have this "PW Instance" panel enabled for the backend, but no others? I was thinking of adding a field where you can type the "label" for the current site - ie "Dev", "Staging", "Live" etc and then would be displayed in the debug bar. You could also choose an icon color along with the label. Any thoughts on this vs coloring the header via AOS?

@horst is right for sure. The other possibility depending on your needs is this:

mod_security is the devil!

I just checked your code here in Hanna's Test code option and it worked fine. I got myself my own form action link, but otherwise used your code. I used the text/html option. Sorry not much help I guess

What do you expect, you're living in the stone age Seriously though it would help if you posted code rather than an image so we could help test, but on that note, do you really want your MailChimp "u" and "id" public in this post? Maybe they are not important - I am not a MailChimp user so not sure on this.

This is a great idea (better than mine) if nothing in the module needs to work on the frontend, but one thing to note - if you change the autoload from true to template=admin you will need to do a Modules > Refresh to have the change take effect - I remember pulling some hairs in my early days of module development wondering why it wasn't working

@operat - welcome to the forums! Here's some info on the field that LK mentioned: https://processwire.com/blog/posts/processwire-3.0.4-repeaters-revisited-preview-of-profields-matrix/#new-profields-repeater-matrix-field

Looks really great @renobird - I know you say it it is specific to your environment and not meant to be released, but are you rethinking that? The one thing that we discussed in the Tracy thread about this was the ability for the tickets to be initiated from a link on every page so the user doesn't need to specify the page, and also so that the devs can view tickets relevant to the page they are viewing. I'd hate to see us all reinventing the wheel here - how can we move forward?

I like where you are headed and as I mentioned I am very keen on this functionality as well. I just want to make sure there won't be duplication of effort here. Are you actually starting to build this, or just trying to motivate?

I floated the idea of a "Notes" panel for Tracy which I think would cover your needs. Have a read through many of the posts below - @bernhard and @szabesz in particular come up with some good ideas of how this might work. As @tpr suggests, Tracy may not be the place for it, but I am still considering the where and how, but I am definitely keen on building this. The key thing I want is to be able to provide and view the feedback on each page in the front-end, as well as having an admin interface to review and manage them all.

Maybe take a look over at the jumplinks thread:

If you can't uninstall normally, you might need to edit the modules table in the database to remove the line for this module. It might also help to manually delete the module files after making that db modification.

Take a look at Jumplinks: http://rockett.pw/jumplinks/

Wow - now I feel so boring and serious Seriously (ha ha) though, I think there is a great place for fun elements in software, but I think it's important who it's aimed at and whether they'll see it as fun or just confusing - "you gotta keep it smart people" (dorky TV quote there)! Getting OT, but why do all phone companies around the world seem to use cute animals in their advertising? I don't see the fun because I can't see the connection - the fun has to be relevant.

Based on the comments above it sounds like there are currently still some issues with 3.x. @kongondo is away at the moment, but I am sure he'll be looking at getting this 3.x compatible now that we are so close to a stable release.

I was waiting for your response here - sorry about that - no offense intended

It's certainly no big deal at all

In most cases you can simply do: if($page->template == "admin") { but this needs to be in ready(). If you need it to work within init(), then I use: if(strpos($_SERVER['REQUEST_URI'], wire('config')->urls->admin) === 0) {

I didn't add it - it's the details of the selector. Not sure, but I think maybe this only appears with ListerPro.

Minor css issue - notice the location of the notes icon - this is the iframe that contains the Usage details on a template settings page.

@tpr - the latest commit fixes the "Uncaught Error: Class 'Tracy\Debugger' not found" error in modals. I have also changed the behavior slightly. Tracy is now loaded in normal modals, but not inline ones. I think this is a good balance, but let me know if anyone has any strong thoughts on this. FYI - an example of an inline modal is the "Usage" section of a template settings page.

Thanks - sounds like that is probably the case - will see if Ryan can help get Tracy loaded first all the time. Actually I intentionally prevent Tracy from loading in modals although I do see why the last commit has changed when you get that error. I can easily have it loaded for modals again though. I was disabling because I thought it was superfluous and looked ugly, but maybe it's important, especially if the modal contains an iframe - in that case having Tracy enabled would be the only way to debug the content of the iframe.