We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'd like nuxt-og-image to render og images for error pages. Currently https://creal.jonas-thelemann.de/does-not-exist/__og_image__/og.png (you cannot click on the link, must copy and paste) shows instead of an image (I'll fix the layout, I promise)
nuxt-og-image
An image should show up with the error page's title and description, like
No response
An internal $fetch errors because /does-not-exist does not exist, thus throwing a 500 on the og.png route itself.
$fetch
/does-not-exist
og.png
The text was updated successfully, but these errors were encountered:
Good idea 👍
Sorry, something went wrong.
Hi any progress on this one? I have some pages with archived content where I set the response code to 404.
I get an error for og-img
Error: [GET] "/og-image/image/.../og.json": 500 [Nuxt OG Image] Failed to read the path /... for og-image extraction. [GET] "/...": 404 .
It's the same behaviour for my error pages.
I've tried using defineOgImage(false) to disable og image on these pages but it gives the same result.
No branches or pull requests
Clear and concise description of the problem
I'd like
nuxt-og-image
to render og images for error pages. Currently https://creal.jonas-thelemann.de/does-not-exist/__og_image__/og.png (you cannot click on the link, must copy and paste) showsinstead of an image (I'll fix the layout, I promise)
Suggested solution
An image should show up with the error page's title and description, like
Alternative
No response
Additional context
An internal
$fetch
errors because/does-not-exist
does not exist, thus throwing a 500 on theog.png
route itself.The text was updated successfully, but these errors were encountered: