Hi, after I enable Synchronization module under "Multilanguage - i18n - experimental" , I got this warning message on each page:
Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name](). 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. in /home/public_html/dlasi/sites/all/modules/i18n/experimental/i18nsync.module on line 142
Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name](). 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. in /home/public_html/dlasi/sites/all/modules/i18n/experimental/i18nsync.module on line 142
When Synchronization module is disabled, warning message disappears. Also If I comment line 142 in i18nsync.module problem is gone.
My site's parameters:
Drupal 5.3
Configuration file Protected
Cron maintenance tasks Last run 2 days 13 hours ago
Database schema Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
MySQL database 4.1.22
PHP 5.2.4
Unicode library PHP Mbstring Extension
Web server Apache
Comments
Comment #1
itsnotme commentedI have the same problem, on a Drupal 5.3 / Mysql5.0 /Php 5.2.2 system. On my local computer, all is fine.
Comment #2
jose reyero commentedComment #3
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #4
ekrispin commentedI still have this problem and at the same line and it is after installing the most updated version to date (that according to the above was supposed to have the problem fixed).
In localhost on XAMPP or/and PHP version 4.4.7 there is no prob. The problem occurs in hosting with PHP version 5.2.2
Comment #5
Oghnia commentedI have the same problem
Comment #6
jose reyero commentedI may be missing something but,
Are you sure you are using the latest (-dev) version? There's a new stable version now though (2.3).
When a bug for 5.x-2.2 is fixed it doesn't mean it's fixed in that version, which is not suppossed to change at all, but in the dev version and the next stable one.
?
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.