nice to be used without site activation

[djay]

This is a really useful debugging tool, particularly for analysing what is going on in a real site for instance on a UAT/staging server. However it's a security risk. For this reason we'd install it on its own special debug zope instance, not on all instances. However due being site specific it causes problems to have to used only on a single instance. It would be nice if there was another version or a way to use it without having to activate it per site.

[afrepues]

One way to have this available is to enable it only when the instance is running in debug mode, like it is possible to do with Clouseau.

[frisi]

by now i'm using Products.PDBDebugMode to inspect production plone sites via a separate zeo client (instance-debug) that has this addon in it's eggs.
it's not installed on the instances used to serve the website in production.

plone.app.debugtoolbar would have the benefit of not having to ssh to the server, open a console and start the instance in foreground mode there to do the same.
however, since it needs to be installed on the plonesite, the production instances are complaining that the package is not installed on startup:

2014-03-26 11:42:30 WARNING OFS.Uninstalled Could not import class 'IDebugToolbarLayer' from module 'plone.app.debugtoolbar.browser.interfaces'

this works, is secure, but not 100% clean.

i'd also vote for skipping the registration to the browserlayer and make the addon available as soon as it's in the eggs section and the instance is started in debug mode.

any implications for other users with different use-cases?

[vangheem]

+1 from me. Go ahead and implement.

[jensens]

indeed! +1

[thet]

also +1