plone / plone/plone.app.debugtoolbar

nice to be used without site activation

Open
#8 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
8
Forks
5
Avg merge
26m
Merged PRs (30d)
1

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing how the debug toolbar is activated per site and document the security implications of using it without site activation; done means a concrete, maintainable approach is agreed for safely using the toolbar across instances.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.