Ongoing issues with the yoast plugin and the Kalium theme.
Seems there is something is the theme generating OG content. Which gives me all kinds of problems, when using on social media. Some pages don't work at all and i've had to rename the page to the correct thing, as i'm unable to affect titles, descriptions etc.
When checking the link through the Facebook OG sharing debugger:
More Than One OG URL Specified Object at URL 'http://www.formatldn.com/showreel/' of type 'article' is invalid because it specifies multiple 'og:url' values: http://www.formatldn.com/showreel/, http://www.formatldn.com/showreel/.
-I checked in a sharing debugger for this page which won't display any meta description content, or the title for some reason. But is seeing the image i've pointed to.
This is the warning i get which i suspect is the cause of the issue:
Inferred Property The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property The 'og:description' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Share App ID Missing The 'fb:app_id' property should be explicitly provided, Specify the app ID so that stories shared to Facebook will be properly attributed to the app. Alternatively, app_id can be set in url when open the share dialog.
Pretty sure there is a compatibility issue with the theme and Yoast after seeing this on a basic portfolio page, with only the basics changed (title, description and image). Nothing else apart from a Meta title, description and image have been input. Even when it's all removed i keep getting these errors.
I've added this to the functions.php but for some reason on the "portfolio page" for example - this is still seeing a title which doesn't exist titled: Portfolio Archive. The page is actually called Portfolio, and the Yoast Facebook/Twitter title is set to FORMAT.LDN - Portfolio nowhere does it say "Archive" so it's still being gneeated. It's alson seeing the correct description, but rather the footer on the page.
The Twitter Card preview returns this and doesn't display anything.
INFO: Page fetched successfully INFO: 15 metatags were found INFO: twitter:card = summary_large_image tag found ERROR: Invalid value (message: Field description failed to validate because: text expects tag property, but not found in Map().) WARN: this card is redirected to http://www.formatldn.com/portfolio/
Facebook Sharing Debugger returns this:
Warnings That Should Be Fixed
Inferred Property
The 'og:description' property should be explicitly provided, even if a value can be inferred from other tags.
Share App ID Missing
The 'fb:app_id' property should be explicitly provided, Specify the app ID so that stories shared to Facebook will be properly attributed to the app. Alternatively, app_id can be set in url when open the share dialog.
The archive page will have the title you set in "title" field in theme options.
After disabling the Kalium built in OG:META you can manage og:description via Yoast, because Kalium no longer generates these tags, so configure settings in Yoast for OG meta.
If only it were that simple. All of the things you've suggested are already done. See attached images. I've set the Yoast information to the correct settings and content. And it still doesn't work. Nor does the title of the page work. Seems Kalium somehow still is generating something which is showing in those facebook/twitter scrapes.
Then I need to check this out by myself, because I have no idea why is this happening so I need your WP credentials to analyze the issue.
Can you please share your WP credentials here, because I need to login to your site and test this issue. Your information is safe here (private) in this thread.
To include your credentials click Insert Credentials button in editor toolbar. (See how)
After debugging your issue, I realized that this was a page slug and custom post type prefix conflict, many users tend to have this problem when they use the same page slug with existing post type:
The problem was a "priority" of rewrite rules, which is how WordPress works and thus it doesn't recognize as an error. However that fix will solve these issues.
Ongoing issues with the yoast plugin and the Kalium theme.
Seems there is something is the theme generating OG content. Which gives me all kinds of problems, when using on social media. Some pages don't work at all and i've had to rename the page to the correct thing, as i'm unable to affect titles, descriptions etc.
When checking the link through the Facebook OG sharing debugger:
-I checked in a sharing debugger for this page which won't display any meta description content, or the title for some reason. But is seeing the image i've pointed to.
This is the warning i get which i suspect is the cause of the issue:
Pretty sure there is a compatibility issue with the theme and Yoast after seeing this on a basic portfolio page, with only the basics changed (title, description and image). Nothing else apart from a Meta title, description and image have been input. Even when it's all removed i keep getting these errors.
Hoping for some help.
Thanks
David
Hi David,
We have included our own OG meta generator and seems that it is conflicting with yoast, so heres how to fix that:
Can you please add the following code in functions.php (end of file):
This should work for you, let me know about that.
If you are testing this on Facebook parser, make sure to fetch new content, because there might be already a cached version of your page.
I've added this to the functions.php but for some reason on the "portfolio page" for example - this is still seeing a title which doesn't exist titled: Portfolio Archive. The page is actually called Portfolio, and the Yoast Facebook/Twitter title is set to FORMAT.LDN - Portfolio nowhere does it say "Archive" so it's still being gneeated. It's alson seeing the correct description, but rather the footer on the page.
The Twitter Card preview returns this and doesn't display anything.
INFO: Page fetched successfully
INFO: 15 metatags were found
INFO: twitter:card = summary_large_image tag found
ERROR: Invalid value (message: Field description failed to validate because: text expects tag property, but not found in Map().)
WARN: this card is redirected to http://www.formatldn.com/portfolio/
Facebook Sharing Debugger returns this:
Warnings That Should Be Fixed
Hi David,
To change the title of Portfolio Archive, go to Theme Options > Portfolio Settings > Other Settings
(view large version)
The archive page will have the title you set in "title" field in theme options.
After disabling the Kalium built in OG:META you can manage og:description via Yoast, because Kalium no longer generates these tags, so configure settings in Yoast for OG meta.
Hi Arlind,
If only it were that simple. All of the things you've suggested are already done. See attached images. I've set the Yoast information to the correct settings and content. And it still doesn't work. Nor does the title of the page work. Seems Kalium somehow still is generating something which is showing in those facebook/twitter scrapes.
Very confusing indeed.
Hi David,
Then I need to check this out by myself, because I have no idea why is this happening so I need your WP credentials to analyze the issue.
Can you please share your WP credentials here, because I need to login to your site and test this issue. Your information is safe here (private) in this thread.
To include your credentials click Insert Credentials button in editor toolbar. (See how)
Hi David,
After debugging your issue, I realized that this was a page slug and custom post type prefix conflict, many users tend to have this problem when they use the same page slug with existing post type:
http://wordpress.stackexchange.com/questions/135146/resolve-a-custom-post-type-name-vs-page-permalink-conflict-same-slug
So I have added this code in functions.php to fix this:
(view large version)
Now your portfolio page shows the exact page content.
OMG thanks so much for fixing this. Was that something i did?
Best
David
Hi David,
Great to hear that!
The problem was a "priority" of rewrite rules, which is how WordPress works and thus it doesn't recognize as an error. However that fix will solve these issues.
Have a great day.