Last modified: 2010-05-15 16:03:27 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 T17964, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15964 - Broken Words and "uninitialized string offset: 0"
Broken Words and "uninitialized string offset: 0"
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.13.x
PC All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://fsserver.pc.chemie.tu-darmstad...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-13 14:42 UTC by Fox Farblack
Modified: 2010-05-15 16:03 UTC (History)
2 users (show)

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


Attachments
--- (upload of the file failed) --- (164.37 KB, text/plain)
2008-10-13 14:42 UTC, Fox Farblack
Details
Page with error message (146.76 KB, image/png)
2008-10-13 14:43 UTC, Fox Farblack
Details
the actual LocalSettings.php. Disabling SMF had no effect on the wiki (5.71 KB, application/x-httpd-php)
2008-10-16 19:12 UTC, Fox Farblack
Details

Description Fox Farblack 2008-10-13 14:42:51 UTC
Created attachment 5422 [details]
--- (upload of the file failed) ---

Four weeks ago our mediawiki show a mixture of the signs used in the code of the pages. So I made an update and everything was ok. A few days later again a lot of words are broken, mixed with other signs as shown on the screenshots.

Today I found out, that I could fix the mainpage by removing all HTML-related <...> tags, but on other pages this solution isn't successful. Since I've "fixed" the mainpage, sometimes an error-message appears:

Notice: Uninitialized string offset: 0 in /home/httpd/mediawiki-1.13.2/includes/parser/Parser.php on line 2143

The dumpfile looks like it's ok, so crashed text-files are not the reason for my problem.
Comment 1 Fox Farblack 2008-10-13 14:43:41 UTC
Created attachment 5423 [details]
Page with error message
Comment 2 Platonides 2008-10-13 15:04:22 UTC
Looks like a misbehaving extension. Disable all extensions and enable them one-by-one until you find which one is producing it.
Comment 3 Fox Farblack 2008-10-13 15:12:34 UTC
As far as I know there are no extensions installed. The page "Special:Version" proofs my opinion, if I'm decrypting correctly.
Comment 4 Platonides 2008-10-13 15:39:30 UTC
Special:Version is too broken to know from it. There're some tables missing, where the extensions would register. Something is filtering an intermediate output and horribly breaking it. Look at LocalSettings for extensions. You can publish to ask for advice, but remember to remove the user & password settings.
Comment 5 Tim Starling 2008-10-16 04:45:31 UTC
(In reply to comment #4)
> Special:Version is too broken to know from it. There're some tables missing,
> where the extensions would register. 

Hook display in Special:Version can be re-enabled by putting:

$wgSpecialVersionShowHooks = true;

at the bottom of LocalSettings.php. 
Comment 6 Fox Farblack 2008-10-16 19:12:37 UTC
Created attachment 5443 [details]
the actual LocalSettings.php. Disabling SMF had no effect on the wiki
Comment 7 Platonides 2008-10-16 21:33:37 UTC
Now it *is* better. Reload the page. Sometimes you get a sane output and others a screwed one. Clean caches (squids, apc, add a $wgCacheEpoch...) and verify if there're still broken pages.
Comment 8 Fox Farblack 2008-10-16 22:31:37 UTC
Thanks a lot for your nice help. Your last hint worked.
I hope I'll understand this stuff some day.
Wish you all the best!

fox

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


Navigation
Links