Updating after a while gives error editing any blueprint and any collection item that has a taxonomy #5082
-
We're running 3.0.27 currently, and I'm trying to update our site to the latest version. Upon doing that though, everything looks ok until I try to edit a blueprint. This can be any of our existing blueprints or a newly created one. We get the following error
We also get the following error when we try to edit any collection item whose blueprint / fieldset uses a taxonomy! All the others work ok, if I remove the taxonomy manually from the blueprint it lets me in again (using vscode as I can't edit in the control panel).
I feel like I'm probably missing something as part of the update but It looks like it's done the relevant changes listed in the 3.1 and 3.2 updates. How to reproduce We updated using
After update: support details Logs
Versions After update: Installation Additional details composer.json
composer.lock |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
Can you share a blueprint you're seeing the issue on? |
Beta Was this translation helpful? Give feedback.
-
Absolutely, although it's all of them, even new ones with the standard items in! So I can click 'Create Blueprint' and choose a collection. Then give it a title and select 'Create Blueprint' and it gives me the same error straight away. The file it creates only has the following in
Here's a pre existing one for our page builder but even our users blueprint gives the same error so it's something pretty fundamental that's wrong.
|
Beta Was this translation helpful? Give feedback.
-
I think I had the same issue. Try to add |
Beta Was this translation helpful? Give feedback.
-
No ideas anyone? We're kinda stuck here as we can't make any changes to our live site :( |
Beta Was this translation helpful? Give feedback.
-
Thanks for sending your site to us. Looks like you had some fields in your fieldsets that had invalid/empty If you remove the following lines, it should spring back to life. I'm not sure why it wasn't exploding for you on 3.0, but it wouldn't have been valid there either. |
Beta Was this translation helpful? Give feedback.
Thanks for sending your site to us. Looks like you had some fields in your fieldsets that had invalid/empty
config
values.If you remove the following lines, it should spring back to life.
I'm not sure why it wasn't exploding for you on 3.0, but it wouldn't have been valid there either.