I have an issue when a change needs to be made to the rest of the content in an area not covered by the experiment. For example, I have the following code:
<p>This is a paragrph</p>
<div class=“callout”>
<a href=“#”>This is what I’m testing</a>
</div>
<p>this is another paragraph</p>When the node is initially published I set up a simple A/B test with two variations on div.callout. Lets say an hour later the editor of the story realizes they misspelled ‘paragraph’ in the first paragraph, so they edit the node in Drupal and make the change. But what is happening is when they go back to view their post they realize the change didn’t come through because the A/B test is running. So I have to stop the test and set it up again. What this means is I am unable to test things for long periods of time and get the necessary number of users to know winning variations.
I've been working with the support team at Optimizely and this is not the intended behavior, only the tested area should be overwritten by jQuery. Have you experienced this before? Is there a fix for this? Do I have something misconfigured?
Thanks!
Comments
Comment #2
BrandonHundt commentedComment #3
DeeZone commentedWhat type of caching are you using on your site and specifically the page you're having issues with?
Comment #4
BrandonHundt commented@DeeZone We run Nginx across multiple frontend servers (Google Cloud Platform). Due to this we actually don't cache our story pages outside of the default Drupal caching. So no Varnish or anything like that.
Comment #5
DeeZone commented@brandonhundt Have you made any progress on this issue? This module is only responsible for apply the call to the Optimizely js file. How that file manages the contents of the page to apply it's A?B test is a function of Optimizely the service.
I'm going to mark this ticket as closed. Please reopen it if you feel there is in fact a bug related to this module.
Comment #6
DeeZone commented