Closed (fixed)
Project:
Bibliography Module
Version:
6.x-1.13
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 May 2010 at 14:15 UTC
Updated:
28 Sep 2010 at 19:20 UTC
I just updated to 6.x-1.12. The link of the titles has changed from example.com/node/123 to example.com/biblio/view/123. The result is that anonymous users get an access denied error on the new links.
The "access biblio content" and "view full text" permission are set for anonymous user. I tried to rebuilt the permissions cache but no luck.
Please help.
Comments
Comment #1
ar-jan commentedSame issue, after I updated from 1.10 to 1.12. A logged-in user (with administer biblio permission in this case) gets redirected to the actual biblio node when clicking the title, which now links to /biblio/view/nid.
Comment #2
droshani commentedI have the same problem, but it has a very strange behaviour. I can access all recodes through Bilio Index list but I can not access them through Biblio Record list.
It says
Access denied
You are not authorized to access this page.
Look at this record which you will not be able to see
http://kurdistanica.com/?q=biblio/view/15
But the same record here is accessible
http://kurdistanica.com/?q=node/15
If you look at the URL the biblio/view/ creates some sort of filter that does not allow access :(
If you are logged in when you hover on a record it show ...../?q=biblio/view/xx and when you click you actually are redirected to ..../?q=node/xx
But this does not happen when you are not logged in and you access it as anonymous. When that redirection does not take place in this version of Biblio?
I hope this will help to debug
Comment #3
ebeyrent commentedIt's worse than that - I can't view the nodes as an authenticated user, as the node author, or anyone else for that matter (except for user 1). As mentioned in #2, navigating directly to node/nid works just fine.
Comment #4
rjerome commentedtry going to admin/settings/performance, scroll down to the bottom of the page and click the "Clear cached data" button.
Comment #5
matze_ commentedThanks Ron,
clearing the cache does not solve the problem for me.
The links from the recent publication block and the abstract links (if there is an abstract) are working (.../node/X). Its just the titles links (.../biblio/view/X) that don't work.
Comment #6
rjerome commentedYep, My Bad! It's a bug and I'll make (yet another!!) release tonight :-(
Ron.
Comment #7
rjerome commentedfixed in the 1.13 release.
Comment #8
matze_ commentedThank You.
Comment #9
ebeyrent commentedAwesome - works now. Thanks!
Comment #10
droshani commentedFixed for me as well, Thank you
Comment #11
rjerome commentedIn case any of you are wondering why this change (title links changed from node/xx to biblio/view/xx ) was made, it was to accommodate an upcoming companion module which needs to override the title links, but only for "biblio" nodes, so there was no way to tell if the link node/xx was to a regular node or a biblio node.
Ron.
Comment #12
droshani commentedRon, Thank you for the hard work!
Comment #13
wuwei23 commentedCan I confirm that this is actually working for everyone?
I've recently upgraded from 1.10 to 1.13 and now my biblio nodes are not accessible to anonymous users. No permissions have changed at my end, but for the record both access biblio content and view full text are checked.
Comment #14
wuwei23 commentedMy apologies, there was another underlying issue that was the cause (somehow node_access was emptied).
Comment #16
cghuebner commentedIs this really fixed now? On my site, anonymous users still have no access to biblio items. Checked all permissions.
cgh
Comment #17
rjerome commentedHave you tried rebuilding the permissions on the 'admin/content/node-settings' page?
Ron.
Comment #18
cghuebner commentedYes, I did. No success. I have taxonomy access installed, but not activated for content type biblio.
Any ideas?
Thanks, Christian
Comment #19
cghuebner commentedI just checked the node_access table, and gid=1 (anonymous user) does not appear for biblio nids.
C
Comment #20
cghuebner commentedDeactivating taxonomy access did the trick. I switched to content access.
C
Comment #21
ar-jan commented