-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Blog Plugin broken #1371
Comments
Caused by the new themeAPI. |
@Bloss Thank you. I'm not too familiar with the Plugin or Theme APIs yet. Do you have any idea what should be changed to work with the new Theme API? |
@tedmiston There might be some peoblems to downgrade vuepress by yarn #1379 |
there is a way to resolve the problem quickly but not completely solve the problem. To change |
Actually there are two problems:
The second problem can be fixed by #1383. |
Okay, so a fix to the second problem has been resolved, merged, and release. Any idea what is left to do for |
The roadmap has some info, looks like it'll be getting some dev time over the next month: |
If this is useful to anyone running in to this issue. I fixed this problem for now by changing |
See: #36 (comment) |
Bug report
I'm experiencing an issue on alpha.40 where the blog plugin causes VuePress to crash on startup.
Both disabling the blog plugin in the config and/or downgrading VuePress and the plugin to alpha.37 seem to work sucessfully, however, I cannot get the blog plugin to work on versions >v1.0.0-alpha.37
.Edit: I misspoke — downgrading does not seem to resolve the error, only disabling the plugin entirely.
Please let me know if you have any ideas how to resolve or if I have missed something in the setup.
Version
Versions:
Steps to reproduce
Steps to reproduce:
I followed the directions at https://v1.vuepress.vuejs.org/plugin/official/plugin-blog.html to configure the blog plugin.
Config:
What is expected?
I expect VuePress to start normally including the Blog Plugin.
What is actually happening?
VuePress crashes on startup.
Trying to run dev mode:
Other relevant information
The text was updated successfully, but these errors were encountered: