Skip to content

Problems with the parser #26

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

Closed
jeena opened this issue Feb 10, 2014 · 5 comments
Closed

Problems with the parser #26

jeena opened this issue Feb 10, 2014 · 5 comments
Labels

Comments

@jeena
Copy link
Collaborator

jeena commented Feb 10, 2014

I am having problems with what I get from the parser, it looks like there is some kind of a bug or something. I am parsing this website: http://snarfed.org/2014-02-03_re-barnaby-walters-latest-php-library-extracted-from-taproo and when you use the PHP parser mf2 it seems to parse the website like expected: http://pin13.net/mf2/?url=http://snarfed.org/2014-02-03_re-barnaby-walters-latest-php-library-extracted-from-taproo but with G5/microformats2 I get this JSON: https://jeena.net/t/mf2.json

You can see that h-entry here has two URLs:

    "url": [
      "http://snarfed.org/",
      "http://snarfed.org/2014-02-03_re-barnaby-walters-latest-php-library-extracted-from-taproo"
    ]

even if the first URL shouldn't be there because it belongs either to the h-card at the top or to to the author h-card in the middle.

@aaronpk
Copy link
Member

aaronpk commented Jul 5, 2014

I think this is the same issue I'm noticing in #31

@mmitchellg5
Copy link

see comment in #31

@mmitchellg5
Copy link

(investigating) as soon as i eliminate the parent h-entry on the snarfed.org site, it starts parsing correctly

@mmitchellg5
Copy link

The textwidget h-card is not declared as a property and is a floating h-card nested within the h-entry — causing the issue noted in the comment in #31

@veganstraightedge
Copy link
Contributor

@jeena @aaronpk I believe this is fixed in 3.0. I just did a test and it looks good to me. Please upgrade and run your comparison too. Re-open this issue if necessary.

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

No branches or pull requests

5 participants