search

requarks / wiki-v1

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

Displaying Old Page Data #171

Closed io-craft closed 5 years ago

io-craft commented 5 years ago

Wiki-V1 MongoDB 3.4

So, in the "normal view" it shows a page version from like several days ago.

Whereas the "source view" version shows the correct page. And the correct page is in the repository.

Where is this old data even coming form? What is going on?

Super annoying, and that coupled with massive issues getting it setup, this has been quite the chore for very few features.

I love the interface, and simplicity... but this is a non starter. I can't even add content at this point.

image

image

NGPixel commented 5 years ago

Try to delete your data/ folder and restart Wiki.js.

io-craft commented 5 years ago

Well, it worked... briefly. Now its doing the same thing after a refresh of the page a few seconds later.

Same behavior after appearing briefly correctly. Navigate around for a few seconds and it fails all over again.

NGPixel commented 5 years ago
io-craft commented 5 years ago

Ubuntu 18.04 Node v10.15.1 Mongo 4.0 Server (Mongo Atlas Cloud DB) Git 2.17.1 (enabled? It's setup and in my config and it seems to be writing and pushing etc... the content in the repository is correct, but for some reason it keeps reverting at the minimum the "Home" page to some weird previous content that isn't even in the repository... as I completly deleted the repo... and recreated it, and it still pulled some version from somewhere...)

This is the only thing in the wiki-error log, after wiping the logs and stopping, starting, and reproducing the issue by simply clicking around between pages until it reverts:

You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection: MongoError: The field 'background' is not valid for an _id index specification. Specification: { v: 2, ns: "iocraft.bruteforces", key: { _id: 1 }, $ at Function.MongoError.create (/storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/error.js:31:11) at /storage/website/node_modules/mongoose/node_modules/mongodb/lib/db.js:1093:80 at /storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/connection/pool.js:469:18 at process._tickCallback (internal/process/next_tick.js:61:11) Unhandled rejection MongoError: The field 'background' is not valid for an _id index specification. Specification: { v: 2, ns: "iocraft.bruteforces$ at Function.MongoError.create (/storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/error.js:31:11) at /storage/website/node_modules/mongoose/node_modules/mongodb/lib/db.js:1093:80 at /storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/connection/pool.js:469:18 at process._tickCallback (internal/process/next_tick.js:61:11) MongoError: The field 'background' is not valid for an _id index specification. Specification: { v: 2, ns: "iocraft.bruteforces", key: { _id: 1 }, $ at Function.MongoError.create (/storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/error.js:31:11) at /storage/website/node_modules/mongoose/node_modules/mongodb/lib/db.js:1093:80 at /storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/connection/pool.js:469:18 at args.(anonymous function) (/storage/bot/node_modules/event-loop-inspector/index.js:138:29) at process._tickCallback (internal/process/next_tick.js:61:11) Unhandled rejection MongoError: The field 'background' is not valid for an _id index specification. Specification: { v: 2, ns: "iocraft.bruteforces$ at Function.MongoError.create (/storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/error.js:31:11) at /storage/website/node_modules/mongoose/node_modules/mongodb/lib/db.js:1093:80 at /storage/website/node_modules/mongoose/node_modules/mongodb-core/lib/connection/pool.js:469:18 at process._tickCallback (internal/process/next_tick.js:61:11)

io-craft commented 5 years ago

I am really sorry. I think it was my derp. I have a git routine for the Wiki itself, and it appears to have been pulling down the data/ directory every time I wiped it.

Everything is functional after disabling that custom cron for my Wiki.js repository.

My fault, and my apologies!