Closed (won't fix)
Project:
Create related content
Version:
6.x-1.1
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Feb 2010 at 14:42 UTC
Updated:
9 Apr 2012 at 12:13 UTC
Hello! I've been using crc with that custom links method ever since I wrote you about it many moons ago.
Since I use the custom links to specifically direct users, the crc tab can cause confusion. Whereas I like having the ability to use it in administrating content, I like having the module do quiet work directing users to create content with a certain tag for example.
This is such an essential module, thank you for sharing it!
Comments
Comment #1
alan d. commentedThe tab is controlled by the two permissions:
(
'access create related content menu'
OR
'access create related content block'
)
AND
can create at least one content type
You can create a role with one of these permissions and assign the role to the users that you want to access the tab.
I think users can bypass the tab via the preset link 'node/add/%/crc-preset/%' if they have the permission 'crc_node_add_by_preset_access' [edit: I mean "create related content by preset" permission]
Hope this helps
Comment #2
Trunkhorn commentedSo, for crc to work, either one of those first 2 permissions must be set?
But if either of those are set, then access to the tab is mandatory?
What I'm looking to do is to disable the tab for non-admin user roles, but still be able to send them to a preset link for them to create content with the preset.
I want to send the user to the preset link to create content, but have them not have access to the tab and it's options.
I tried mixing and matching between the options on the permission page, and couldn't find one that would preserve functionality while not displaying the tab.
Comment #3
alan d. commentedThere must be a double permission check somewhere. I'll try and get some time to look into it but no ETOD
Comment #4
Trunkhorn commentedVery cool, thanks!
Comment #5
Trunkhorn commentedAlan, would you be able to explain what that last % stands for in this 'node/add/%/crc-preset/%'
Is it supposed to be a node number?
I'd still like to use this feature if you can advise me.
Comment #6
alan d. commentedIt is the preset id from memory.
Comment #7
Trunkhorn commentedOk... I think I finally get that now. That would be used if you had some specific presets not related to a current node, but defined in the administration section?
Good to know. I actually haven't used that before.
Comment #8
alan d. commentedAs per the project page, I am stopping development of this module.
Note that I am not marking it abandoned as this triggers update warnings and I will address any security issues should they raise.