Closing and Next Buttons Missing After Plugin Update

Hi Pascal,

Thanks for your quick reply.

As suggested, I switched to the default Twenty Twenty-Five theme and disabled all other plugins, leaving only the Web Stories plugin active. Unfortunately, the issue still persists. can it be related with server?

thanks.

Hi,

I think I’ve identified the issue with the missing closing and next buttons after updating to version 1.40.0.

I normally use the Classic Editor to generate and insert the shortcode for Web Stories. I don’t use Gutenberg in my workflow. The shortcode I typically use is:

[web_stories title="false" excerpt="false" author="false" date="false" archive_link="true" archive_link_label="" circle_size="200" sharp_corners="false" image_alignment="left" number_of_columns="1" number_of_stories="5" order="DESC" orderby="post_date" view="circles" scrolling="no" /]

However, I tried embedding a block using Gutenberg, and everything worked correctly. Here’s the Gutenberg-generated block:

<!-- wp:web-stories/embed {"blockType":"latest-stories","viewType":"circles","circleSize":125,"order":"asc","fieldState":{"show_title":false,"show_author":false,"show_date":false,"show_image_alignment":false,"show_excerpt":false,"show_sharp_corners":false,"show_archive_link":false,"show_circle_size":true,"show_number_of_columns":false},"taxQuery":{"web_story_category":[]}} /-->///

Interestingly, when both the Classic Editor shortcode and the Gutenberg block are present on the same page, everything works fine. But if I remove the Gutenberg block and leave only the Classic Editor shortcode, the issue returns — the closing and next buttons stop working.

So it seems the new update (1.40.0) has compatibility issues with shortcodes inserted via the Classic Editor.
Is there any way to continue using the shortcode method (without relying on Gutenberg)?
I use Classic Editor + WPBakery or Elementor in most of my workflow, and I also place shortcodes inside text widgets.

Thanks in advance for your help!

That is cool! thank you. looking forward to seing next update

Hi,

Thank you for the update. Unfortunately, version 1.41.0 did not fix the issue on my end. The problem still persists.

Hello Pascal,

This time, when I switched to the default theme, it worked. However, I noticed the following error in my developer console.

There doesn’t seem to be any conflict with plugins, but the issue appears to be related to the theme (which has been working fine for years).

In Firefox:

Uncaught TypeError: The "@wordpress/interactivity" specifier was a bare specifier but was not matched with anything. Relative module specifiers must start with "./", "../", or "/".
web-stories-block-view.js:1:17

In Chrome:

Uncaught TypeError: Failed to resolve module specifier "@wordpress/interactivity". Relative references must start with either "/", "./", or "../".

Hello Pascal

I can confirm that one worked! (1.42.0-alpha.0)
Also there is no error in the console.

Thanks.