mikerev

By spinning I mean that when you click on one of the posts impacted by the defect, your browser sits there spinning as it’s querying for the feature image of the post, not a native function or anything.

I checked the media library to confirm they were not being generated. Historically (since about June 2018) your plugin has worked flawlessly. Another point of interest is that WordPress To Buffer recently released a feature that seemed similar to your plugin, so it’s plausible that there is some sort of contention being created between the two when posts are generated and it lines up with when the defect started. Anecdotal at best but I haven’t had enough time to refresh my staging environment and try to recreate the issue, I basically just confirmed that downgrading to the version your plugin supports corrected the issue.

Here’s an example of a post that generated the image on publish:
https://www.fishin.life/catching-aquarium-fish-for-your-fish-tank-at-home-diy/

Here’s an example of a post that was published but did not generate a default image:
https://www.fishin.life/new-years-eve-lower-illinois-river-trout-footage/

The examples probably aren’t very meaningful because the former was taken after the downgrade, the latter was before the downgrade.

I’m more than happy to give you guys an account on the instance to troubleshoot if it helps, just let me know where to send a onetimesecret or pgp or whatever with credentials. If that doesn’t work I will refresh my staging environment tomorrow and try to recreate the issue there. I’d be surprised if it’s my production configuration, the entire thing is codified and idempotent via Ansible with a well defined pattern. Thanks again for the help guys, love your product (when it’s working :))

• This reply was modified 7 years, 5 months ago by mikerev.