When configuring defaults per content type, the resulting form structure differs from core's, which breaks Wysiwyg module's format parsing.

I'll look into this.

CommentFileSizeAuthor
#2 wysiwyg.resizable.patch2.27 KBsun

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Project: Better Formats » Wysiwyg
Version: 6.x-1.1 » 6.x-2.x-dev

erm, sorry, turns out that this is actually a bug in Wysiwyg ;)

So the issue is that we munge a #resizable textarea in the hope that we'll load an editor afterwards. But if we don't? Hell breaks lose. Or at least, no yummy-resizy ;)

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: Per-content type settings result in different form structure, breaking other modules (Wysiwyg) » #resizable textarea not resizable when no editor profiles are accessible/loaded
Status: Active » Needs review
StatusFileSize
new wysiwyg.resizable.patch2.27 KB

Better title + patch.

dragonwize’s picture

dragonwize commented

This also affects the comment form. #620338: comment textarea resizable function removed when removed fieldset

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs review » Reviewed & tested by the community

I need another review/test here and I hope that TwoD or someone else is able to chime in. To raise attention, marking as RTBC.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

Haven't had time to test it but the patch in #2 looks good and I can follow its logic without problems as it just delays the overriding of the #resizable flag until we know if we can actually handle it ourselves. Ok from me.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Reviewed & tested by the community » Fixed

Thanks for reporting, reviewing, and testing! Committed to all branches.

A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.

Status: Fixed » Closed (fixed)

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