Strict messages are less severe than notices, which are already being ignored, so this really isn't a problem. Probably all that has happened is that PHP have introduced some strict messages to alert coders that they are using features that are discouraged or may one day be removed from PHP. Over time, apps will be updated, but in the meantime, it's certainly no concern that the messages are triggered; they are very minor.
Ben. On 31/01/12 7:18 AM, James Devine wrote: > That works but I had to modify program/include/iniset.php in order to do that > because it was setting it to E_ALL&~E_NOTICE, that seems like sweeping a > problem > under the carpet though > > On Mon, Jan 30, 2012 at 11:50 AM, Luigi Rosa <[email protected] > <mailto:[email protected]>> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > James Devine said the following on 30/01/12 19:02: > > Am I doing something wrong to be seeing all these errors? > > > > [30-Jan-2012 18:00:34 UTC] PHP Strict Standards: Only variables > should be > > assigned by reference in > > > > /var/www/roundcube_local/roundcubemail-0.7.1/program/lib/MDB2/Driver/Datatype/Common.php > > > > > on line 1221 > > > Disable E_STRICT error logging in php.ini > > > > Ciao, > luigi > > - -- > / > +--[Luigi Rosa]-- > \ > > Sinclair: Good morning, Lieutenant Commander. Sleep well? > Ivanova: Sleeping is not the problem. Waking up, that is a problem. > I've always had a hard time getting up when it's dark outside. > Sinclair: But in space it's always dark. > Ivanova: I know. I know. > --"Signs and Portents" > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk8m5nIACgkQ3kWu7Tfl6ZSNvgCfbTz+uGVawKwmH1hhcuHg7bCG > aeUAnjP6ODmWQx8hjXRT1tLuod883paf > =LI5S > -----END PGP SIGNATURE----- > -- > List info: http://lists.roundcube.net/users/ > BT/041e0616 > > > > -- List info: http://lists.roundcube.net/users/ BT/8f4f07cd
