Special:SpecialPages

Jump to: navigation, search

I'm don't can use Special:SpecialPages after instalation of FlaggedRevs - Special:SpecialPages. This page shows "The website has a programming error.". Other pages as I see works. What is programming error can be. This is for the new site [1]. May by that is compability error Version. For this time I exclude FlaggedRevs. Page Special:SpecialPages after that are work. What I can do. FlaggedRevs in this site is needed. And. FlaggedRevs/maintenance/updateStats.php return "Invalid entry". Please help. Thanks.

Vpovilaitis18:04, 26 January 2012

Look at the PHP error log (often in the apache error log).

Aaron00:12, 31 January 2012

Thanks. I'm found for Special:SpecialPages that was needed more memory. But when I execute FlaggedRevs/maintenance/updateStats.php, I'm receiving "Invalid entry".

Vpovilaitis17:30, 1 February 2012

I'd need to know more about what the error looks like. I don't recognize "Invalid entry".

Aaron02:05, 2 February 2012

I'm comment in file extensions/FlaggedRevs/maintenance/updateStats.inc lines:

/*if ( php_sapi_name() != 'cli' ) {
        print( 'Invalid entry' );
        die( 1 );
}*/

after that. I'm receive:

Content-type: text/html

ValidationStatistics A database error has occurred. Did you forget to run maintenance/update.php after upgrading? See: http://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script Query: SELECT MIN(rev_timestamp) AS rt,MIN(n.fr_timestamp) AS nft,MAX(p.fr_rev_id) FROM `encrevision` INNER JOIN `encflaggedrevs` `p` FORCE INDEX (PRIMARY) ON ((p.fr_page_id = rev_page) AND (p.fr_rev_id < rev_id) AND (p.fr_timestamp < rev_timestamp)) INNER JOIN `encflaggedrevs` `n` FORCE INDEX (PRIMARY) ON ((n.fr_page_id = rev_page) AND (n.fr_rev_id >= rev_id) AND (n.fr_timestamp >= rev_timestamp)) WHERE rev_user = '0' AND (rev_timestamp BETWEEN '20120126223222' AND '20120207112002') AND ((rev_id % 1) = 0) GROUP BY rev_id Function: FlaggedRevsStats::getReviewTimesAnons Error: 1104 The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay (localhost)

Vpovilaitis12:29, 7 February 2012

Yes. This sql has error. Full scan is needed for this sql. Must be changed index witch must be used in this sql.

Vpovilaitis20:47, 7 February 2012
 

I'm change extensions/FlaggedRevs/dataclasses/FlaggedRevsStats.php fragment to (change using index PRIMARY to page_rev):

                # For edits that started off pending, how long do they take to get reviewed?
                # Edits started off pending if made when a flagged rev of the page already existed.
                # Get the *first* reviewed rev *after* each edit and get the time difference.
                $res = $dbr->select(
                        array( 'revision', 'p' => 'flaggedrevs', 'n' => 'flaggedrevs' ),
                        array( 'MIN(rev_timestamp) AS rt', 'MIN(n.fr_timestamp) AS nft', 'MAX(p.fr_rev_id)' ),
                        array( 'rev_user' => 0, $timeCondition, "(rev_id % $mod) = 0" ),
                        __METHOD__,
                        array(
                                'GROUP BY'      => 'rev_id',
                                'USE INDEX' => array( 'p' => 'page_rev', 'n' => 'page_rev' )
                                #'USE INDEX' => array( 'p' => 'PRIMARY', 'n' => 'PRIMARY' )
                        ),
                        array(
                                'p' => array( 'INNER JOIN', array( // last review INNER
                                        'p.fr_page_id = rev_page',
                                        'p.fr_rev_id < rev_id',
                                        'p.fr_timestamp < rev_timestamp' ) ),
                                'n'     => array( 'INNER JOIN', array( // next review INNER
                                        'n.fr_page_id = rev_page',
                                        'n.fr_rev_id >= rev_id',
                                        'n.fr_timestamp >= rev_timestamp' ) )
                        )
                );

Vpovilaitis07:03, 8 February 2012

The index usage looks fine in /trunk. I've just backported the query changes to 1.18 in r110921.

Aaron08:21, 8 February 2012
 
 
 
 
 
 
Personal tools

Variants
Actions
Navigation
Support
Download
Development
Communication
Toolbox