Laravel-Backpack/PageManager

Doesn't work with no wysiwyg field

flamreal opened this issue · 3 comments

This addon doesn't work with free current version of Backpack 5.0 because it has no must have wysiwyg field now =
Please, reconsider this issue or inform about it in readme of the addon.

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 mediums:

  • 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;

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

@flamreal , when adding Backpack v5 support we've changed the wysiwyg fields to summernote, which is a FREE field. So we DO have a free field that will let you edit HTML, just the name has changed. Please do the same in your own templates. The upgrade guide did not inform of this, because the upgrade guide will only be followed by people who were using Backpack with a license.

I've edited the README to also use summernote instead of wysiwyg, thanks! That must have been the source of confusion.

Let me know if I've misunderstood this in some way.

Cheers!

Thanks for reply, this is what I expected!
(I'm newbe here and just was confused when the addon marked as free crashed by requering paid only feature)