Specific page blueprint not working after upgrading from 3.2.16 to 3.2.17 or 3.2.18 #4577
-
I have two pages on a site based on a blueprint called "Segments." They worked great in version 3.2.16. However, after upgrading to version 3.2.17 or 3.2.18, I see a server 500 error, and only for pages based on that blueprint. All other pages in the site (based on other blueprints) work as expected, and the pages based on the "Segment" blueprint worked fine in 3.2.16 and earlier. The segments.yaml code is below. Excuse the unelegant, repetitive way of dealing with each segment (title_1, content_1, photo_1, image_position_1, title_2, content_2, etc.). I'm only a very amateur coder, so I didn't know how to code this more elegantly and iteratively (yet). Any idea why this could be failing in 3.2.17 and 3.2.18, but not in 3.2.16?
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
Can you give more information about the issue? What is it that's "failing"? Do you get an error message, are some fields not showing, does the page timeout? |
Beta Was this translation helpful? Give feedback.
-
I just updated my site to 3.2.22, and everything is working as expected now. |
Beta Was this translation helpful? Give feedback.
I just updated my site to 3.2.22, and everything is working as expected now.
--Ron