Last modified: 2007-10-03 02:40:05 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 64.236.170.228] PHP Notice: Undefined index: no_autocomplete in /home/sergey/www/sites/techpresentations.org/w/extensions/SemanticForms_0.6.4/includes/SF_FormPrinter.inc on line 1197, referer: http://www.techpresentations.org/Special:AddPage?page_name=My+Presentation&form=Presentation&= [Tue Oct 02 07:16:33 2007] [error] [client 64.236.170.228] PHP Notice: Undefined index: Conference,category in /home/sergey/www/sites/techpresentations.org/w/extensions/SemanticForms_0.6.4/includes/SF_FormPrinter.inc on line 1229, referer: http://www.techpresentations.org/Special:AddPage?page_name=My+Presentation&form=Presentation&= [Tue Oct 02 07:16:33 2007] [error] [client 64.236.170.228] PHP Notice: Undefined variable: javascript_text in /home/sergey/www/sites/techpresentations.org/w/extensions/SemanticForms_0.6.4/includes/SF_FormPrinter.inc on line 1235, referer: http://www.techpresentations.org/Special:AddPage?page_name=My+Presentation&form=Presentation&= [Tue Oct 02 07:16:33 2007] [error] [client 64.236.170.228] PHP Notice: Undefined variable: is_mandatory in /home/sergey/www/sites/techpresentations.org/w/extensions/SemanticForms_0.6.4/includes/SF_FormPrinter.inc on line 1270, referer: http://www.techpresentations.org/Special:AddPage?page_name=My+Presentation&form=Presentation&=
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.
Yeh, I'm lowering the severity since it only affects forms with "autocomplete on=" set to nothing.
This is fixed in version 0.6.5.
