[Bug] Missing info about TinyMCE upgrade

[majomix]

Bug report / Feature Request

What I did

I followed the upgrade guide from Backpack 5 to Backpack 6.

What I expected to happen

My custom code and plugins for TinyMCE v5 work.

What happened

TinyMCE v5 got an upgrade to v6, lots of plugins were removed, renamed or moved to paid section. Loading of custom plugins is also broken.

---

If I knew TinyMCE got a major version upgrade, I wouldn't go through the whole hustle of upgrading Laravel 9 to Laravel 10 in order to upgrade Backpack 5 to Backpack 6. This breaking change wasn't mentioned in the upgrade guide nor the fields description. I was interested in trying out the new fields before my paid Backpack license expires on the first week of December.

Would it be possible to create TinyMCE v5 field?

[welcome[bot]]

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication channels:

• Bug Reports, Feature Requests - Github Issues (here);
• Quick help (How do I do X) - Gitter Chatroom;
• Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;
• Showing off something you've made, asking for opinion on Backpack/Laravel matters - Reddit;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

-- Justin Case The Backpack Robot

[pxpm]

Hey @majomix

As easy a putting a file in resources/views/vendor/backpack/crud/pro/fields/tinymce.blade.php and that becomes the tinymce of your application. You can use whatever version of tinymce you want.

I'd suggest you rename your custom to like tinymce_custom or something so that you keep the ability to use both fields. If you never intend to use the backpack tinymce just leave your custom with the same name of the package and Backpack will automatically pick your file instead of ours when you do type => 'tinymce' in a field.

Cheers

[pxpm]

I am closing this.

Hope you solved the issue by now, and sorry for the trouble.

Cheers