Last modified: 2007-10-03 02:40:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11535 - Special:AddData doesn't work
Special:AddData doesn't work
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
All All
: High major (vote)
: ---
Assigned To: Yaron Koren
Depends on:
  Show dependency treegraph
Reported: 2007-10-02 14:18 UTC by Sergey Chernyshev
Modified: 2007-10-03 02:40 UTC (History)
0 users

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


Description Sergey Chernyshev 2007-10-02 14:18:04 UTC
I've just upgraded to 0.6.4 and SpecialAddData stopped working - no page is being generated at all. I had to downgrade to 0.6.3. by downloading a tarball (usually I use SVN update for upgrades).

These are notices I get in the log:
[Tue Oct 02 07:16:33 2007] [error] [client] PHP Notice:  Undefined index:  no_autocomplete in /home/sergey/www/sites/ on line 1197, referer:
[Tue Oct 02 07:16:33 2007] [error] [client] PHP Notice:  Undefined index:  Conference,category in /home/sergey/www/sites/ on line 1229, referer:
[Tue Oct 02 07:16:33 2007] [error] [client] PHP Notice:  Undefined variable: javascript_text in /home/sergey/www/sites/ on line 1235, referer:
[Tue Oct 02 07:16:33 2007] [error] [client] PHP Notice:  Undefined variable: is_mandatory in /home/sergey/www/sites/ on line 1270, referer:
Comment 1 Yaron Koren 2007-10-02 16:09:37 UTC
Looking at it more with Sergey, I discovered that the problem came when a field in the form is specified as "autocomplete on=", with a blank value, done to disable autocompletion. Some innocent-seeming changes to get the PHP working better in 0.6.4 had caused the code to go into an infinite loop when this setting was on. It'll be fixed in the next version.

The "PHP Notice" errors are a separate, minor issue, although I'll try to fix at least some of those too.
Comment 2 Sergey Chernyshev 2007-10-02 17:37:50 UTC
Yeh, I'm lowering the severity since it only affects forms with "autocomplete on=" set to nothing.
Comment 3 Yaron Koren 2007-10-03 02:40:05 UTC
This is fixed in version 0.6.5.

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