Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#8 | authcache-debug_users-error.jpg | 150.79 KB | philsward |
#7 | authcache-debug_users-error.jpg | 134.98 KB | philsward |
#7 | authcache-debug_users-noerror.jpg | 117.64 KB | philsward |
#1 | 2006012-fix-debug-users-widget.diff | 440 bytes | znerol |
Comments
Comment #1
znerol CreditAttribution: znerol commentedWould you please apply the attached patch and report back whether it fixes the problem.
Comment #2
znerol CreditAttribution: znerol commentedComment #3
DeNelo CreditAttribution: DeNelo commentedHi,
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.
Comment #4
DeNelo CreditAttribution: DeNelo commentedUpdate: 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.
Comment #5
znerol CreditAttribution: znerol commentedWhat happens when you're on an admin page (and the seven-theme is selected for admin-pages)?
Comment #6
philsward CreditAttribution: philsward commentedApplying the patch removed the error for me, however, it also removed the debug link :-/
Comment #7
philsward CreditAttribution: philsward commentedListing some screenshots of how mine looks with and without the patch.
Comment #8
philsward CreditAttribution: philsward commentedWhoops! Let's try this again... Forgot to refresh the screen to get the error back.
Comment #9
znerol CreditAttribution: znerol commentedThanks 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.
Comment #10
simg CreditAttribution: 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.
Comment #11
znerol CreditAttribution: znerol commented