I've overridden the og:image value for my article content type and user entity. When the articles or users are shared everything works like it should be.
The issue happens when
1. I clear the site cache.
2. I use the facebook og debugger tool to check some article node or user url
3. It always says "The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags."
4. Coundn't get the token value to work for that node or user there after.
5. The global default image also doesn't show up.
Took some time to get what was happening and I do understand If i don't clear the cache and use the debugger tool to check how somethings gonna look it won't happen. But everyone clears the cache at some point also i guess facebook scrapes url after a certain time period.
Am using the module for the first time do guide me if i got it all wrong.
This happens with all overridden values not just image property.
Comments
Comment #1
SantVim CreditAttribution: SantVim commentedAdded "This happens with all overridden values not just image property."
Comment #2
SantVim CreditAttribution: SantVim commentedAlso the user and nodes created before installing the module only shows the global values not the overridden values for the individual node and users.
I understand the module is actively maintained and evolving, but it'll be good to know if it happens for anyone else and ways to fix it. Thanks.
Comment #3
SantVim CreditAttribution: SantVim commentedAfter clearing cache the nodes that are edited or resaved show the right og properties. No luck with users though.
Comment #4
DamienMcKennaI've just encountered this too on one particular site. It's a bit of a nuisance.
Comment #5
DamienMcKennaI've seen this happen repeatedly when the "drush cc all" is ran, but it's fine if just the {cache_metatag} table is cleared. It also affects multiple meta tags, not just the Open Graph ones.
Comment #6
SantVim CreditAttribution: SantVim commentedTested this again with 7.x-1.0-beta9+35-dev. the overridden values for nodes are working good now even after cache clear. Tested with at least 20 -25 nodes.
The issue exist with users though, all i am getting is the global default meta for existing users and for new users it works good and defaults to global for some users once cache is cleared. Weird cause it works good on some and not on others.
Comment #7
DamienMcKennaCan you please try again with the latest -dev release?
Comment #8
SantVim CreditAttribution: SantVim commentedHey Damien, tested it with the new rc1, with upgrade and fresh install the same behavior is exhibited with users in my site. Can send you the links if you'd want to have a look.
Comment #9
DamienMcKenna@Dhamub: Yes, please send me a message with some links and I'll be happy to take a look. Thanks.
Comment #10
DamienMcKennaI've confirmed the problem that Dhamub's site is experiencing - some objects are loading their configuration correctly while some others don't - but I haven't been able to track it down yet. Argh.
Comment #11
DamienMcKennaTaking this off the 1.0 release schedule, will follow-up afterwards.
Comment #12
SantVim CreditAttribution: SantVim commentedTested with the latest dev for a few hours, Looks the metatags works fine with authenticated users but defaults to global when the user has other custom roles like editor, moderator etc and admin.
1. When the admin creates a user with an additional role and if the admin or user edit their profile the metatag defaults to global.
2. When a user registers from a path other than user/register like editor/register using regpath module the metatags are reset to global when the profile is edited
Comment #13
SantVim CreditAttribution: SantVim commentedThe issue seems to be created when the drupal roles and profile2 profiles assigned to them have the same name. No more issue with users on cache clear.
Comment #14
DamienMcKennaOk, that's completely confusing. Glad you got it working.
Going to leave this open so it can be looked into some more, now that you've worked out some specifics.
Comment #15
DamienMcKennaDoes this problem still happen with the latest -dev release?