Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facebook Open Graph metadata isn't scraped #1

Open
1 of 2 tasks
ythecombinator opened this issue Oct 19, 2016 · 2 comments
Open
1 of 2 tasks

Facebook Open Graph metadata isn't scraped #1

ythecombinator opened this issue Oct 19, 2016 · 2 comments

Comments

@ythecombinator
Copy link
Member

ythecombinator commented Oct 19, 2016

Issue Type

  • Bug Report
  • Feature/Improvement Suggestion

Steps to reproduce (if applicable)

  1. Open Open Graph Object Debugger
  2. Fill Input URL with http://blaugame.com/
  3. Fetch new scrape information

Expected Behavior

The debugger should've scraped and recognized all og: metadata available in the index.html file which comes from config.json and is rendered in _social.pug template file.

Other scrapers (eg. iframely) could find metadata in the very same way the OG Debugger should've done:

iframely is cool

Actual Behavior

Instead, the OG Debugger throws a few errors:

OG Debugger isn't cool

Being the main one (Errors That Must Be Fixed):

Object at URL 'https://blaugame.com/' of type 'website' is invalid because a required property 'og:title' of type 'string' was not provided.

Which makes no sense for me since index.html DOES HAVE a og:title - and it's filled with Blau Game.

@ythecombinator ythecombinator changed the title Facebook Open Graph Object Facebook Open Graph metadata isn't scraped Oct 19, 2016
@jonodonovan
Copy link

Is there any compression going on here?

@ythecombinator
Copy link
Member Author

ythecombinator commented Oct 22, 2016

Thanks for your attention, @jonodonovan.

Actually, pug.js pretty option - which adds pretty-indentation whitespace to output instead of making it sound like a compressed one - defaults to false - and we haven't changed it.

But there's no reason for it be affecting the way the debugger scraps it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants