Last modified: 2013-04-10 01:16:30 UTC
Error after instalation of FlaggedRevs: Fatal error: Call to undefined method ParserOutput::getFileSearchOptions() in /var/www/Mediawiki_eac/extensions/FlaggedRevs/backend/FlaggedRevs.class.php on line 591
MediaWiki version?
1.18
Which exact version? There are several 1.18 versions... And how did you download and install FlaggedRevs (I am wondering if the version fits to the MediaWiki version)?
Sorry for the incomplete information. My mediawiki instalation version is 1.18.5 The flaggedrevs was installed by git, which took the latest version of the extension, and another attempt was made by 'snapshoot' page of the wiki extension on average. Thanks.
(In reply to comment #4) > The flaggedrevs was installed by git, which took the latest version of the > extension It seems like there is no REL1_18 branch, so did you check out git master, or the REL1_19 branch which should be closer to the MediaWiki codebase that you use? It's unlikely that the most recent development version of FlaggedRevs works well with such an old version of MediaWiki.
Well, I update my Mediawiki to 1.20.3 version and this problem is solved. But some behaviors occurred: 1º: When the variable is like "$wgFlaggedRevsOverride = true;", the stable version isn't the default pages but the modified page and the modified pages are usually displayed before approval. *I dont know what i do. Can you help me?! This is priority**** ---------------------------------------------------------------- 2º: When the variable is like "$wgFlaggedRevsWhitelist = true;", the mediawiki presents: "Warning: in_array() expects parameter 2 to be array, boolean given in /var/www/mediawiki/extensions/FlaggedRevs/backend/FlaggedRevs.class.php on line 895" It's the function "inReviewNamespace" in the code: if ( in_array( $title->getPrefixedDBKey(), $wgFlaggedRevsWhitelist ) ) { ---------------------------------------------------------------- 3º: When the variable is like "$wgFlaggedRevsExceptions = true;", the mediawiki presents: "Warning: Invalid argument supplied for foreach() in /var/www/mediawiki/extensions/FlaggedRevs/frontend/FlaggablePageView.php on line 170" It's the function "userViewsDraftByDefault" in the code: foreach ( $wgFlaggedRevsExceptions as $group ) { ---------------------------------------------------------------- Ps.: My FlaggedRevs is the las stable version from mediawiki.org/wiki/Extension:FlaggedRevs Thanks too much.
(In reply to comment #6) > 2º: > > When the variable is like "$wgFlaggedRevsWhitelist = true;", the mediawiki > presents: > > "Warning: in_array() expects parameter 2 to be array, boolean given in > /var/www/mediawiki/extensions/FlaggedRevs/backend/FlaggedRevs.class.php on > line > 895" > > It's the function "inReviewNamespace" in the code: > > if ( in_array( $title->getPrefixedDBKey(), $wgFlaggedRevsWhitelist ) ) { > > ---------------------------------------------------------------- > > > 3º: > > When the variable is like "$wgFlaggedRevsExceptions = true;", the mediawiki > presents: > > "Warning: Invalid argument supplied for foreach() in > /var/www/mediawiki/extensions/FlaggedRevs/frontend/FlaggablePageView.php on > line 170" > > > It's the function "userViewsDraftByDefault" in the code: > > > foreach ( $wgFlaggedRevsExceptions as $group ) { Both of these variables are expected to be arrays, not 'true'.
Sorry, but I don't know. How do I set the array to this variable "$wgFlaggedRevsOverride"? Could you give me an example? but the pages that were not reviewed are displayed normally? Is there any way to make the page appears for the users only after authorization? Sorry for so many questions and doubts. I'm having trouble. And I appreciate all the support.
(In reply to comment #8) > Sorry, but I don't know. > > How do I set the array to this variable "$wgFlaggedRevsOverride"? Could you > give me an example? > $wgFlaggedRevsOverride is boolean, he said that the others were arrays, which they are. > but the pages that were not reviewed are displayed normally? Is there any way > to make the page appears for the users only after authorization? > You can't hide new pages like this. A new (and unreviewed) page is visible to everyone by default. It's not clear how that would be implemented. I guess one could change the "unreviewed page" notice to something like "this page is unreviewed, click here to see it" and hide all the content until that link is clicked. Anyway, this feature is not present.