-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Enhancement: Ability to specify the preview image in the content type #124
Comments
This will be supported in the upcoming release where you can specify in your content type image field that it can be used as the preview image with the {
"title": "Article preview",
"name": "custom-image",
"type": "image",
"isPreviewImage": true
} |
@appieschot this is now available for testing in the https://beta.frontmatter.codes version More information: https://beta.frontmatter.codes/docs/content-types#field-properties |
Awesome work 🚀, two more questions though ;-):
|
@appieschot did you specify the https://frontmatter.codes/docs/settings#frontmatter.content.publicfolder |
Yes, the preview itself shows on the left pane (see screenshot) but throws a image not found in the dashboard. Part of the settings:
|
Would you be able to open the developer tools and check which URL of the image it tries to load? |
Learned something new; didn't know it would be that easy. Image on the left is rendered using: The image in the dashboard is: Manually changing the URL only solves the problem. |
ok, know what the issue is 😀, will fix it |
Will have a look at the code to see if I can help out next time as well 💪 |
@appieschot just tested it in two different projects, should be fixed now. Would you be able to validate it on your end? |
Seems something went wrong during the build |
Ok, found it. Auto-import inserted something in the wrong order. Should be fixed in the next release which is currently publishing. |
Released and works again @appieschot 😁 |
Awesome works great! Can be closed out 🚀 |
Specify which field can be used for the preview image in the content type.
The issue raised by @appieschot on Twitter: https://twitter.com/appieschot/status/1443568883248492554?s=20
The text was updated successfully, but these errors were encountered: