Pascal Birchler

Thanks for your report!

Could you perhaps provide some additional information about where this was happening and what action you were trying to perform? There’s usually a button to copy error messages, which would be extremely helpful for us.

Like I said, you need to check the source code and look for the ID attribute of the <amp-story-page>. You can’t just use a page number.

Here’s an example:

On https://wp.stories.google/stories/turning-your-dream-into-reality/, page number 10 looks like this in the source code: <amp-story-page id="849d7482-9ad6-46af-b8d3-00278643199d".

Thus, I can link to it directly using https://wp.stories.google/stories/turning-your-dream-into-reality/#page=849d7482-9ad6-46af-b8d3-00278643199d

It’s generally possible to link to a specific page by looking at the id attribute of the <amp-story-page> element in the source code and using that to construct a link. See https://amp.dev/documentation/components/stories/amp-story#branching

Hi there,

Thanks for reaching out.

I don’t know at which stage of the upload process Polylang’s media duplication feature kicks in, but according to some documentation there is a pll_enable_duplicate_media filter in the plugin to conditionally disable the feature. You could use that to improve compatibility with Web Stories. Example:

<?php
/**
 * Plugin Name: Do not duplicate posters
 * Description: Prevent Polylang from duplicating poster images originating from Web Stories.
 */

add_filter(
  'pll_enable_duplicate_media',
  function ( $enable, $post_id ) {
    // Use $post_id to determine whether it's a poster image.
    // For example (untested):
    if ( has_term( 'poster-generation', 'web_story_media_source', $post_id ) {
      return false;
    }

    return $enable;
  },
  10,
  2
);

Hope that helps!

It sounds like you are doing a lot of optimizations for LCP already. Using a CDN for images is a good choice.

A big part of LCP is the time to first byte (TTFB), which is essentially the server load time. Using a caching solution (either with a plugin or on the network layer) will help improve TTFB and LCP. So I recommend looking into that.

As for other recommendations in PageSpeed Insights, they can be taken with a grain of salt as they don’t know the specific AMP / Web Stories stack.

The release cadence has perhaps slowed down, but the plugin is very stable at this point 🙂

Hope this helps!

The default behavior is simple: users see the new version only when they refresh the page.

For your use case, what might work is the live-story feature as described at https://amp.dev/documentation/components/amp-story#live-story

With this feature, the story would frequently poll the server for new updates. It’s meant for live content (e.g. during a sports game) but with a low poll interval it might work for you. The default is 15 seconds, but something like 1 hour might be good enough.

The caveat: the Web Stories WordPress plugin doesn’t support this feature out of the box. However, your developer may be able to add the necessary markup changes using a custom “sanitizer” class as in this example: https://gist.github.com/swissspidy/a86f1eabefd24827646973ec4f497539

Hi there,

Thanks for reaching out! Sorry to hear you’re having troubles bringing back those stories.

I noticed some of the images in this particular story are broken/missing. When you upload an image to WordPress, it creates various sub-sizes (thumbnails) for use one different screen sizes, but somehow some of them no longer exist. That causes the story pages to be blank

For example: one of the story pages references https://homemadehooplah.com/wp-content/uploads/2021/03/creamy-spinach-dip-2-1200.jpg and its smaller version https://homemadehooplah.com/wp-content/uploads/2021/03/creamy-spinach-dip-2-1200-400x599.jpg, but the latter doesn’t exist anymore.

There are a few easy ways to address this:

1. Edit the story, remove each image that looks good in the preview but not on the actual site, and simply upload it again.
2. Use a plugin such as Regenerate Thumbnails to create those missing image sub-sizes without having to manually edit the stories.
3. Use an image CDN such as Jetpack’s Photon that deals with image sub-sizes so you don’t have to, and also helps with compressing images to make them smaller.

Option 2 is probably the easiest since you mentioned there are a few affected stories.

After that, I definitely recommend updating to the latest version of the plugin again 🙂