I've selected to show the Authcache Debug info for one user only. However, when logging in as that user, I get:
Notice: Undefined variable: debug_users i authcache_authcache_info() (linje 760 af /home/kristentf/public_html/sites/all/modules/authcache/authcache.module).
Content of authcache_debug_users variable:
a:1:{i:0;s:6:"DeNelo";}
Logging in as DeNelo.

CommentFileSizeAuthor
#8 authcache-debug_users-error.jpg150.79 KBphilsward
#7 authcache-debug_users-error.jpg134.98 KBphilsward
#7 authcache-debug_users-noerror.jpg117.64 KBphilsward
#1 2006012-fix-debug-users-widget.diff440 bytesznerol

Comments

znerol’s picture

znerol commented
StatusFileSize
new 2006012-fix-debug-users-widget.diff440 bytes

Would you please apply the attached patch and report back whether it fixes the problem.

znerol’s picture

znerol commented
Status: Active » Needs review
DeNelo’s picture

DeNelo commented

Hi,
I applied the patch, selected the "DeNelo" user in "Enable for specified users", and cleared all caches.
I then logged in as DeNelo, but no Authcache box is shown, unfortunately.

DeNelo’s picture

DeNelo commented

Update: This was done in IE10. Clicking Compatibility View (you know, the broken page on the right in the address bar) brought up the box (but the site looked like crap which is beside the point).
So: It works, but only in IE in Compatibility View mode, and not in standard IE10 (for instance), or in Chrome.

znerol’s picture

znerol commented

What happens when you're on an admin page (and the seven-theme is selected for admin-pages)?

philsward’s picture

philsward commented

Applying the patch removed the error for me, however, it also removed the debug link :-/

philsward’s picture

philsward commented
StatusFileSize
new Patch Applied117.64 KB
new No Patch Applied134.98 KB

Listing some screenshots of how mine looks with and without the patch.

philsward’s picture

philsward commented
StatusFileSize
new No Patch Applied150.79 KB

Whoops! Let's try this again... Forgot to refresh the screen to get the error back.

znerol’s picture

znerol commented
Status: Needs review » Postponed

Thanks for reporting. Because this is not related to productive operation of the module I'm not going to fix this issue for the 1.x branch. In the 2.x branch I likely will remove this feature and instead rely on the access-control system provided by core.

I'll accept patches though if anyone needs to have that fixed in the 1.x branch.

simg’s picture

simg commented

>I likely will remove this feature and instead rely on the access-control system provided by core.

Bear in mind that access control is for determining if someone is *authorised* to do something. It shouldn't be used for turning features on and off.

znerol’s picture

znerol commented
Issue summary: View changes
Status: Postponed » Closed (outdated)