{ "info": { "author": "Martin Aspeli", "author_email": "optilude@gmail.com", "bugtrack_url": null, "classifiers": [ "Framework :: Plone", "Framework :: Plone :: 5.0", "Framework :: Plone :: 5.1", "Framework :: Plone :: 5.2", "License :: OSI Approved :: GNU General Public License (GPL)", "Programming Language :: Python", "Programming Language :: Python :: 2.7", "Programming Language :: Python :: 3.6", "Programming Language :: Python :: 3.7" ], "description": "Introduction\n============\n\n``plone.app.debugtoolbar`` provides a wealth of debug information about a\nrunning Plone site at your fingertips. Simply install it in your build\n(e.g. by adding it to the ``eggs`` list in your Buildout and re-running\nbuildout) and install it into your Plone site.\n\nYou should now see a ``Debug`` link at the top of your site. Click it to open\nthe debug drawer. Click on a panel to view relevant information.\n\nPanels include:\n\n* Context, showing information about the current content object\n* Interactive, providing an interactive Python prompt through which you can\n interact with the current context (only available to users with the\n ``Manage portal`` permission)\n* Request, showing information about the request that produced the current page\n* Response, showing informationa about the response that produced the current\n page\n* Published, showing information about the page template or view that was\n published\n* Theme, showing information about the current theme and browser layers\n* User, showing information about the current user\n* Workflow, showing information about workflow and security\n* Zope, showing information about how the Zope server is configured\n* Versions, listing the versions of every package known to the Zope process\n\nSafety\n======\n\nThe debug toolbar provides a lot of information about your Plone site that you\nmay not want the world to know. It could also have a noticable performance\nimpact, and for users with the ``Manage portal`` permission it provides access\nto an interactive interpreter where arbitrary Python statements can be executed,\nallowing a user to bypass Zope security.\n\nIn other words: **Do not install this package on your production server**.\n\nIntegration\n===========\n\nEach panels is included as a viewlet. You can register new panels using a\nviewlet registration like this::\n\n \n\nSee ``plone.app.debugtoolbar.browser`` for plenty of examples of panels.\n\nContributors\n============\n\n- Martin Aspeli, Author\n- Giacomo Spettoli, i18n\n- Leonardo Caballero, Spanish Translation, Uninstall GenericSetup profile\n\nChangelog\n=========\n\n.. You should *NOT* be adding new change log entries to this file.\n You should create a file in the news directory instead.\n For helpful instructions, please see:\n https://github.com/plone/plone.releaser/blob/master/ADD-A-NEWS-ITEM.rst\n\n.. towncrier release notes start\n\n\n1.2.0 (2019-01-09)\n------------------\n\nNew features:\n\n- Prepare for Python 2 / 3 compatibility [jmevissen]\n\n\n1.1.4 (2018-03-07)\n------------------\n\nBug fixes:\n\n- Remove unittest2 dependency\n [kakshay21]\n\n- Make it work in chrome, as '