{"action":"created","issue":{"url":"https://api.github.com/repos/sybrew/the-seo-framework/issues/285","repository_url":"https://api.github.com/repos/sybrew/the-seo-framework","labels_url":"https://api.github.com/repos/sybrew/the-seo-framework/issues/285/labels{/name}","comments_url":"https://api.github.com/repos/sybrew/the-seo-framework/issues/285/comments","events_url":"https://api.github.com/repos/sybrew/the-seo-framework/issues/285/events","html_url":"https://github.com/sybrew/the-seo-framework/issues/285","id":308205419,"number":285,"title":"Can TSF Address Facebook Debugger Warnings?","user":{"login":"GuardianMajor","id":5274181,"avatar_url":"https://avatars2.githubusercontent.com/u/5274181?v=4","gravatar_id":"","url":"https://api.github.com/users/GuardianMajor","html_url":"https://github.com/GuardianMajor","followers_url":"https://api.github.com/users/GuardianMajor/followers","following_url":"https://api.github.com/users/GuardianMajor/following{/other_user}","gists_url":"https://api.github.com/users/GuardianMajor/gists{/gist_id}","starred_url":"https://api.github.com/users/GuardianMajor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GuardianMajor/subscriptions","organizations_url":"https://api.github.com/users/GuardianMajor/orgs","repos_url":"https://api.github.com/users/GuardianMajor/repos","events_url":"https://api.github.com/users/GuardianMajor/events{/privacy}","received_events_url":"https://api.github.com/users/GuardianMajor/received_events","type":"User","site_admin":false},"labels":[{"id":618807852,"url":"https://api.github.com/repos/sybrew/the-seo-framework/labels/Support","name":"Support","color":"ff9900","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2018-03-23T23:23:44Z","updated_at":"2018-04-22T20:51:11Z","closed_at":null,"author_association":"NONE","body":"When running the Facebook debugger on posts that don't immediately show up correctly based on their meta values, you see something like this:\r\n\r\n> Inferred Property\r\n> The provided 'og:image' properties are not yet available because new images are processed asynchronously. To ensure shares of new URLs include an image, specify the dimensions using 'og:image:width' and 'og:image:height' tags. Learn More\r\n> \r\n> Extraneous properties specified\r\n> The following properties are specified on the webpage but NOT supported for the specified 'og:type': article:publisher, article:author, article:published_time, article:modified_time\r\n\r\nWith regard to the first one, is TSF able to provide the `og:image:width` and `og:image:height` values to alleviate this issue they complain about? Wondering if upon putting in the link to the \"social image\", it can perhaps parse these values and include them upon posting to effectively resolve this? It appears to also affect Google+ using their validator shows issues as well (among a few other complaints), which I will post an issue for separately (See #286).\r\n\r\nNow the second one, I understand that while perhaps they don't use those values, others might? Am I correct in assuming that? or is it something that can be reasonably removed and no longer relevant?\r\n\r\nI tried to keep it short this time like you asked, hopefully I have given you enough information. If not, please let me know. TIA."},"comment":{"url":"https://api.github.com/repos/sybrew/the-seo-framework/issues/comments/383411379","html_url":"https://github.com/sybrew/the-seo-framework/issues/285#issuecomment-383411379","issue_url":"https://api.github.com/repos/sybrew/the-seo-framework/issues/285","id":383411379,"user":{"login":"GuardianMajor","id":5274181,"avatar_url":"https://avatars2.githubusercontent.com/u/5274181?v=4","gravatar_id":"","url":"https://api.github.com/users/GuardianMajor","html_url":"https://github.com/GuardianMajor","followers_url":"https://api.github.com/users/GuardianMajor/followers","following_url":"https://api.github.com/users/GuardianMajor/following{/other_user}","gists_url":"https://api.github.com/users/GuardianMajor/gists{/gist_id}","starred_url":"https://api.github.com/users/GuardianMajor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GuardianMajor/subscriptions","organizations_url":"https://api.github.com/users/GuardianMajor/orgs","repos_url":"https://api.github.com/users/GuardianMajor/repos","events_url":"https://api.github.com/users/GuardianMajor/events{/privacy}","received_events_url":"https://api.github.com/users/GuardianMajor/received_events","type":"User","site_admin":false},"created_at":"2018-04-22T20:51:10Z","updated_at":"2018-04-22T20:51:10Z","author_association":"NONE","body":"@sybrew Thank you my friend, appreciate it ❤️ \r\n\r\nDon't you think the inherent use of TSF implies some degree of competence for the users who enable it? The prefill method of the existing system would alleviate confusion and the empty to provide it manually will either be ignored by the user or used by those who know what it is. A small (i) hover can give them warning about leaving it empty if unsure what you are doing. Doesn't the benefit outweigh the potential \"issues\"? \r\n\r\nJust thinking out loud here, ultimately your call. I agree that a perfect solution would be best, but until you can reach that based on the considerations of it, it would be a useful stopgap measure. Doesn't say it has to be a permanent solution, just a lower resource bridge until such time \"perfect\" solution can be realized. The problem with Facebook is that once they have completed the \"scrape\" and missing data is not populated, it won't scrape again unless you go into object debug and force it.\r\n\r\nFor the title, I saw your reference and completely understand, thank you for the update on that. I did see your workaround and will be testing it. Quick look seems to be a very elegant workaround, thank you for sharing it. I will let you know if any \"changes\" are necessary but so far looking at it, seems very elegant, thank you."}}
{"actor":{"display_login":"GuardianMajor"}}