upstartdm

Thanks

Thanks for the reply. It’s a shame we can’t access this functionality again after publishing (either via YOAST or, presumably, WordPress) – for some reason it’s often the only way we can get Twitter to pull in our images, even though the metadata looks OK at first glance.

Thanks for the reply, can I send the URL to you privately? In terms of replicating the issue though, please try this:

– Set the WordPress homepage to display “Your latest posts” in Settings -> Reading.

– Tick both boxes in the “No Custom Excerpts” section of the Advanced Excerpt plugin settings.

– Create a post using a PostX Post Grid #4 block but do *not* add a manual excerpt (I’m not sure if the Post Grid #4 block is only available in the paid version of PostX but the issue may not be limited to this block anyway, I haven’t tested other blocks).

– View the homepage.

The developers at PostX are also looking into this to see if there’s anything they can do on their side, I’ll let you know when I hear back.

BTW we are using the GeneratePress theme.

Thanks for the reply – can I send the screenshots privately?

Thank you, I have sent the report just now.

Many thanks for the detailed reply, much appreciated. I think we probably would want to do more than just change the sort order, some kind of graphical flourish would also be appropriate for these “featured” items, so if that’s possible with CSS and a custom template I think we’ll try that way first. Thanks again for your help!

Extremely useful, George, thanks very much indeed!

Can we have a reply to this please, either here or to our emails?

Thanks, an error is reported:

Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource.

I’ll send you further details by email.

PS not sure if it’s relevant but on reinstallation I got a “We detected that a previous file integrity scan failed due to an unknown reason” error message on the first scan.

I’ve tried that just now but I’m afraid the same issue persists.

Updating to 1.7.1 hasn’t fixed this for us. Can you look again at this issue please?

Hi, running 1.7.0 here – I’m not 100% sure but upgrading to 1.7.0 may be what triggered this behaviour, it feels like both things happened around the same time.

We have the same problem but the plugin developer can’t replicate it.

Thank you!