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

Yoast json import results in error 500 #10

Closed
georgegebbett opened this issue May 12, 2022 · 10 comments · Fixed by #16
Closed

Yoast json import results in error 500 #10

georgegebbett opened this issue May 12, 2022 · 10 comments · Fixed by #16

Comments

@georgegebbett
Copy link
Owner

On pages such as https://www.joyfulhealthyeats.com/no-bake-vegan-cookie-dough-energy-balls/, the ld-json is added by an SEO plugin called Yoast. This plugin puts the data on the page in a Graph, which is not currently well handled.

@mshuflin
Copy link

This results in a 500 Internal Server Error for me.

@georgegebbett
Copy link
Owner Author

georgegebbett commented May 13, 2022

Me too - this is the ld/json contained on that page. The @Recipe is in there, just not where the scraper expects to find it... It really is infuriating how this data which is supposed to be standardised is in fact implemented completely randomly 😡

@georgegebbett georgegebbett changed the title Yoast json import Yoast json import results in error 500 May 13, 2022
@mshuflin
Copy link

These sites are still giving me a error 500. Anything (logs or something) I can provide that would help?

@georgegebbett
Copy link
Owner Author

The contents of the JS console is always helpful - have you pulled the latest images?

@mshuflin
Copy link

{
    "statusCode": 500,
    "message": "Unable to extract Recipe metadata from provided url",
    "error": "Internal Server Error"
}

with this URL https://www.budgetbytes.com/weeknight-black-bean-chili/

@mshuflin
Copy link

Here are screenshots from the console.

Screen Shot 2022-05-22 at 6 16 00 PM

Screen Shot 2022-05-22 at 6 15 51 PM

Screen Shot 2022-05-22 at 6 15 39 PM

@georgegebbett
Copy link
Owner Author

I've just tested and this works fine for me

image

I think this is likely an issue with you running an older version - it does not automatically update. What is in your docker-compose.yml file? Is it the same as the latest version in this repo?

@mshuflin
Copy link

Thanks for your patience. I got it working. My docker-compose.yml matches the one in the repo, but I did not have the latest image. Normally with dockerhub, portainer will pull the latest image when I recreate the container. But I had to pull the image, then recreate the container. working now!

@georgegebbett
Copy link
Owner Author

Amazing, glad you got it working! I'm about to do a release with a few enhancements so there will be another new image shortly - I've made changes to the way images are tagged which I'm hoping will make the whole thing play nicer with Portainer too. Out of interest, are you running RB as a Portainer Stack?

@mshuflin
Copy link

Yeah, I just paste the docker-compose.yml into the stack.

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

Successfully merging a pull request may close this issue.

2 participants