-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
hey @seoulaja, sorry to see you are having this issue. Since the last update we are now enforcing the proper component structure for screens. The section component wasn't designed to be a child of a lot of other components so we have a validation rule that prevents that from being done (see this line of the code for example where the property that prevents this is set) For context, that ticket to enforce the validation in the latest update can be found here: #10229 To prevent this change from breaking existing apps like yours that wouldn't pass the new validation rules, it was set to only apply to apps that were created after the update. Unfortunately in your situation, that also included old apps that have been imported after the update. When you imported the app it was being treated as a newly created app so the validation was being applied. After some discussion with the engineers yesterday, a fix has been written to ensure that the new validation rules don't apply to legacy app exports that have been imported in the new version. The pull request for that fix is here: #11384 That fix should be merged soon and will be included in the next build of Budibase. Once it is released it should allow you to work with your older apps as normal! Hope this helps |
Beta Was this translation helpful? Give feedback.
-
Hi @andz-bb Thank you for your response and the incoming solution for the older apps, really appreciate it! One of the reasons I love using sections is because it makes the layout easier and it still looks good in mobile view. It would be great if the same behavior can be implemented in the container. Thank you! |
Beta Was this translation helpful? Give feedback.
hey @seoulaja, sorry to see you are having this issue.
Since the last update we are now enforcing the proper component structure for screens. The section component wasn't designed to be a child of a lot of other components so we have a validation rule that prevents that from being done (see this line of the code for example where the property that prevents this is set)
For context, that ticket to enforce the validation in the latest update can be found here: #10229
To prevent this change from breaking existing apps like yours that wouldn't pass the new validation rules, it was set to only apply to apps that were created after the update. Unfortunately in your situation, that also included…