Page MenuHomePhabricator

PHP warnings in Special:Import (PHP v4.1.2)
Closed, ResolvedPublic

Description

I know that PHP v4.1.2 is considered 'old', but here's an error that I have
encountered in my 4.1.2-based wiki (it does not exist on my 4.3.11-based wiki).
Feel free to mark as WONTFIX if appropriate, but it might be a simple tweak
that would help those of us who are unable to upgrade PHP.

The warnings occur when Special:Import is viewed - the following is output at
the top of the file (before the DOCTYPE):

Warning: Call-time pass-by-reference has been deprecated - argument passed by
value; If you would like to pass it by reference, modify the declaration of
xml_set_object(). If you would like to enable call-time pass-by-reference, you
can set allow_call_time_pass_reference to true in your INI file. However,
future versions may not support this any longer. in
/.../wiki/includes/SpecialImport.php on line 270

Warning: Call-time pass-by-reference has been deprecated - argument passed by
value; If you would like to pass it by reference, modify the declaration of
call_user_func(). If you would like to enable call-time pass-by-reference, you
can set allow_call_time_pass_reference to true in your INI file. However,
future versions may not support this any longer. in
/.../wiki/includes/SpecialImport.php on line 526

Warning: Call-time pass-by-reference has been deprecated - argument passed by
value; If you would like to pass it by reference, modify the declaration of
call_user_func(). If you would like to enable call-time pass-by-reference, you
can set allow_call_time_pass_reference to true in your INI file. However,
future versions may not support this any longer. in
/.../wiki/includes/SpecialImport.php on line 527


Version: 1.5.x
Severity: minor
OS: Windows 2000
Platform: PC

Details

Reference
bz3761

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 8:53 PM
bzimport set Reference to bz3761.
bzimport added a subscriber: Unknown Object (MLST).

Applied fix to REL1_5 and HEAD.

  • Bug 2812 has been marked as a duplicate of this bug. ***