ggoddard

Thanks Pascal @swissspidy for your prompt response.

With regards to this point:

Is there any code that we can add to ensure it refreshes to the latest version and goes back to Page 1 of the story?

Unfortunately, no. This is a feature of the Web Stories format itself and nothing done by this plugin. If you prefer a different behavior, I recommend opening a feature request at

Using this URL as an example:

https://brainsparker.com/web-stories/inapp-user-guides-creative-vibes/

As I understand it then, if the User opens the story and swipes until Page 4 and then stops.

When they return they’ll still see Page 4.

Could you tell me what happens then if:

• we’ve updated the content of Page 4 to create v2. Will they see v1 until they refresh in which case they’ll see v2?
• what if we update the content of Page 2. When they return and see Page 4 v1 and swipe back to Page 2, will they see v1 or v2 of Page 2?

The reason this is important to us, is that we are embedding the Web Stories in our app (iOS) using the direct link. The way it’s set up is that the User is not given the option to refresh the page. They can tap “Done” and go back to the main menu.

The ideal is that when they tap on the Web Story again it opens on Page 1 with the latest version.

We migrated these micro-learning modules from another platform (Kites.io) and whenever we updated them in Kites, they would immediately show as updated in the app.

We’ve been playing around with our cache setup rules in WP Rocket, to limit local caching.

I was wondering if there was any code my developer could add to the way the Web-Stories work in the embedded web pages – to ensure it always delivers the latest version of the story.

I appreciate this might be out of your remit, but it’s worth asking just in case.

Thanks
Gabriella