benmyhre

hat option was introduced to conform with WP security standard (probably it will be removed and the ability to execute PHP moved to a special “define” on wp-config.php)

Please note that if you do that without some sort of automation or some very clear notification, sites will break.

Hey thanks!

Just to be clear, I don’t think this is fixed, but rather just a workaround. Right now, we are advising others not to update, as there seems to be other conflicts.

Hey Munir,

I encountered the same issue on what was probably a different site (Hi Justin).

Disabling the plugin fixed the issue. I then found this post and disable the checkbox you indicated. That also seemed to do the trick.

Ben

I have seen this today, as well.

Yes! thanks for the follow up. It was a me issue! ??

@swissspidy perfect. I will roll her site back and just wait for the next release. Thanks for addressing it. I appreciate it greatly.

It might actually be several hundred story pages that need to be edited among 100 published pages. Not a great outcome on this one.

Ahh… I found a separate story where the same issue (she has many … ie https://www.butterandbaggage.com/web-stories/hamburger-helper-without-a-box/) and a few others.

It does seem like the solution is to manually edit each of these stories and remove that. That said, it feels a bit icky for an update like this to suddenly break almost 100 stories and the solution is manually edit each one because files were removed from the repo. I presume there are some users with more than 100 stores created that could be impacted by similar items.

It feels like if someone puts in a whole bunch of effort in using the tool, they shouldn’t just break on an update like this and be a little more sturdy when it comes to backward compatibility.

@swissspidy in this case (both sites) I just fixed it by updating each, so I don’t think there is a need for me to open a support issue. That’s why I just left this as a note rather than a new issue. I suspect you might see other instances of this, but it does seem like one of those issues that is not immediately noticeable. If I find one with an insurmountable number of stories to update, I will open a new issue.

Perhaps a conflict, but it would seem like a new conflict introduced by the newest version of Web Stories.

Of the two environments I experience it in, they are running completely different custom themes. It might not mean that both don’t have the same conflict, but would seem unlikely. There are a few shared plugins/tools like wp rocket and CF Enterprise. I tried without WP Rocket and that didn’t seem to be the issue. The pancake site has really a small number of plugins.

The same individual actually has two completely separate implementations. The same thing was happening on the other, as well. Updating those fixed it, but I do think there is an issue going on here that was revealed with updating from 1.12.0 to 1.13.0

I just encountered a similar issue here https://pancakerecipes.com/web-stories/blueberry-pancakes/ and all web stories on this site. Every web story was just showing as a blank page with no error in the console.

I roll back to 1.12.0 and all of them worked fine.

Reupdated to 1.13.0 and they were all broke.

Following this thread, I just (without changing anything), hit the update button and the individual web story worked. All of the others were still broke. I verified in the validator that it was being seen as a good web story. It was.

Since there were only a few web stories on this site, I just updated each of them.

Currently, this site is on the latest version and all works. The fix that worked for me was to manually update each individual web story.

1) I sent the information in the private link and this site uses WP Rocket, but is also cloudflare enterprise.

2) To confirm, you are seeing a blank second page for the story referenced here? TRUE

What you are seeing is how it should act and how we are currently seeing it. To make it work, we had to manually create the media folder and the grid-placeholder file in the web story plugin files. Without it, and after time passes,this particular page using that template on all historical web stories show up as blank. Just a white page. The other slides are fine.

3)I cant really say… it sounds like the user copied a template from a while ago and then just duplicate it. Here is what she said “I got the slide from their templates and I just duplicate my grouping of slides that includes that slide. It’s no longer in their template folder. I’m not sure what it was called when I initially started using it.”

I added the file types to the CDN setup and that did the trick. Thanks for your help, Pascal. ??

Hi Pascal,

This is what it looks like https://imgur.com/a/rFuKzOk

If you look to the left hand side, that is how it appears in the selector. When I try and add it to the story, it shows the grey area in the wysiwyg.

Then I reupdated and once again recreated the problem. The console looks mostly related to CORS

View post on imgur.com

I then rolled back again and it works fine. There are no errors in console.log. So, per your messaging to Lee, I do think this is somehow related to CORS, but it seems likely to be somehow specific to this update somehow

If I take a piece of video media file with 1.12.0, it works fine.
Do the same with 1.13.0, it is problematic.
Rollback… do the exact same steps with 1.12.0, it is fine.
Now, I have updated a second time to 1.13.0 and it is a problem.

For the record, on my personal site, I have gotten it a few times where videos show up wonky in the story editor and I see things that look similar. Usually, I just reupload the videos and it ends up being fine. That is the first thing I tried with this before I started looking at the versioning. I tried with a different video. Neither helped.

• This reply was modified 3 years ago by benmyhre.