Spacena

So this is resolved for now.

Thanks for all the help, Adam. Really appreciate it.

Here’s loom link: https://www.loom.com/share/9f37f98fa6f54cf9bc5211841d2f7cc2

As you can see I added the poster however it doesn’t show up in the frontend.

Since I am adding the embed on the blog page, its archive page is the blog page. So when I go to the blog page as you can see in the loom recording, there is no clickable thumbnail of the web story. Looks like the poster is not loading or working here.

This is the likely cause yes. Do you see any ‘CORS’ related issues if you check for any console errors?

If that’s so, then why was the option to add a poster in an embed given in the first place? Don’t you think if the poster option is given then it should work?

Here’s the screenshot.

Adam, the issue is I don’t find the embedded stories on the archive page. Only the stories that I create on my website are found on the archive page.

Plus, the poster is not working with the embedded stories. Is it because the embedded stories’ links are from 3rd-party websites?

Hey Adam,

1. I shared the info using the form.
2. I am using the built-in feature of the Web Story plugin to embed a story using the link. So not sure if I could share any embed code.
3. I did uninstall one caching plugin.

The height/width thing is working now. I think it started working before I disabled the caching plugin. Not sure what happened there.

That said, I still don’t get the poster thing working. I think in the embed using the link, it’s asking for a poster. When I provide the poster with 900×1200 dimension (3:4 aspect ratio as required by the plugin), it doesn’t show on the frontend. Ideally, the web story should be clickable. When you don’t add a poster, your web story is invalid however, it will still show but won’t be clickable.

Since the poster thing is not working, I don’t see a clickable thumbnail of the web story.

What’s happening here is that when I create a new story, then it goes under the folder: /web-stories/

But when I embed a story in a fresh post, then there is no such folder for that story and it stays on the post page. And hence, it’s not clickable and you are not able to load the story as you would be if it was not an embed.

PS: I could see the poster initially until the story loads completely. I think the story is overriding my submitted poster.

@willchou regarding the first point. I think the better way to go about it would be to make it scrollable no matter where you put your fingers on the screen. This is so practical.

Let’s suppose we give some breathing space to the web stories in the post as a publisher, is it a good UX that people get stuck if they try to scroll while having their fingers on the web story? This is such a bad UX. So instead of going for a workaround about fixing the default width and all, I would recommend making it work no matter whether there is any space surrounding it.

Looks like they rolled back and it’s working fine now.

However, I am still looking for an answer to my first point. Looks like this is a feature yet to be made. Web Stories are not made to work on touchscreens yet. I learnt that it is one of the future features. More details here: https://docs.google.com/spreadsheets/d/10DZZrWJdkjcJXD1vL0VG0PqRhsIqaHkacF_ujOdEwJc/view#gid=1673856264

I raised the issue here thinking it’s a bug: https://github.com/google/web-stories-wp/issues/4973

Any idea when It can be launched because that gives very bad User Experience. You are making something for mobile that can’t work on touchscreen devices is an epic failure.

This is the link for the reference: https://kunalparihar.in/what-is-google-web-stories/

You can see that the embedded web story is not loading. 2-3 days back when I checked it last time, it worked.

Thanks for the reply. I did use site kit plugin and it fixed the problem. I was putting the GA code directly into the header.php earlier. Anyways, thanks guys ??

If I remove the wp_redirect(home_url()) part, the code doesn’t bring any unexpected result. Though the users are prevented to access the restricted area, they are sent to /wp-admin page with nothing displayed as they are no redirects now.