Extension talk:Oversight 2
deletion[edit]
The difference is an additional permission unhiderevision, that allows undo of hiding revisions --Steevie 17:58, 19 May 2010 (UTC)
- Yup, the point being that unhiding the revisions is easier, doesn't require DB access, and is logged. --Shaiaqua 01:51, 16 June 2010 (UTC)
- I think it should be deleted. It just adds another permission, that is no longer needed because the original Oversight extension itself has been superseded by RevisionDelete. --Diego Grez ¡hablemos! 00:07, 24 June 2010 (UTC)
- RevDelete can't restore revisions hidden by the Oversight extension though. It can only restore revisions that were hidden by RevDelete. To unhide oversighted revisions you have to restore them manually from the database, or you could use this extension. That's why it was created, and why it may still be useful for some wikis. Reach Out to the Truth 01:50, 24 June 2010 (UTC)
- I know. I said that RevDelete superseded Oversight, that has these problems. --Diego Grez ¡hablemos! 01:53, 24 June 2010 (UTC)
- And indeed it has. I'm not advising using Oversight to hide revisions, unless for some reason someone is still using an old version of MediaWiki from before RevisionDelete existed. But the fact is that Oversight has been used in the past, so Oversight 2 may be of use to some of those wikis. Reach Out to the Truth 02:02, 24 June 2010 (UTC)
- I know. I said that RevDelete superseded Oversight, that has these problems. --Diego Grez ¡hablemos! 01:53, 24 June 2010 (UTC)
- RevDelete can't restore revisions hidden by the Oversight extension though. It can only restore revisions that were hidden by RevDelete. To unhide oversighted revisions you have to restore them manually from the database, or you could use this extension. That's why it was created, and why it may still be useful for some wikis. Reach Out to the Truth 01:50, 24 June 2010 (UTC)
- I think it should be deleted. It just adds another permission, that is no longer needed because the original Oversight extension itself has been superseded by RevisionDelete. --Diego Grez ¡hablemos! 00:07, 24 June 2010 (UTC)
Error[edit]
(translated so "informs" might be a wrong word) Error SQL-query:
CREATE TABLE IF NOT EXISTS `/*$wgDBprefix*/hidden` ( `hidden_page` int(11) UNSIGNED NOT NULL DEFAULT '0', `hidden_namespace` int(11) NOT NULL DEFAULT '0', `hidden_title` varchar(255) character SET latin1 collate latin1_bin NOT NULL DEFAULT , `hidden_comment` tinyblob NOT NULL, `hidden_user` int(5) UNSIGNED NOT NULL DEFAULT '0', `hidden_user_text` varchar(255) character SET latin1 collate latin1_bin NOT NULL, `hidden_timestamp` char(14) character SET latin1 collate latin1_bin NOT NULL DEFAULT , `hidden_minor_edit` tinyint(1) NOT NULL DEFAULT '0', `hidden_deleted` tinyint(1) NOT NULL DEFAULT '0', `hidden_rev_id` int(8) UNSIGNED DEFAULT NULL, `hidden_text_id` int(8) UNSIGNED DEFAULT NULL, `hidden_by_user` int(11) DEFAULT NULL, `hidden_on_timestamp` char(14) character SET latin1 collate latin1_bin DEFAULT NULL, `hidden_reason` text, `unhidden_by_user` int(11) DEFAULT NULL, `unhidden_on_timestamp` char(14) DEFAULT NULL, `unhidden_reason[...]
MySQL informs:
- 1103 - Incorrect table name '/*$wgDBprefix*/hidden'
What i am supposed to do now? --84.249.165.65 14:56, 22 April 2009 (UTC)
- You are supposed to replace the variable - /*$wgDBprefix*/ becomes the value of that variable from localsettings.php --Shaiaqua 01:50, 16 June 2010 (UTC)
I don't understand, can you explain, please ? Thanks Chrischros34 22:56, 16 August 2010 (UTC)
- When you configured MediaWiki, you did so in a file called LocalSettings.php. If you look through that file, you will see a line that says $wgDBprefix = "SOMETHING";
- , where SOMETHING could be mw_ or similar, or empty. Whatever SOMETHING is, you put in place of /*$wgDBprefix*/, so with mw_ it becomes mw_hidden. --Shaiaqua 06:23, 17 August 2010 (UTC)