-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sluggable field no longer works after form refresh #26
Comments
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in this issue for the last 6 months. |
This issue will be closed and archived in 3 days, as there has been no activity in this issue for the last 6 months. |
This issue will be closed and archived in 3 days, as there has been no activity in this issue for the last 6 months. |
develop
Description:
Sluggable fields appear to stop working as soon as a form is refreshed. This happens even if the form context is in
create
and the sluggable field itself has not been modified, so theoretically, the slug should still be tracking the trigger field value.Steps To Reproduce:
StaticPage
component)/home
/home
. At this point, we would expect the slug to be/welcome
.The text was updated successfully, but these errors were encountered: