Closed (fixed)
Project:
Title Override
Version:
7.x-1.1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Jun 2012 at 02:57 UTC
Updated:
29 Dec 2012 at 21:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedHey Reg, thanks for the message. Somehow I overlooked that in the original development. Next update I push out I'll make sure to commit that change.
Comment #2
reg commentedCool.
When I looked at this It was to solve a problem which this comes close to but not quite. In case you're interested here's the problem... when you create content types sometimes the title field would be better named differently to suit the content type, e.g.: "Networking Group Name". This would be much more useful than page-by-page for many circumstances and you could list the content types and just have people supply an alternative name next to any that they want to override.
Cheers!
Comment #3
authentictech commentedThe module page and README needs updating on how to configure this module. I couldn't see how to use it and until I discovered this issue ticket.
Perhaps a note could be added to the docs as soon as possible as a temporary and easy measure while the code is being added? Remember, most users are encouraged through the Drupal manuals to create and use non-super user accounts as soon as possible so it would likely trip up a few people trying to use the module.
I really like the idea behind this module by the way. Very simple / easy to use and meets an important need.
Many thanks!
Comment #4
Anonymous (not verified) commentedHey authentictech, thanks for the message and feedback! I'm actually developing an entirely new admin page for this - something a bit less confusing and one that doesn't require the differentiation between system and node types.
Keep an eye on this project, and you should hopefully see at least a dev version up within a few weeks. Also, I've updated the overview page to make note of this current issue. Thanks!
Comment #5
authentictech commentedThanks. Due respect given for all that you are doing for the Drupal project. :-)
Comment #6
Miszel commentedhere is a patch that adds hook_permission to the module
Comment #7
james.williamsThis patch adds the correct permission (and also tidies up this module's entry on the modules page).
Comment #8
Anonymous (not verified) commentedHey Marcin & James - thanks for posting the patches. I'll try to get those pushed into the main branch here shortly.
Comment #9
Anonymous (not verified) commentedJust pushed up a new commit with the contributed changes. Thanks for the assistance on this guys.