Some stories do not load for non-admin users

@swissspidy Strange since Ahrefs is saying that we have two meta descriptions.

OK I just checked one of your stories and you’re right. I guess you mistyped before.

I can see two <meta name="description"> in your story.

Now, since you have added that mini-plugin I shared with you earlier, none of these meta descriptions are coming from the Web Stories plugin. They are coming from either your theme or another plugin.

While we will look into what we could do about this from our side (if possible), I still urge you to do some troubleshooting on your end to find the culprit and get it fixed in the theme or plugins causing this.

We cannot provide support for code injected by third-party tools.

Hope that makes sense.

@swissspidy Actually, that plugin was disabled at that time and it does remove that second twitter meta description now.

Not sure what was causing it, but we definitely did not. We also did not have double meta descriptions for posts/pages, only stories. We have even checked if the meta description is empty on Yoast.

Well, in that case it sounds like a resolved issue now.

@swissspidy Still have to make sure that it doesn’t happen to others.

And I am waiting for the response from the hosting’s tech team regarding that character limit.

Will keep you updated, thanks.

@swissspidy Our hosting’s tech team got back to me and said that our URL limit is up to 4096, not around 200 like you said.

Just like I said before, everything is fine on our side and it is an issue/error/glitch with your plugin.

I’m afraid to inform you that this is still plain wrong.

Please check my comment again with steps to reproduce this on your very own site, in the WordPress post editor, without Web Stories even being active.

Repeating the steps here again:

1. Go to Posts -> Add New
2. Open your browser dev tools via F12
3. Under “Console”, type await wp.apiFetch({ path: 'wp/v2/posts?embed=true&_fields=a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,a1,b1,c1,d1,e1,f1,g1,h1,i1,j1,k1,l1,m1,n1,o1,p1,q1,r1,s1,t12' })
4. See no error message.
5. Repeat, but with the path being one character longer: await wp.apiFetch({ path: 'wp/v2/posts?embed=true&_fields=a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,a1,b1,c1,d1,e1,f1,g1,h1,i1,j1,k1,l1,m1,n1,o1,p1,q1,r1,s1,t123' })
6. See error message.

Again, this happens on your site even without the Web Stories plugin active.

The Web Stories plugin relies on your site operating normally.

We cannot provide any more support if it doesn’t.

@swissspidy

Our hosting says: “the max url length is indeed 4096 characters and only once it is reached you get a 414 error”.

Have your hosting provider log into your site and repeat the above steps.

@swissspidy So are you still saying that it is the problem with hosting?

@swissspidy We haven’t done any changes to permalinks or something like that. It is only happening to non-admin users (just like the font issue).

We do not have any issues with our website or other plugins.

Yes, there is clearly a misconfiguration somewhere on your site, be it at the server level or WordPress level.

Have your hosting provider or a developer log into your site and repeat the above steps to start debug this issue.

Hosting is not going to log in since they do not provide such help and it is not caused by them. I will have our developers have a look at this. But it was definitely caused by you (maybe not entirely, but you definitely did something to trigger those errors at the end), since everything was fine before and we didn’t have any changes to our URLs or any other development work recently. And this is only happening to non-admin users.

Of course, it could only be happening to us because of our environment, but we didn’t create this out of thin air. And everything else on the site works fine.

@swissspidy Hello, we just did that character limit test and we don’t get that Error. So the issue is on your side.

I’m afraid that is somewhat hard to believe. Can you please share a screenshot of the result here?

Have you tried longer messages, such as await wp.apiFetch({ path: 'wp/v2/posts?embed=true&_fields=a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,a1,b1,c1,d1,e1,f1,a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,a1,b1,c1,d1,e1,f1,' })