Halo 1.3.0 发布
版本更新了,主题不支持,然后退回 1.2 了。
@Ryan Wang
Ryan Wang
请务必确保你正在使用的主题已经适配了 1.3.0 再进行更新。目前在 https://github.com/halo-dev 下的主题均已适配 1.3.0。
升级1.3.1 旧的主题无法删除了,自己能手动删除一下吗?
Drinker 无法删除的体现是?
- 已编辑
Ryan Wang 有个错误提示框,但是没有字显示。F12 有报错:
chunk-vendors.cae1e3cb.js:50 DELETE https://wangfashuai.top/api/admin/themes/codelunatic_simple 403
(anonymous) @ chunk-vendors.cae1e3cb.js:50
e.exports @ chunk-vendors.cae1e3cb.js:50
e.exports @ chunk-vendors.cae1e3cb.js:38
Promise.then (async)
c.request @ chunk-vendors.cae1e3cb.js:1
(anonymous) @ chunk-vendors.cae1e3cb.js:10
delete @ chunk-0b44f908.d38ba511.js:1
handleDeleteTheme @ chunk-0b44f908.d38ba511.js:12
onOk @ chunk-0b44f908.d38ba511.js:12
onClick @ chunk-vendors.cae1e3cb.js:56
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
nt @ chunk-vendors.cae1e3cb.js:16
e.$emit @ chunk-vendors.cae1e3cb.js:16
handleClick @ chunk-vendors.cae1e3cb.js:38
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
Qi.o._wrapper @ chunk-vendors.cae1e3cb.js:16
chunk-vendors.cae1e3cb.js:45 error | jsdelivr | Response failed Error: Request failed with status code 403
at e.exports (chunk-vendors.cae1e3cb.js:22)
at e.exports (chunk-vendors.cae1e3cb.js:33)
at XMLHttpRequest.d.onreadystatechange (chunk-vendors.cae1e3cb.js:50)
e.printLogMessage @ chunk-vendors.cae1e3cb.js:45
t.forEach.t.indexOf.t.indexOf.e.isEnabled.r.<computed> @ chunk-vendors.cae1e3cb.js:45
(anonymous) @ app.9e02d773.js:1
Promise.then (async)
c.request @ chunk-vendors.cae1e3cb.js:1
(anonymous) @ chunk-vendors.cae1e3cb.js:10
delete @ chunk-0b44f908.d38ba511.js:1
handleDeleteTheme @ chunk-0b44f908.d38ba511.js:12
onOk @ chunk-0b44f908.d38ba511.js:12
onClick @ chunk-vendors.cae1e3cb.js:56
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
nt @ chunk-vendors.cae1e3cb.js:16
e.$emit @ chunk-vendors.cae1e3cb.js:16
handleClick @ chunk-vendors.cae1e3cb.js:38
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
Qi.o._wrapper @ chunk-vendors.cae1e3cb.js:16
chunk-vendors.cae1e3cb.js:45 error | jsdelivr | Server response status 403
e.printLogMessage @ chunk-vendors.cae1e3cb.js:45
t.forEach.t.indexOf.t.indexOf.e.isEnabled.r.<computed> @ chunk-vendors.cae1e3cb.js:45
(anonymous) @ app.9e02d773.js:1
Promise.then (async)
c.request @ chunk-vendors.cae1e3cb.js:1
(anonymous) @ chunk-vendors.cae1e3cb.js:10
delete @ chunk-0b44f908.d38ba511.js:1
handleDeleteTheme @ chunk-0b44f908.d38ba511.js:12
onOk @ chunk-0b44f908.d38ba511.js:12
onClick @ chunk-vendors.cae1e3cb.js:56
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
nt @ chunk-vendors.cae1e3cb.js:16
e.$emit @ chunk-vendors.cae1e3cb.js:16
handleClick @ chunk-vendors.cae1e3cb.js:38
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
Qi.o._wrapper @ chunk-vendors.cae1e3cb.js:16
chunk-vendors.cae1e3cb.js:45 error | jsdelivr | Business response status undefined
e.printLogMessage @ chunk-vendors.cae1e3cb.js:45
t.forEach.t.indexOf.t.indexOf.e.isEnabled.r.<computed> @ chunk-vendors.cae1e3cb.js:45
(anonymous) @ app.9e02d773.js:1
Promise.then (async)
c.request @ chunk-vendors.cae1e3cb.js:1
(anonymous) @ chunk-vendors.cae1e3cb.js:10
delete @ chunk-0b44f908.d38ba511.js:1
handleDeleteTheme @ chunk-0b44f908.d38ba511.js:12
onOk @ chunk-0b44f908.d38ba511.js:12
onClick @ chunk-vendors.cae1e3cb.js:56
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
nt @ chunk-vendors.cae1e3cb.js:16
e.$emit @ chunk-vendors.cae1e3cb.js:16
handleClick @ chunk-vendors.cae1e3cb.js:38
nt @ chunk-vendors.cae1e3cb.js:16
n @ chunk-vendors.cae1e3cb.js:16
Qi.o._wrapper @ chunk-vendors.cae1e3cb.js:16
chunk-vendors.cae1e3cb.js:22 Uncaught (in promise) Error: Request failed with status code 403
at e.exports (chunk-vendors.cae1e3cb.js:22)
at e.exports (chunk-vendors.cae1e3cb.js:33)
at XMLHttpRequest.d.onreadystatechange (chunk-vendors.cae1e3cb.js:50)
- 已编辑
我之前使用的版本是1.1.1,今天尝试更新1.3.1失败,经过一番查找发现需要先升级到1.2.x后才能更新到1.3.x,于是我尝试升级1.2.0,但还是报错,信息如下
2020-03-29 23:40:01.909 ERROR 1454 --- [ main] o.s.boot.SpringApplication : Application run failed
org.flywaydb.core.api.FlywayException: Validate failed:
Detected failed migration to version 2 (migrate 1.2.0-beta.1 to 1.2.0-beta.2)
at org.flywaydb.core.Flyway.doValidate(Flyway.java:273) ~[flyway-core-6.1.0.jar!/:na]
at org.flywaydb.core.Flyway.access$100(Flyway.java:72) ~[flyway-core-6.1.0.jar!/:na]
at org.flywaydb.core.Flyway$1.execute(Flyway.java:155) ~[flyway-core-6.1.0.jar!/:na]
at org.flywaydb.core.Flyway$1.execute(Flyway.java:147) ~[flyway-core-6.1.0.jar!/:na]
at org.flywaydb.core.Flyway.execute(Flyway.java:511) ~[flyway-core-6.1.0.jar!/:na]
at org.flywaydb.core.Flyway.migrate(Flyway.java:147) ~[flyway-core-6.1.0.jar!/:na]
at run.halo.app.listener.StartedListener.migrate(StartedListener.java:86) ~[classes!/:1.2.0]
at run.halo.app.listener.StartedListener.onApplicationEvent(StartedListener.java:58) ~[classes!/:1.2.0]
at run.halo.app.listener.StartedListener.onApplicationEvent(StartedListener.java:33) ~[classes!/:1.2.0]
at run.halo.app.listener.StartedListener$$EnhancerBySpringCGLIB$$b5a3867c.onApplicationEvent(<generated>) ~[classes!/:1.2.0]
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:403) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:360) ~[spring-context-5.2.1.RELEASE.jar!/:5.2.1.RELEASE]
at org.springframework.boot.context.event.EventPublishingRunListener.started(EventPublishingRunListener.java:98) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
at org.springframework.boot.SpringApplicationRunListeners.started(SpringApplicationRunListeners.java:71) ~[spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:321) [spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.1.RELEASE.jar!/:2.2.1.RELEASE]
at run.halo.app.Application.main(Application.java:35) [classes!/:1.2.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_232]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_232]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_232]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_232]
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) [halo-latest.jar:1.2.0]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) [halo-latest.jar:1.2.0]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:51) [halo-latest.jar:1.2.0]
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52) [halo-latest.jar:1.2.0]
2020-03-29 23:40:01.913 INFO 1454 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Shutting down ExecutorService 'taskScheduler'
2020-03-29 23:40:01.952 INFO 1454 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default'
2020-03-29 23:40:01.957 INFO 1454 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated...
2020-03-29 23:40:01.993 INFO 1454 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed.
2020-03-29 23:40:01.996 INFO 1454 --- [ main] io.undertow : stopping server: Undertow - 2.0.27.Final
这是什么原因?
我现在回退到1.1.1也不行了
跪求大佬帮忙,让我从1.1.1升级到1.3.1
Colan 建议长期观测下。
miantiao5115 数据备份下,卸载重装
congjinruo 怎么操作才能卸载干净?
这个版本升级太坑了 好多字段都改了
ctlyt 如果仔细看了发布信息,那就没坑。
这一次的更新是提醒主题作者该更新主题了
虽然前面发布了好几次主题大牛一直没有给主题放上去(其实是我写的主题还有很多BUG),
经过这一次的大修改应该是没有致命的bug
完美支持 halo1.3.1
我看来机会来了
主题安装地址:https://github.com/cuntoulaoyangtou/halo-them-ctlyt-gently.git
预览地址:http://ctlyt.yunypan.cn
希望大佬支持扶我上墙
推荐个主题,支持 Halo 1.3.1,https://github.com/jinqilin721/halo-theme-fantastic
看效果:https://blog.xinac.cn/
急急急!!!更新后,首页进不去了,请问怎么一般是什么问题啊?
liem 我都在更新说明不止一个地方说明了,那我还能怎么做?为了后面的便利,这次修改主题api是利大于弊的。迟早都要做。
liem 官网上所有主题均已适配,升级下就好了。 如果你自己改了主题或者自己做的。那就只能自己修改了。