requarks / wiki-v1

Legacy version (1.x) of Wiki.js
https://wiki.js.org
GNU Affero General Public License v3.0
100 stars 75 forks source link

Delet button not working v1.0.10 #33

Open prakhardeep opened 6 years ago

prakhardeep commented 6 years ago

Actual behavior

The delete button is visible on the navigation bar on a given page but nothing happens on clicking it.

Expected behavior

There should be a pop asking user if he wants to delete the page and on confirmation page should be deleted

Steps to reproduce the behavior

Upgrade v1.0.9 to v1.0.10

drampelt commented 6 years ago

Having the same problem, there's an error in the browser console:

[vuex] unknown action type: modalDeletePage/open
NGPixel commented 6 years ago

Delete your browser cache and server cache if any. You're still loading 1.0.9 js files.

drampelt commented 6 years ago

That fixed it for me, thanks!

KovganIV commented 6 years ago

Still dont work... Nice design, but project has a lot of bugs.

KovganIV commented 6 years ago

After click on delete button I dont receive any messages from console and nothing happens

NGPixel commented 6 years ago

@KovganIV If nothing happens and there's nothing in the console / network tab, then you are definitely using js files from an earlier version.

johnalanyoung commented 6 years ago

How does one refresh the server cache? I am getting this issue on a fresh install of v1.0.11.

wikiissue

NGPixel commented 6 years ago

@johnalanyoung This is not a cache issue as you get the correct modal. Do you have any error in the browser console / server logs?

johnalanyoung commented 6 years ago

@NGPixel The browser console shows the following:

DevTools failed to parse SourceMap: http://[DOMAIN]/page/anotherpage/app.scss.map
WebSocket connection to 'ws://[DOMAIN]/socket.io/?EIO=3&transport=websocket&sid=J8So1DR20FtrecSKAAGx' failed: Error during WebSocket handshake: Unexpected response code: 400

I get the above output on every page. I've omitted my test domain.

What server logs should I be checking (I'm new to Node.js)?

NGPixel commented 6 years ago

@johnalanyoung Logs are located in the /logs folder.

johnalanyoung commented 6 years ago

@NGPixel I performed the steps to replicate this problem and watched the log files within /logs and saw nothing. In fact the error log is completely empty.

The httpd error log file (located in var/log/httpd/error_log) however shows the following on every web page i visit for the wiki site. I suppose this is unrelated but its similar to what I saw in the browser console?

[Wed Oct 25 19:44:33.881985 2017] [proxy_http:error] [pid 3220] (70007)The timeout specified has expired: [client [INTERNAL IP]:53150] AH01102: error reading status line from remote server localhost:3000, referer: http://[TESTDOMAIN]/page/article
[Wed Oct 25 19:44:33.882049 2017] [proxy:error] [pid 3220] [client [INTERNAL IP]:53150] AH00898: Error reading from remote server returned by /socket.io/, referer: http://[TESTDOMAIN]/page/article
[Wed Oct 25 19:44:48.143152 2017] [proxy_http:error] [pid 2737] (70007)The timeout specified has expired: [client [INTERNAL IP]:59452] AH01102: error reading status line from remote server localhost:3000, referer: http://[TESTDOMAIN]/all
[Wed Oct 25 19:44:48.143217 2017] [proxy:error] [pid 2737] [client [INTERNAL IP]:59452] AH00898: Error reading from remote server returned by /socket.io/, referer: http://[TESTDOMAIN]/all
[Wed Oct 25 19:44:49.817718 2017] [proxy_http:error] [pid 3558] (70007)The timeout specified has expired: [client [INTERNAL IP]:52874] AH01102: error reading status line from remote server localhost:3000, referer: http://[TESTDOMAIN]/page/article/test
[Wed Oct 25 19:44:49.817777 2017] [proxy:error] [pid 3558] [client [INTERNAL IP]:52874] AH00898: Error reading from remote server returned by /socket.io/, referer: http://[TESTDOMAIN]/page/article/test
johnalanyoung commented 6 years ago

@NGPixel any ideas on this at all? I appreciate your help on this :)

jwfeng commented 6 years ago

@johnalanyoung Encountered the same problem. @NGPixel

olivier37520 commented 6 years ago

Same issue here. using docker and git disabled in configuration http request headers :

:method:DELETE
:path:/actions-et-travaux

JSON server response : {"ok":false,"error":"git --git-dir=repo/.git --work-tree=repo rm actions-et-travaux.md failed with code 1"}

It seems that delete function didn't follow config if git is disabled