Pascal Birchler

It won’t magically reappear after deactivating all other plugins — if the data is gone, it’s gone. You would need to restore it from a backup through your hosting provider.

But you can now now try again to create a new story with all plugins deactivated and see if the data is saved properly.

Email sent!

I dug a little deeper and I think your plugin is not removing the WPLANG value of the option, but is still responsible for removing it.

Hmm are you fetching that value using direct database queries? You will notice that calling get_option( 'WPLANG' ) will still return de_DE_formal as the value, so there shouldn’t be any breakage.

But if you do direct queries or circumvent any filters that’s another story… In that case I can look into always persisting that value, no matter what.

The Web Stories plugin stores two types of information in the database: the “raw” story data used for the editor, and the generated HTML markup for the frontend.

The raw story data is stored in the wp_posts.post_content_filtered database column. If you have done some import/export or use a plugin that removes or breaks the data in this column, you’ll get a blank editor. And of course saving a blank story results in a blank story on the frontend too. (Note: you can restore the previous version using the revisions screen if you accidentally saved this blank story)

So yeah, you most likely have some conflicting plugin or botched export that touched the post_content_filtered column and I recommend looking into that, maybe with the help of your site developer or hosting provider.

If this still happens if you disable all plugins and switch themes, then there might be another issue at play. So try that too.

These two lines set the language to en_US when you clear the list of preferred languages. That‘s the same as when you mamually set the language to en_US in the settings. The option is not updated otherwise. The value is always fresh though by filtering the option value (line 448 onwards).

If you have any minimum viable reproduction steps for a bug involving PL that can be verified without purchasing a plugin, that would be helpful.

That‘s just plain wrong, the plugin doesn‘t delete any options. In fact, it _filters_ the option to return the first choice in the list at runtime.

Hi there

The tags / categories feature is purely for organizational purposes right now, they aren’t supposed to be shown anywhere on the frontend.

I see them in both browsers, but your website is very slow to load, so if you click on the story before everything is loaded, it won’t open in a modal with the arrows, but without.

Hi there

There isn’t supposed to be any next/previous button when you view a single story.

The only time you get those buttons is when you use the Web Stories Gutenberg block to display your stories somewhere on the website, e.g. in a carousel. Then you can use arrow buttons to go from one story to the next.

Hi there,

This seems to be a server configuration issue, as this happens even outside of stories when you try to access video files like e.g. https://supermamie.fr/wp-content/uploads/2024/08/astuce-de-grand-mere-moustiques.mp4 directly in Safari. This is because your server does not honor byte range requests à la Range: bytes=0-1, which is basically the browser telling the server “please send me only the first few pieces of the video”

I recommend reaching out to your hosting provider so they can fix their support for the Range HTTP header.

Again, just try opening the above video file in Safari on your desktop and you’ll immediately see the issue. Once that is resolved, your videos should be playing fine everywhere.

Borlabs Cookie is a commercial plugin so I cannot test it.

If it doesn’t support plugins like Preferred Languages (which will be merged into core eventually too), then this needs to be addressed there.

Opening a support request with them sounds like the best course of action.

Closing this topic accordingly.

Images that were uploaded in the Web Stories editor usually have at least 1 term in the web_stories_media_source taxonomy, so you could filter attachments by those with terms in that taxonomy. Tools like WP-CLI are typically helpful in such cases.

However, note that the images might be in use elsewhere on your site as well, so delete them at your own risk and make sure you have a backup first.

Please share the link to your website and your feed so we can take a look.

In case you’re using a caching plugin, try clearing the cache and try using a different browser.

Hi!

That‘s not true. The language can be changed even multiple times during a request using switch_to_locale.

Worth noting that Preferred Languages filters get_locale and supports locale switching too. It has a robust set of tests for all of that.

Not sure what yor comment is about that. Are you doing something special in the load process? Are you saving translated strings in the database?

I don‘t know what that plugin does or how it works, but it sounds like it does unusual things in WordPress. Have you reported this to that plugin already? If not, I recommend doing that first.

In our plugin, the content area has a 2:3 aspect ratio, with the background (“fullbleed area”) having a 9:16 aspect ratio. If a device’s aspect ratio is beyond that (like in the case of the Pixel 6 Pro), then these black bars (what we call letterboxing) are expected and the layout mechanism is working as intended. There is nothing to do about this and we don’t have any plans to change the default aspect ratio at the moment.