-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Hyas SEO v2 twitter:image path problem #16
Comments
What does the content structure looks like? I guess that the |
No, I tested/confirmed this. I suspect it's got something to do with the context and the dot |
Could you provide |
Frontmatter referenced image: images: ["vincent-van-zalinge-9NapHjhwxEg-unsplash.jpg"] Page bundle: │
└───doks-1-2
cover-doks-1-2.png
index.md
vincent-van-zalinge-9NapHjhwxEg-unsplash.jpg Output: <meta property="og:image" content="http://localhost:1313/vincent-van-zalinge-9NapHjhwxEg-unsplash.jpg" /> Should be: <meta property="og:image" content="http://localhost:1313/blog/doks-1-2/vincent-van-zalinge-9NapHjhwxEg-unsplash.jpg" > |
Ah, I missed that — thanks! I can confirm it does work all right with: "otherDependencies": {
"hugo": "0.121.1"
}, |
So we should manually add this to our package.json -- is that the right way to fix this? |
That won't work right now. But, it will work with the upcoming Doks (and Hyas) release that will surface the most important dependencies, so you can update Hugo, Images, and SEO for example — yourself. |
Available soon |
Looking forward to this! |
Tested/verified — solved/works with: "otherDependencies": {
"hugo": "0.123.7"
}, |
Closing |
Discussed in https://github.com/orgs/gethyas/discussions/446
Originally posted by pensivedog December 22, 2023
After upgrading the hyas seo module from v1 to v2, the twitter image path is incorrect. Instead of using, for instance:
localhost:1313/articles/article-title/article-image.jpg
for the twitter image, it now useslocalhost:1313/article-image.jpg
, placing the file name directly after the site root, without the rest of the file path.Any idea how to fix this?
The text was updated successfully, but these errors were encountered: