Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
that would be nice, though right now it appears that it's just by user - so if a user type is specific toa content type, problem solved -but i do know what you mean! it would be cool...
The wiki pages are setup to accept MediaWiki tags, so it would be nice to have a editor loaded for those tags
Our Forums only accept bbcodes, again would be nice to have the editor setup for that.
Finaly our news section accepts certain HTML tags.
I realy like the editors possibility to add / change the code behind the buttons. But right now i have absolutely no use for them.
This was implemented for 6.x-1.x branch which interprets node/add/node_type also as node/*/edit for the node_type.
For example, for story type all you have to do is to add node/add/story to the page visibility settings. This will automatically include the pages node/*/edit for the story type. Note that you shouldn't add node/*/edit or node/* as they match all node types.
@ufku - That's a really cool feature, but what I'd like to do is initialize the editor for comments only on forum nodes. The path-checking section doesn't recognize url aliases, just system paths. It would be easy enough to set a path like forum/* , which would pick up all forum posts I've aliased as such through pathauto. Of course, if it could pick up by content type, that would probably be more reliable than by alias.
for story type all you have to do is to add node/add/story to the page visibility settings. This will automatically include the pages node/*/edit for the story type. Note that you shouldn't add node/*/edit or node/* as they match all node types.
Though this is a great functionality, I don't find this very intuitive. Is this in the documentation? Because if I wouldn't have read it here, I wouldn't have known that.
Personally having a checkbox per content type would make more sense to me. In the end it's just a matter of personal taste. It all works.
if you use the bueditor branch 1 you have the possibility to use the editor by content type.
Please take a look at this post: Patch to use the bueditor by content type
What you describe in http://drupal.org/node/333583#comment-1287814 does not work.
Maybe I'm too stupid. But I can not configure an editor in order to exclude individual content types. That is the reason for my patch.
But there is another argument for the patch:
The inserted configuration is immediately understandable and intuitive, and thus achieves a better usability.
Comments
Comment #1
zilla commentedthat would be nice, though right now it appears that it's just by user - so if a user type is specific toa content type, problem solved -but i do know what you mean! it would be cool...
Comment #2
elbertvan commentedThats the exact thing im running into.
Our site has 3 main content types:
Forums
Wiki pages
News Items
The wiki pages are setup to accept MediaWiki tags, so it would be nice to have a editor loaded for those tags
Our Forums only accept bbcodes, again would be nice to have the editor setup for that.
Finaly our news section accepts certain HTML tags.
I realy like the editors possibility to add / change the code behind the buttons. But right now i have absolutely no use for them.
Im using v 1.2 not the dev
Comment #3
YorickDowne commented[nevermind me]
Comment #4
CompShack commented+1 for this feature - would love to see it happen! I then could allow BBcode on my forum and wiki markup on wiki pages.
Comment #5
ufku commentedThis was implemented for 6.x-1.x branch which interprets node/add/node_type also as node/*/edit for the node_type.
For example, for story type all you have to do is to add node/add/story to the page visibility settings. This will automatically include the pages node/*/edit for the story type. Note that you shouldn't add node/*/edit or node/* as they match all node types.
Comment #6
ao5357 commented@ufku - That's a really cool feature, but what I'd like to do is initialize the editor for comments only on forum nodes. The path-checking section doesn't recognize url aliases, just system paths. It would be easy enough to set a path like forum/* , which would pick up all forum posts I've aliased as such through pathauto. Of course, if it could pick up by content type, that would probably be more reliable than by alias.
Comment #7
ufku commenteddid you try 6.x-1.x-dev?
Comment #8
ao5357 commentedNo, of course not. I just installed it and URL aliases appear to work like a charm! Thanks.
Comment #9
ufku commentedComment #11
danny_joris commentedThough this is a great functionality, I don't find this very intuitive. Is this in the documentation? Because if I wouldn't have read it here, I wouldn't have known that.
Personally having a checkbox per content type would make more sense to me. In the end it's just a matter of personal taste. It all works.
Cheers,
Danny
Comment #12
quiptime commented@Flying Drupalist,
if you use the bueditor branch 1 you have the possibility to use the editor by content type.
Please take a look at this post: Patch to use the bueditor by content type
Comment #13
quiptime commentedComment #14
ufku commented"Editor by content type" is already in and explained at http://drupal.org/node/333583#comment-1287814
Comment #15
quiptime commentedWhat you describe in http://drupal.org/node/333583#comment-1287814 does not work.
Maybe I'm too stupid. But I can not configure an editor in order to exclude individual content types. That is the reason for my patch.
But there is another argument for the patch:
The inserted configuration is immediately understandable and intuitive, and thus achieves a better usability.
Comment #16
ufku commentedThis issue is about including(not excluding) bueditor for specific content types and it has a solution.
Comment #17
quiptime commentedThe issue post:
These words do not include: inclusion or exclusion! It can be concluded: Both -> Please allow us to set ... is available ...
Why do you permanently set the status to closed? Do you want to keep the number of open issues small?
Please behave yourself like a man. Thanks.
Comment #18
ufku commentedWhat kind of a man! are you?
Comment #19
ufku commented-Duplicate post-
Comment #20
ufku commented-Site maintenance-