When working on sites with a number of different people, it is quite annoying that when theme developer is enabled, it is enabled for every user with permission. Ideally, the theme developer information would be enabled on a per users basis.

Comments

moshe weitzman’s picture

moshe weitzman commented

Seems reasonable. Not sure how the user experience would work. I'd love to see a patch for this.

td540’s picture

td540 commented

I was just about to post an issue with the same question.

moshe weitzman’s picture

moshe weitzman commented
Project: Devel » Theme developer
Component: devel_themer » Code
moshe weitzman’s picture

moshe weitzman commented
Project: Theme developer » Devel
Component: Code » devel_themer

Maybe we require a querystring param in addition to the perm? Then perhaps do way with the toggle in the bottom left?

moshe weitzman’s picture

moshe weitzman commented
Project: Devel » Theme developer
Component: devel_themer » Code
JeremyFrench’s picture

JeremyFrench commented
Version: 6.x-1.x-dev » 7.x-1.x-dev

Setting to correct version. I'm not against this, there is scope for customizing theme_developer per user and this could be part of that.

Can't promise anything soon, but I'll keep this on the radar.

kenneth.venken’s picture

kenneth.venken commented
Status: Active » Postponed (maintainer needs more info)

First of all try #1247280: Fixing html breakage once and for all and see if that decreases the annoyance of working with theme developer.

Theme developer should only be used by developers on development sites. Is there an argument for this feature except for the 'theme developer breaks my site'-argument?

Theme developer changes the theme registry with 'hook_theme_registry_alter', and this hook is only called when the theme registry is built (cache clear), this makes it impossible to alter the registry only for specific users. We could let theme developer change the registry, but prevent it from inserting html and displaying the javascript checkbox. We're currently fixing the problems related to the modification of html so a fix would come down to not displaying the javascript checkbox. And that can't be right...

kenneth.venken’s picture

kenneth.venken commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

7+ weeks without extra feedback.

I'm closing this issue. Further feedback should probably be posted on #1247280: Fixing html breakage once and for all.