search

labd / wagtailstreamforms

What happened when a FormBuilder met a StreamField
http://wagtailstreamforms.readthedocs.io
MIT License
156 stars 80 forks source link

Add support to Wagtail 5.0 #219

Open PrynsTag opened 1 year ago

PrynsTag commented 1 year ago

This update brings new features such as dark mode, SVG support, enhanced accessibility checker, and safer delete option. These features provide more options and control over content creation experience and make it easier to manage websites. It also has a lot of bug fixes and it drop the support for Django 4.0 that reached end of life on 1st April 2023.

stevejalim commented 1 year ago

Noticed this DeprecationWarning when running things just now:

RemovedInWagtail50Warning: Importing from wagtail.core.blocks is deprecated. 
Use wagtail.blocks instead. 
See https://docs.wagtail.org/en/stable/releases/3.0.html#changes-to-module-paths
stevejalim commented 1 year ago

I'm hoping to carve away some time to work on a PR for this, unless anyone's already got it started?

toptalo commented 1 year ago

Wagtail 5.2 (LTS) relised

urlsangel commented 1 year ago

The project I'm working on could do with 5.2 support! 👍

funkhaus-phil commented 11 months ago

how is the status on the 5.2 lts support?

toptalo commented 3 weeks ago

Wagtail 6.3 (LTS) relised 😭

funkhaus-phil commented 3 weeks ago

Hey i don't know if it helps anybody, but for us this solution works out great. We do use wagtail as a headless cms tho. When you want to use it within the templating language as well you probably need to put further work into it.

Basically we removed streamforms entirely from our projects and replaced it with the form builder that comes with wagtail and formed it a little bit to fit into the idea behind streamforms. We have a dedicated form page that is outside of the sitemap context and that page does handle the logic for creating the forms, sending mails and also creating submissions. For this type of page we created a streamfield Block, we can use in any Page context like before with streamforms which lets you decide which form you like to render. I created a serializer for that Form Block that does serialize the data from the form page the same way streamforms did and therefor our Frontend Apps which consume the Data from the API needed basically no adjustments. Only downside is, that you have to recreate and also place them again in the StreamField context of your pages in older Projects. In our case we made a cut for some older projects and leave them on the latest working release of wagtail==4.1.9 (4.2.+ probably also works), django==4.1.8 and streamforms==4.1.0 newer projects are coming fully upgraded to the latest LTS versions :) In case somebody is interested about the specifics, let me know.