I'm having a problem with BUEditor's visibility for content types.
Even on the settings page for each editor type, the "demo" area does not display BUEditor. I have configured the BBCode editor to display on pages with "node/add/forum", (I've also tried forum and forum/*) without success. The only place where BUEditor is displayed is on the Content section when you edit buttons for an editor type.
My Role-editor assignments are as follows:
user#1: Assigned = BBCode, Alternative = Default,
administrator: Assigned = Default, Alternative = BBCode, Weight = -10
content author: Assigned = Default, Alternative = BBCode, Weight = -9
registered user: Assigned = BBCode, Alternative = Default, Weight = -7
un-registered user: Assigned = none, Alternative = none, Weight = 0
authenticated user: Assigned = Default, Alternative = Default, Weight = 11
anonymous user : Assigned = none, Alternative = none
No users are assigned the authenticated user role.
All I'd like to have set up is for admins and content authors to use the default editor for blogs, and admins, content authors and registered users to use the BBCode editor for forums. All administration pages should use the default editor. At the moment, for creating major site content such as stories, pages and panels I use CKEditor.
What am I doing wrong, for inevitably I think it is something I'm missing?
Thanks.
Comments
Comment #1
trotskyicepick commentedJust messing about, I configured the BBCode editor as the "assigned" and "alternative" editor for all users. Now, the "Demo" field shows a demo of the editor being configured (ie, when configuring BBCode editor it shows a demo of the BBCode editor, same for default, commenter etc). The "Content" field when editing the buttons now properly displays a text area that expands to show the full code for the button when you enter it.
As for "all" other content types (blogs, forums, stories, pages etc), no editor is displayed. So it must be me getting confused regarding "role-editor assignments". Any helpful advice will be greatly appreciated, as I've mentioned elsewhere I'm quite excited about the "possibilities" this editor offers, and it looks great on the page too.
Thanks Again.
Comment #2
ufku commentedAll you need to set Visibility settings of the assigned editor. You can define the page paths at which BUEditor is visible. You can also set the excluded textarea ids at those pages. Both fields accept * as wildcard.
While processing a textarea if the visibility settings of the assigned editor does not apply BUEditor checks the visibility settings of the alternate editor(if set).
Note that BUEditor won't be visible for textareas that are already processed by WYSIWYG editors.
Comment #3
trotskyicepick commentedThanks again, I've finally got things working more or less the way I expect.
Comment #4
ufku commented