Henrik Fransas
Mar 21, 2015
(0 votes)

Error in EPiServer Self-Optimizing Block

This blog post is just to inform about a bug in EPiServer Self-Optimizing Block that other might encounter. I have reported it to support so it will be handled.

We are using EPiServer Self-Optimizing Block to test different versions of blocks on the site and now we have noticed that there are a error in this addon when it contains a block with a xform in it. The error is that the postback in the xform does not work and the user ends up on a erro page instead of the thank you page, like this:
We solved it by removing the Self-Optimizing Block so now the xform works but we are not able to test different versions of it.

If you would like to try it out yourself it can be reproduced in a standard Alloy site like this:

1: Create a new Alloy MVC site with the Visual Studio AddOn (the error is in both 7.19 and 8.2)
2: Add the addon  EPiServer Self-Optimizing Block with nuget
3: Run the site and first create two FormBlock that use the Contact Us form
4: Create a Self-Optimizing block that use the two blocks you have just created
5: In one page add one of the formblock and add the other one on another page
6: In a third page add the Self-Optimizing block you have just created
7: Verify that the formblock works by trying them on the pages you have added them on
8: Try out the Self-Optimizing block and now you will have a error page when posting it.¨

Mar 21, 2015


valdis Mar 24, 2015 09:28 PM

What is grand base controller (just before Mvc one) for optimization block?

Henrik Fransas
Henrik Fransas Mar 24, 2015 10:19 PM

Good question, for this one I am using controller-less block so it should be the default controller from EPiServer that service it, but maybe Allan has more info, he said like this in twitter:
not surprised by the bug.. Postbacks to blocks in blocks is new territory for us.

valdis Mar 25, 2015 03:24 PM

Hm, interesting.. even block controller are inheriting from EPiServer abstract controller base that should handle unknown actions..

Daniel Norlin
Daniel Norlin Apr 14, 2016 02:23 PM

Is this fixed? Did not find a bug report in http://world.episerver.com/support/Bug-list/ for this issue.

Henrik Fransas
Henrik Fransas Apr 14, 2016 02:26 PM

I do not think so Daniel and with the new epi form it is maybe an obselete question also.

I have not tried form in an self optimizing block. Have you?

Please login to comment.
Latest blogs
IDX21323 - RequireNonce is true, Nonce was null

We have multiple clients configured with Azure Active Directory (Microsoft Entra) for requiring authentication when accessing their website. The...

David Drouin-Prince | Oct 1, 2023 | Syndicated blog

Minimum Detectable Effect in Optimizely Web Experimentation

Understanding Minimum Detectable Effect Minimum Detectable Effect (MDE) is a core statistical calculation in Optimizely Web Experimentation. In...

Matthew Dunn | Oct 1, 2023 | Syndicated blog

Configured Commerce - Introduction to Long-Term Support (LTS) Releases

First off, for those who have not had a chance to meet me yet, my name is John McCarroll, and I am the Technical Product Manager for the Optimizely...

John McCarroll | Sep 29, 2023

Auto-translate with OpenAI in Optimizely CMS

You can now auto-translate content using your favorite online AI service, inside the old trustworthy Episerver.Labs.LanguageManager!

Tomas Hensrud Gulla | Sep 29, 2023 | Syndicated blog