Last modified: 2010-05-15 15:48:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10851, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8851 - Array Slice warning
Array Slice warning
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.9.x
PC Windows XP
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.epeoplepress.com/index.php...
:
: 8853 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-01 21:36 UTC by lawrence
Modified: 2010-05-15 15:48 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description lawrence 2007-02-01 21:36:16 UTC
We have a warning message on every wiki page on our server. 

Warning:  array_slice() ['function.array-slice'>function.array-slice]: The first 
argument should be an array in /home/epeople/public_html/languages/Language.php on line 
1115

ALso an invalid argument warning:
Warning:invalid argument supplied for foreach()
in /home/epeople/public_html/includes/SpecialPage.php on line 199

Anyone have a solutions to this problem?

The main pages come up fine, check every file to make sure im not missed one but they 
all seem to have ftp'd over fine.
Comment 1 Rob Church 2007-02-01 21:39:32 UTC
What changed? Upgrade?

If so, were you using precompiled serialized language files before? Either
delete them from serialized/ or re-make them. (Note: Don't delete UtfNormal.ser!)

If that's not the case, then check that all the language files were completely
updated.
Comment 2 lawrence 2007-02-01 22:43:02 UTC
Nothing changed first install. Check to make sure all language files come through 
they appear to be there.
Comment 3 Steve Sanbeg 2007-02-01 23:15:58 UTC
Could be a buggy extension.  If a parser function doesn't initialze properly,
later extensions will break; I think you'd get an error message like that.
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-02-02 00:09:40 UTC
*** Bug 8853 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links