DFC005
Forum Replies Created
-
Forum: Plugins
In reply to: [Getty Images] Updated to WordPress 5.5. and plugin appears brokenCommenting out the following seems to resolve the issue.
// Are we stupid? if($.browser.msie && $.browser.version < 10) { this.set('unsupported', true); }Perhaps it’s a browser update that is causing it?
- This reply was modified 5 years, 8 months ago by DFC005. Reason: Fixing formatting
Oh wow. That is a fantastic tool for finding plugin conflicts!
Indeed to was another plugin that was causing the issue. Disabling it’s SEO functionality has returned my titles to all their glory.
Appreciate the quick response.
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Duplicate Title TagsThat looks to have resolved the issue. Thanks a lot guys!
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Duplicate Title TagsAny idea when the next update will be released?
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Duplicate Title Tags (Yoast)We also have this issue. After a recent update to the AMP plugin, we now have duplicate title tags across the site.
Disabling AMP plugin removes the duplicates.
@devnihil Yes, that looks like exactly the issue we’re experiencing. I’ve added a comment to that issue and will track it there as well. Cheers.
So I assume no one else has reported this issue (or similar) and also been using a caching plugin? As you did mention there was a similar issue and you were trying to ascertain if mine was related.
@omega8719 Do you use WP Rocket (or another) caching plugin?
I swear this all used to work fine before the major upgrade to Yoast.
I haven’t been able to give it a good test but a few quick attempts suggest that indeed, the caching plugin alongside Yoast is causing the issue.
With WP Rocket disabled, I wasn’t able to reproduce the problem.
Is it an issue with the order of the plugins doing their loading perhaps?
Well, it’s hard for us to do that as we can’t push the article to social media without the og:image tag as then it doesn’t present well.
So as mentioned above, we’re currently in the process of being forced to update every single post to guarantee it has the correct tags (as this always resolves the issue).
I’m currently investigating a theory that perhaps our caching plugin is creating a cached version of the page BEFORE Yoast SEO has added the og:image tag, as it seems when it happens if I view the page without the cache, the tag is correctly there.
Going to try and run a few tests to see if I can make it happen without WP Rocket (our caching plugin) running
OK. I was able to reproduce the issue 3/5 attempts at posting an article (just wanted to make sure it was still happening) by immediately visiting the new article in a separate browser that isn’t logged into WordPress.
On those occasions, looking at the source code for the page there were no og:image tags.
After installing the Yoast Test Helper plugin and running the “Reset indexables tables & migrations” I was not able to reproduce this issue after numerous attempts.
We actually a few websites on this server all with the exact same setup (themes and plugins) and moving over to one of the other websites, I was still able to reproduce the issue at least 50% of the time.
Does that suggest there is/was a problem with the “indexables tables & migrations” perhaps?
Here is an example link: https://www.zerotackle.com/storm-set-for-extended-stay-interstate-updated-56613/
Hard to see the issue as we are currently updated every article after posting to make sure it has the og:image tag added.
I can try posting a test article (backdated a while to keep it off the homepage) if that might help but as previously stated, it doesn’t always happen either which is part of the frustration.
Yes, using the latest version of WordPress and Yoast SEO.
We set the featured image for the post and then publish the article. It seems in about 50% of cases though, when viewing the article after publishing, there is no og:image tag set in the header of the article. All other og tags look to be set correctly.
If we update the article, then the og:image tag is set correctly.
Any update on this? Still not working for us.
Well, I can categorically claim that I was part of the 1% and it’s an issue.
We’ve used the same server and same IP address for that server for close to five years. It’s in the same city where we live and post from.
This USE to work fine but something has changed recently (most likely something on the Facebook side) and now doesn’t. I appreciate that it might work for most but when we’re paying customers, just repeating that it should work fine isn’t really good enough.
I am happy to report though that going through the review process has 100% resolved the issue for us. I’ll be cancelling the Premium API as it’s useless now.
I have followed @darrentoogood and submitted two apps for review.
All up the process took less than 48 hours to complete and have since had no problems. Can totally understand now wanting to this for a large number of pages though!