在本地测试 solo3.3 出现问题
solo3.3 文章评论问题
相关帖子
-
-
-
-
-
-
Jackwu199 •作者
Connected to server [2019-03-18 04:46:39,512] Artifact solo3-3:war exploded: Artifact is being deployed, please wait... 18-Mar-2019 16:46:42.075 信息 [RMI TCP Connection(3)-127.0.0.1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. [WARN ]-[2019-03-18 16:46:42]-[org.b3log.latke.Latkes:531]: !!!!Runtime mode is [DEVELOPMENT], please make sure configured it with [PRODUCTION] in latke.properties if deployed on production environment!!!! [INFO ]-[2019-03-18 16:46:43]-[com.zaxxer.hikari.HikariDataSource:110]: HikariPool-1 - Starting... [INFO ]-[2019-03-18 16:46:43]-[com.zaxxer.hikari.HikariDataSource:123]: HikariPool-1 - Start completed. [INFO ]-[2019-03-18 16:46:44]-[org.b3log.solo.SoloServletListener:127]: Solo is running [2019-03-18 04:46:44,412] Artifact solo3-3:war exploded: Artifact is deployed successfully [2019-03-18 04:46:44,413] Artifact solo3-3:war exploded: Deploy took 4,900 milliseconds Connected to server [2019-03-18 04:46:39,512] Artifact solo3-3:war exploded: Artifact is being deployed, please wait... 18-Mar-2019 16:46:42.075 信息 [RMI TCP Connection(3)-127.0.0.1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. [WARN ]-[2019-03-18 16:46:42]-[org.b3log.latke.Latkes:531]: !!!!Runtime mode is [DEVELOPMENT], please make sure configured it with [PRODUCTION] in latke.properties if deployed on production environment!!!! [INFO ]-[2019-03-18 16:46:43]-[com.zaxxer.hikari.HikariDataSource:110]: HikariPool-1 - Starting... [INFO ]-[2019-03-18 16:46:43]-[com.zaxxer.hikari.HikariDataSource:123]: HikariPool-1 - Start completed. [INFO ]-[2019-03-18 16:46:44]-[org.b3log.solo.SoloServletListener:127]: Solo is running [2019-03-18 04:46:44,412] Artifact solo3-3:war exploded: Artifact is deployed successfully [2019-03-18 04:46:44,413] Artifact solo3-3:war exploded: Deploy took 4,900 milliseconds
1 回复 -
Jackwu199 •作者
Uncaught TypeError: Cannot read property 'emoji' of undefined at e.t (<anonymous>:27:42823) at new e (<anonymous>:27:45338) at <anonymous>:27:62609 at Array.forEach (<anonymous>) at new <anonymous> (<anonymous>:27:62552) at new t (<anonymous>:27:68056) at Page.toggleEditor (<anonymous>:68:23) at HTMLTextAreaElement.<anonymous> (<anonymous>:49:12) at HTMLTextAreaElement.dispatch (pjax.min.js:1) at HTMLTextAreaElement.m.handle (pjax.min.js:1) 3VM309:27 Uncaught TypeError: Cannot read property 'emoji' of undefined at e.t (<anonymous>:27:42823) at new e (<anonymous>:27:45338) at <anonymous>:27:62609 at Array.forEach (<anonymous>) at new <anonymous> (<anonymous>:27:62552) at new t (<anonymous>:27:68056) at Page.toggleEditor (<anonymous>:68:23) at HTMLTextAreaElement.<anonymous> (<anonymous>:49:12) at HTMLTextAreaElement.dispatch (pjax.min.js:1) at HTMLTextAreaElement.m.handle (pjax.min.js:1) t @ VM309:27 e @ VM309:27 (anonymous) @ VM309:27 (anonymous) @ VM309:27 t @ VM309:27 toggleEditor @ VM312:68 (anonymous) @ VM312:49 dispatch @ pjax.min.js:1 m.handle @ pjax.min.js:1
1 回复 -
-
Jackwu199 •作者
我是在本地上通过 idea 运行的
要是没有打开 sass 监听的话,前端评论是正常的,没有问题
但是我把 watcher sass 配置好,就出现
问题
我就测试
前端可以显示,但是评论就乱了1 回复 -
-
欢迎来到这里!
我们正在构建一个小众社区,大家在这里相互信任,以平等 • 自由 • 奔放的价值观进行分享交流。最终,希望大家能够找到与自己志同道合的伙伴,共同成长。
注册 关于