You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have articles in various formats, such as Markdown (.md) and AsciiDoc (.adoc). However, due to the code at this link, when the post_asset_folder is enabled, only articles with the same extension as defined in new_post_name can be rendered. Other types of documents are treated as asset files and ignored. I want articles with different file extensions to be rendered correctly.
Actual behavior
My new_post_name setting is "year:month:day-:title.md", so only Markdown articles with the .md format are rendered, while other articles are ignored.
I am wondering if there is a configuration for a whitelist or blacklist to distinguish which files are articles and which are asset files. For example: post_extension: ["md", "adoc"], and anything beyond this will be considered as asset files.
I am wondering if there is a configuration for a whitelist or blacklist to distinguish which files are articles and which are asset files. For example: post_extension: ["md", "adoc"], and anything beyond this will be considered as asset files.
As far as I know, there are none. I'm not sure what side effects there might be, but if you (or someone) submit a PR about this, we could be accepted.
Check List
hexo version
to check)Expected behavior
I have articles in various formats, such as Markdown (.md) and AsciiDoc (.adoc). However, due to the code at this link, when the post_asset_folder is enabled, only articles with the same extension as defined in new_post_name can be rendered. Other types of documents are treated as asset files and ignored. I want articles with different file extensions to be rendered correctly.
Actual behavior
My new_post_name setting is "year:month:day-:title.md", so only Markdown articles with the .md format are rendered, while other articles are ignored.
How to reproduce?
Is the problem still there under
Safe mode
?yes
Your Node.js & npm version
Your Hexo and Plugin version
Your
package.json
Your site's
_config.yml
(Optional)No response
Others
No response
The text was updated successfully, but these errors were encountered: