A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
Hi,
Have you reported this directly to optimizely?
I have just upgraded a project and haven't tested the feature yet. The project i am work on is completely new. Is yours the same?
Interested to know if it is more an upgrade to 12.20.0 to 12.22 5 or somewhere in between as it might be a problem. If you have already upgraded to a version which introduced inline blocks and are now going back to disabling them as it may have already converted the blocks to I line blocks.
As I understood from opti you can only use the disable setting if you have not already upgraded to inline blocks.
Not much help I know, however seems like we should have a way to go back.
Paul
I had a version 12.17.X and updated to 12.22.5
I was informed that you need to opt-in to use inline blocks. Adding appsettings was only for making it explicit that I don't want to have that feature.
It was not reported directly yet.
Thanks,
Dawid
I have updated CMS to version 12.22.5 - I don't want to use Inline block
Tried to use (both in appsettings and Startup.cs):