The WYSIWYG module js checks for elements with the class wysiwyg. The theme hook removes the formatting guidelines, which have a class "wysiwyg". If you also limit the input formats to 1 for a role, there will be no element in the page with class wysiwyg, which results in not loading the editor.
How should we handle this? Make a setting to allow displaying the guidelines? Or just remove the guidelines in css with a display:none or visiblity:hidden? In that way the js will still work I guess.

CommentFileSizeAuthor
#8 rubik-933222-8.patch788 bytestraviscarden
#6 rubik-933222.patch671 bytestraviscarden

Comments

cyberwolf’s picture

Subscribing.

cyberwolf’s picture

Actually looks like this was fixed already in Git, see http://github.com/developmentseed/rubik/issues/closed/#issue/107

twod’s picture

The guidelines (text) can be removed, but the container div must be present because of the classes used by Wysiwyg. I haven't looked how it was fixed in the Git repository, but for reference; check out how the Better Formats module does this in the function they use instead of filter_form().

Anonymous’s picture

planctus’s picture

I've just noticed that this is not the only problem you have using wysiwyg and rubik theme together.
I have three textarea in the same content type with different input formats ( using better formats ) and editor profiles.
One is the default body field, and that's the only one with the rich text attached for all roles except the administrator whatever configuration i've tried.
Thanks,
Da.

traviscarden’s picture

StatusFileSize
new671 bytes

Here's a CVS patch, in case anyone wants it.

Viybel’s picture

Version: 6.x-3.0-beta1 » 6.x-3.0-beta3
Priority: Normal » Major

It's been more than a year. How comme this patch hasn't been applied to 6.x-3.0-beta3?

It has costed me more than two hours of debugging just to find it...

traviscarden’s picture

Title: rubik_filter_form() breaks loading editor if only one input format is active » rubik_filter_form() breaks WYSIWYG functionality
Status: Active » Needs review
StatusFileSize
new788 bytes

Maybe a Git patch would grease the wheels a little.

danylevskyi’s picture

TravisCarden, your patch #8 works like a charm! Thanks!

robert castelo’s picture

Can confirm that this is still a problem in 6.x-3.0-beta3 and that the patch in #8 fixes it.

traviscarden’s picture

Status: Needs review » Reviewed & tested by the community

I think we can RTBC this now.

Jānis Bebrītis’s picture

bump.

latest patch at #8 works with beta3. Create new release with this patch, please

haydeniv’s picture

Status: Reviewed & tested by the community » Fixed

Committed: d0ca028
Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.