pages fieldtype errors when single id is used #2023
Comments
Anyone found a fix for this yet? |
I'm still getting this in 2.10.2. I've patched it locally as follows, and it seems to work in my case, but I haven't looked into the root cause. Would be nice to get an official fix. statamic/bundles/Suggest/Modes/PagesMode.php:88
Here's the stacktrace:
|
@emlyn-Resn This fix works for me too. As you say though, would be good to get this rolled into an official release so as not to have to do this manually on every new site. |
+1 here getting this on 2.11.2 |
@emlyn-Resn Thank you for posting this fix until the Gentlemen make it work! |
Any updates on this? |
Reporting the same issue here on |
Still an issue on Any chance the above fix could be added to avoid having to do this every time? |
Will be in next release. Thanks @emlyn-Resn 🤘 |
Describe the bug
The fieldset editor, makes a
pages
fieldtype with the formatparent: cf02a919-d9df-43a9-acc5-dbff19d2c942
in the YAML.This causes a javascript 500 error in the CP when an entry with that fieldset is used and the pages selection control shows the loading spinner.
In addition, when you go back to the edit the field in the fieldset editor the
parent
selection is empty.To Reproduce
Steps to reproduce the behavior:
pages
fieldtype in the fieldset editorExpected behavior
Control loads.
Workarounds
Using a URL path works:
parent: /path/to/page
Formatting as an array works:
Additional context
@jasonvarga posted
as a fix in
PagesMode.php
Line 100
but this gives an error when loading the entry edit page in the CP:Environment details (please complete the following information):
The text was updated successfully, but these errors were encountered: