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.(line 58 of C:\XAMPP\htdocs\drupal_head\sites\all\modules\comment_notify-HEAD\comment_notify.lib.inc).
Set up: create a node. add comments to the node.
Click on the comments link below the node.
This error message seems to happen only when I am accessing the comments through user id 1.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 761888_comment_notify_default_4.patch | 4.07 KB | greggles |
| #1 | 761888_comment_notify_default.patch | 2.09 KB | greggles |
| uid1_error_message_accessing_comments.png | 105.4 KB | vegantriathlete | |
Comments
Comment #1
gregglesThere's a couple things I found which may be causing this and are also causing weird behavior related to it.
To repeat this: be sure you don't save your user account after installing comment_notify.
Comment #2
vegantriathleteJust to make it clear how to test this.
Create a user without having comment_notify enabled; it is irrelevant if it is uid 1. Then enable comment_notify and access comments. You will get the error message.
I still haven't updated the uid 1 profile, so it still doesn't have those preferences set. Patch fixes problem.
Comment #3
vegantriathleteActually, somehow it does seem to be related to my uid 1. I can't recreate the problem for other authenticated users. I even disabled and uninstalled comment_notify and created another user. That user didn't get the error message.
Nonetheless, the patch appears to fix the problem.
Comment #4
gregglesOK. Here's a more robust patch that fixes this problem in a few places and fixes a mismatch between function name and the variable it returns.
Comment #5
vegantriathleteI have reversed the first patch, tested with this patch, and confirmed that this patch also takes care of the problem.
Comment #6
gregglesNow fixed - http://drupal.org/cvs?commit=350840
Thanks for testing, vegantriathlete!