Steve Evans
Forum Replies Created
-
Forum: Plugins
In reply to: [upPrev] Sorry, you are not allowed to access this page.Same, updated to latest version and the fly-out is now gone along with all the customisation I had and when I try to go to settings from the plugin list I get the same error, of not being allowed to access the page.
Have changed back to full text feeds and it truncates correctly, but it isn’t including the images like it used to.
Also experiencing this.
In case it’s helpful, it began in the morning of July 28th for us, and our first two posts that day were fine (truncated the email at the more tag as expected), but the third onwards wasn’t.
We hadn’t updated anything, as we never do in the daytime. So it seems this bug isn’t in the plugin, but rather in the Jetpack codebase at the developers end.
Hope this might be helpful in getting a fix sooner than later, we’ve lost around 4,000 pageviews a week because of this, but can’t change the feeds to extracts to fix the emails, as we use the feed in other ways.
Hi there. We have another example of this where Yoast is not following the rule you mention above.
See: https://www.reinsurancene.ws/nat-cats-drive-losses-in-2018-but-totals-down-significantly-swiss-re/
The image in this post is clearly much larger than 200px in height and width, but still the Yoast plugin has used the default image in the og:image tag.
Would you mind having a look please and let me know if this is still intended behaviour by the plugin?
Many thanks!
This has literally only been happening since the latest updates, so if it is expected behaviour then Yoast SEO was not following the expected rules previously.
It’s changed, we can look back at earlier posts and see much smaller images being put into the OG:image tag by Yoast.
Am assuming you’re now leaving this alone? It’s a little annoying when stuff changes but isn’t put in the changelogs…
Hi Marius,
Thanks for continuing to look. So we have had a good example today of the problem.
A 550 × 185 pixel png company logo was uploaded to an article page and the og:image tage contained the default image.
We then increased the size of the same logo slightly to 550 x 200 and then it did work, the logo image was used in the og:image field on the post page.
Also, in case of use, a square image of 416 X 416 also worked correctly, filling the og:image. So it’s not a width issue alone.
It appears to be an issue with the area dimensions of the image.
Also, in case helpful, our default image is 433 X 300 in size.
Hope this helps in diagnosing the problem!
Thanks,
Steve.
Thanks, but this isn’t about the homepage, this is about the default image being used instead of the post image in the og:image tag on post pages.
Is the bug related? I see nothing in Github explaining the post pages issue, only the homepage issue others are having.
Resolved, thanks to a reply from Adam H to a support request. Thanks Jeremy too!
Sorry, final note on this issue. When I look at the WordPress.com account I now have the site successfully connected to I can see Notification alerts about the statistics for artemis.bm going back a long way.
However, when I view the stats on WordPress.com I can only see a few page views since I reconnected it and none of the last four years or more of data.
So, it appears I may be connected to the right account but at the moment I do not have access the the stats data?
Ugghh, ok I just re-connected it by deleting and reinstalling Jetpack, but I only have stats from that time onwards on WordPress.com for this site.
So, I think I’ve connected it to the wrong WordPress.com account, but I can’t remember my other username.
Can you help? Either the username or the email address attached to the correct WordPress.com account would be a huge help.
Thanks!
Ok thanks Jeremy, am relieved to hear that nothing is lost at least!
I will try removing Jetpack and reconnecting. However I just had a thought that perhaps I am trying to connect it to the wrong WordPress.com username.
Are you able to tell me which username account I should be attempting to connect it to please?
Thanks!
I should note that Akismet still works strangely, but still if I go to WordPress.com I cannot see this site listed under those connected.