Closed (fixed)
Project:
Flexinode
Version:
master
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
21 Sep 2005 at 23:57 UTC
Updated:
22 May 2006 at 13:32 UTC
Jump to comment: Most recent file
Using flexinode cvs in the current drupal head.
Only the root user can create flexinode content. Even with permissions set other users don't see the links on the create content page, although it does appear in the navigation menu (bug in drupal head?) the link there doesn't work.
Seems to be a problem with flexinode_access. I don't know enough to fix it though.
I do know that getting flexinode_access to return true allows normal users to post flexinode content, so the rest seems to work fine.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 31880.patch | 1.79 KB | samc |
| #1 | flexinode.module.47update.patch | 1.59 KB | moggy |
Comments
Comment #1
moggy commentedOk, think I've sorted it
[code]- return user_access('create '. flexinode_node_name($node->type) .' content');
+ return user_access('create '. node_get_name($node) .' content');
[/code]
The patch attached fixes this problem plus a couple of other little changes that appeared to be needed to update to 4.7
Comment #2
moggy commentedStill missing table view. Just getting a blank page at the moment :(
Comment #3
Steve Dondley commentedSee http://drupal.org/node/22218#theme_username for how to fix the blank page.
Comment #4
Bèr Kessels commentedThis is an important patch. Its a first step towards a release for 4.7
Comment #5
Bèr Kessels commentedalso see the now closed thread http://drupal.org/node/29947
Comment #6
samc commentedUpdated patch:
- removes flexinode_node_name() function definition
- replaces calls to flexinode_node_name() with node_get_name()
- replaces calls to format_name() with theme_username()
Works fine for me.
Comment #7
samc commentedComment #8
Bèr Kessels commentedLooks good, but needs testing.
Can someone please review?
Comment #9
Bèr Kessels commentedI reviewed, tested and committed.
Chances are that specific fields now show fatal errors, but for that we need to open separate issues.
Comment #10
Waldemar commentedI believe this patch introduces errors on translated pages. node_get_name gets you a translated name of the content type, however access permissions are set in the original language. I've checked that and if I give users the permission to post but translate the content type name, then that access permission is not applied.
Comment #11
(not verified) commented