Forums » General
Wiki = haxx0rz
Somebody rudely edited the wiki in a manner not suitable for drawing up information about VO. The comments left by the perpetrator lead me to believe that the attack was aimed specifically at our resident popcorn master. I'd put this in the community projects section, but honestly who goes there?
Huh. I wonder if this isn't just a joke? They left all the informaton intact.
Nonetheless, it is a rather tasteless joke.
Nonetheless, it is a rather tasteless joke.
Lies!
another reason to hate wiki's :P
Nice recovery, Roguelazer.
Just kidding. This was all apparently just a strange delusion on my part. Not getting enough VO I suppose.
Um, one of the advantages of wikis, you know, is that old information is not lost, so if someone comes and defaces an entry, the people in charge can restore it, like, in two clicks. So don't be surprised that something vanishes as it wasn't ever there.
Next time take a screenie.
Next time take a screenie.
Yes, Mediawiki stores all changes, ever. Any sysop on the wiki gets a convenient rollback button in order to restore changes like these. You can view any old revisions of a page by clicking on the "History" link near the top of the page.
Jex is correct about how wikis store data. It was never "lost", all Rogue had to do was to select the closest-to-intact version from the page history, click "rollback" and bam, there's the old page again.
Three of VO-Wiki's admin team (Roguelazer, Lemming and myself) are constantly monitoring the wiki for such actions and cleaning up when they occur.
Thanks for the heads-up.
--Miharu
Three of VO-Wiki's admin team (Roguelazer, Lemming and myself) are constantly monitoring the wiki for such actions and cleaning up when they occur.
Thanks for the heads-up.
--Miharu
Lemming?
I sent an email to site5, as it appears the server the site is on broke.
Edit:
All is good in wiki land once again.
Edit:
All is good in wiki land once again.
Glad I could help you out this morning, Rogue...
Hehe.
Hehe.
i keep getting database errors :(
I emailed site5 in the morning and they resolved the issue.