Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
master
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Dec 2006 at 05:46 UTC
Updated:
8 Jan 2007 at 05:46 UTC
When I install nodewords, everything worked great, except that when I looked at my logs, I had a lot of "access denied" messages for comments. Sure enough, even as user/1 I could not post a comment (nor as anonymous of course) and just got "access denied" I turned off nodewords and comments worked just as before installing nodewords (that is perfectly).
Comments
Comment #1
ergophobe commentedI checked this on another server with different versions of PHP and MySQL with the same result. If both comment and nodeword are active, even user/1 gets access denied to comments.
Comment #2
ergophobe commentedLet's see - I changed the drupal_access_denied() calls to include __FILE__ and __LINE__ and output them. So the access denied message is coming from index.php, line 21
that means that function menu_execute_active_handler() (menu.inc, line 386 ff) is returning false for the expression
!_menu_item_is_accessible(menu_get_active_item()) [on line 407]
When I output the return value for menu_get_active_item, it is '0' with nodewords active.
When I disable nodewords, the return value for menu_get_active_item is 117 (correct for the test page in question) and everythign works as expected.
Sorry to say that it's bed time and that's as far as I got.
Comment #3
ByteEnable commentedIts also broken in Drupal 5.x too.
Byte
Comment #4
Robrecht Jacques commentedBug confirmed. If you enable nodewords and input a "geourl", then you can't post comments. This is probably an old bug popping up again.
Fixed again by only outputting a DC.title for node-pages. If someone knows a reliable way of getting the title of a page (any page) in hook_menu(), let me know. We can do it reliable for node-pages because then we just have to look at $node->title.
Fixed in nodewords.module v1.32.2.16 (for Drupal4.7) and in nodewords.module v1.55 (for Drupal5.0).
If the issue was not fixed for you, please reopen the issue.
Comment #5
ergophobe commentedVerified - issue is fixed for me on 4.7. Thanks!
Comment #6
(not verified) commented