HTML editor not loading since upgrade to 7.x-1.0-beta4

Same issue here. Reverting back to 7.x-1.0-beta2

Same here

+1
What is even odder is that it happened to me on some particular fields, not all of them.

I'm not sure this is a bug. But, because the type of format select changes from "select" to "hidden", some modules, like Wysiwyg, which expects it to be "select" can't find it and set the right filter to textarea. For me I've solved it by hiding the select element, instead of change it's type.

Your patch applies correctly, and it seems to solve the issue. Thank you!

However, I noticed another one: for some text formats, I hid in wysiwyg the text format selection and the tips, but I allowed the ability to switch on and off the rich text editor. With the Beta5 release, the toggle wrapper block for this option is included into the fieldset with the "element-invisible" class, which hides the option while I need it visible.

Maybe I should open another issue about this problem, and we can mark this current issue as RTBC?

Confirming this issue! This seems to be a regression, did someone check which issue & change in the last release caused this?
Needs a new fixed release asap, please.

Looks like it might have been caused by this issue? 🐛 Removing the format field breaks other modules Fixed

I can confirm the issue still occurs with 7.x-1.0-beta6.

I can re-produce this on both 7.x-1.x and 7.x-2.x.

1. Text field, an enable " Limit allowed text formats"
2. Select two formats
3. For users that have permission to both of these input formats, the editor work/load>/li>
4. For users that only have access to one of the input formats, the editor does not load. No error messages

Looked at the patch in #5. The minim change in better_formats.module to make it show up (ref #12) was just to uncomment:

      if (count($options) === 1) {
//        $element['format']['format']['#type'] = 'hidden';

Non of our tester noticed this in staging and I just needed a hot fix.

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

This change was not committed to the 7.x-1.x branch and unfortunately was not part of the 1.0 release. @joseph - Got time to cherry-pick and tag a 1.1 version?

https://www.drupal.org/project/better_formats/releases/7.x-1.1 →

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

Thanks for the stable release. Given the issue I described in #6 still happens with 7.x-1.2, I had to correct it via CSS, which is not the ideal solution.