You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is beyond what we do with our normal breaking changes policy, since the majority of those changes are on parts of Wagtail that haven’t been publicly supported / documented in any way. To make sure this goes smoothly anyway, I’m here to provide an advance notice of what we’re aware of with this specific package 🙂
In the case of StreamForms, there are no confirmed issues, but I thought it would be worthwhile to give you a heads’up of what to manually review nonetheless.
Header template
We’ve made cosmetic changes to our header component. We expect it to work as-before otherwise, but it’s worth checking manually:
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/advanced_settings.html
8: {% include "wagtailadmin/shared/header.html" with title=title_str subtitle=object icon="doc-empty-inverse" %}
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/confirm_copy.html
8: {% include "wagtailadmin/shared/header.html" with title=copy_str subtitle=object.title icon="doc-empty-inverse" %}
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/confirm_delete.html
8: {% include "wagtailadmin/shared/header.html" with title=del_str subtitle=object.title icon="doc-empty-inverse" %}
Core templates reuse
We’ve made a lot of styling and template changes to our base templates – it’s worth checking whether this affects any of those customisations:
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/advanced_settings.html
1:{% extends "wagtailadmin/base.html" %}
8: {% include "wagtailadmin/shared/header.html" with title=title_str subtitle=object icon="doc-empty-inverse" %}
16: {% include "wagtailadmin/shared/field_as_li.html" %}
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/confirm_copy.html
1:{% extends "wagtailadmin/base.html" %}
8: {% include "wagtailadmin/shared/header.html" with title=copy_str subtitle=object.title icon="doc-empty-inverse" %}
17: {% include "wagtailadmin/shared/field_as_li.html" %}
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/confirm_delete.html
1:{% extends "wagtailadmin/base.html" %}
8: {% include "wagtailadmin/shared/header.html" with title=del_str subtitle=object.title icon="doc-empty-inverse" %}
wagtail/labd/wagtailstreamforms/wagtailstreamforms/templates/streamforms/index_submissions.html
1:{% extends "wagtailadmin/base.html" %}
6: {% include "streamforms/wagtailadmin/shared/datetimepicker_translations.html" %}
80: {% include "wagtailadmin/shared/field_as_li.html" with field=field field_classes="field-small" li_classes="col4" %}
I hope this all makes sense. We’ve made a lot of other styling and template changes that are hard to track down, and for which it’s unclear whether any breakage might be expected or not. As you go through the Wagtail 3.0 compatibility work, please let me know if there are other compatibility issues you come across so we can consider those customisations in Wagtail development in the future, and let others know about those breakages.
The text was updated successfully, but these errors were encountered:
Hi Lab Digital!The Wagtail 3.0 first release candidate is out. There are large UI changes in this release, for which we have reviewed expected breakage in third-party UI customisations.
This is beyond what we do with our normal breaking changes policy, since the majority of those changes are on parts of Wagtail that haven’t been publicly supported / documented in any way. To make sure this goes smoothly anyway, I’m here to provide an advance notice of what we’re aware of with this specific package 🙂
In the case of StreamForms, there are no confirmed issues, but I thought it would be worthwhile to give you a heads’up of what to manually review nonetheless.
Header template
We’ve made cosmetic changes to our header component. We expect it to work as-before otherwise, but it’s worth checking manually:
Core templates reuse
We’ve made a lot of styling and template changes to our base templates – it’s worth checking whether this affects any of those customisations:
I hope this all makes sense. We’ve made a lot of other styling and template changes that are hard to track down, and for which it’s unclear whether any breakage might be expected or not. As you go through the Wagtail 3.0 compatibility work, please let me know if there are other compatibility issues you come across so we can consider those customisations in Wagtail development in the future, and let others know about those breakages.
The text was updated successfully, but these errors were encountered: