Share » Forums » Setup & design » Notice: Only variables should be...

Notice: Only variables should be assigned by reference in...

Notice: Only variables should be assigned by reference in...

Tuesday 12 July 2005 4:02:44 pm - 10 replies

Modified on Tuesday 12 July 2005 4:04:17 pm by tommy bergeron

Author Message

Frederik Holljen

Tuesday 12 July 2005 11:24:23 pm

This happens because PHP has been upgraded to PHP 4.4. You will have to upgrade to eZ publish 3.7 in order to use PHP 4.4 (release candidate is in the works)

Thorsten Körner

Friday 15 July 2005 4:41:55 am

Hi,

as a quick solution, you can follow this short workaround-instruction:

create a file 'php_log' in the var subdirectory and give write-permissions to the Webserver-User (wwwrun, nobody or something like that.)

Open index.php in your editor and find a line like:

error_reporting ( E_ALL );

(You never should have this line in a productional environment!!!)
Leave this line as is and put the following three lines after this line:

ini_set('display_errors',0);
 ini_set('log_errors', 1);
 ini_set('error_log', 'var/php_log');


Now all Your notices, warnings and error-messages will apear in php_log instead of beeing displayed on the screen to every_one

Greetings
-thorsten

http://Server4Profis.de CMS, Database and eZ publish Hosting
http://123tk.de Database-, Internet and Intranet Development
eZ publish programing, extensions and modules
SAP, Lotus and IFS integration

Frederik Holljen

Friday 15 July 2005 5:08:04 am

I would strongly advise <b>not</b> to run eZ publish versions before 3.7 on PHP 4.4 in this way. Some functionality will not work as you expect.

Thorsten Körner

Friday 15 July 2005 5:28:26 am

Hi Frederik,

it is just a 'quick and dirty' workaround in the case that only PHP 4.4 is available on the host and there is no Version eZ publish 3.7 for productional use available for download.

On the other hand, I mention that using error_reporting ( E_ALL ) in a way, that displays all errors to <b>every user</b> in a productional environment, is never a good solution. (I would say it is not acceptable).
So one should have a look on this issue, when setting up a new Site and change this settings to either

error_reporting(0)

, or to the code that I have posted above in the other message.

Greetings
-thorsten

P.S. Have You a timeline for 3.7 release?

http://Server4Profis.de CMS, Database and eZ publish Hosting
http://123tk.de Database-, Internet and Intranet Development
eZ publish programing, extensions and modules
SAP, Lotus and IFS integration

tommy bergeron

Friday 15 July 2005 3:20:06 pm

Thanks a lot!!! :D

Frederik Holljen

Saturday 16 July 2005 1:59:07 am

Thorsten,

We'll release a release candidate of 3.7 next week. The final release will follow about a week later.

Thorsten Körner

Saturday 16 July 2005 2:21:17 am

Hi Frederik,

that's good news on this issue.
Is the 3.7 in svn/stable ready? I mean fixes stable that problem already?

I'm thinking about editing my Makefiles to use svn/stable as download source for automatic updates for my hosted customers at http://server4profis.de . By now I've at any update edited the Makefile by hand to adopt the new release. But I only can do this, when the sources in /stable are __really__ stable and will not be changed until release.

Greetings
-thorsten

http://Server4Profis.de CMS, Database and eZ publish Hosting
http://123tk.de Database-, Internet and Intranet Development
eZ publish programing, extensions and modules
SAP, Lotus and IFS integration

Frederik Holljen

Saturday 16 July 2005 3:07:16 am

We have forked stable/3.7 there are no known major problems and it works with PHP 4.4. I can't promise you that we will not change anything before the release though (this is why we don't release it now right :)

Siniša Šehović

Monday 18 July 2005 4:10:05 am

Hi Frederik,

I don't know if I am mad or what but svn version 3.7 is not working for me!?!???

I'm getting

PHP Fatal error: Maximum execution time of 220 seconds exceeded in ../lib/ezxml/classes/ezxml.php on line 355

Server is slackware 10.1 with php 4.4.0 and apache 1.3.33.

I'm really confused ...

What to do?

Best regards,
Sinisa

P.S. eZp 3.6.0 with php 4.3 works nice on same server!
P.P.S Looks like that pubsvn.ez.no is not updated with svn.ez.no revision

---
If at first you don't succeed, look in the trash for the instructions.

Marko Žmak

Friday 22 July 2005 11:47:49 am

Hi, I have the same problem but this quick fix that Thorsten gave doesn't work for me.

I still get the same warnings, and the eZ admin interface doesn't function properly. For example when I choose "Discard Draft" I get an eZ error and nothing happens.

I also get this error:

Cannot open log file 'var/log/warning.log' for writing
The web server must be allowed to modify the file.
File logging for 'var/log/warning.log' is disabled.

Also the same error for "error.log".
I have checked, and double checked that files have the apropriate permissions, I even gave 777 permissions to the directories, but it's always the same.

Right now I don't have the time to upgrade eZ to 3.7 and test it, so I would really need a quick fix that works. Anyone?

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu