From: Scott R. <sr...@ge...> - 2013-01-01 18:12:32
|
Yo. This is what you said earlier: Paul Lesniewski > On Tue, Jan 1, 2013 at 9:24 AM, Scott Ruckh <sr...@ge...> wrote: >> SquirrelMail version: 1.4.23 (SVN 2012-12-21) >> Every plugin installed: (change_sqlpass, delete_move_next, select_range, >> javascript_libs, custom_from, avelsieve) >> PHP version: (php-5.4.10-1) >> Web server Apache (httpd-2.2.3-65), lighttpd (lighttpd-1.4.31-1) >> IMAP server (cyrus-imapd-2.4.16-1) >> SMTP server (postfix-2.9.1-1) >> OS and, if applicable, distribution (CentOS Linux 5.8 x64, kernel >> 2.6.18-308.24.1) >> >> PHP was recently upgraded to PHP 5.4. It appears that the custom_from >> plugin is no longer working correctly with my environment. >> >> I removed the existing custom_from directory from the plugins directory. >> I downloaded custom_from-2.0-1.4.0 from squirrelmail repository. I >> extracted the tarball to plugins directory, copied >> config/config_example.php to config/config.php, and ran the squirrelmail >> configure to ensure the custom_from was selected in the "Installed >> Plugins" section. No changes were made to config.php. > > If you made no changes to the configuration, please try deleting this > file. > >> As I am running >> version 1.4.23, I am under the impression the compatibility plugin is >> not >> necessary. >> >> When clicking on "Compose", the From field is not displayed. The >> expected >> result is that the From field would be displayed. >> >> I tried to enable display_errors in php.ini, but no errors are displayed >> when clicking on the Compose link. >> >> It is assumed the PHP 5.4 upgrade has caused this plugin to stop >> functioning. > > That is doubtful if there are no errors being reported in your logs. > I'd suggest looking in your web server error logs instead of turning > on display_errors. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > Deleting the config.php did not change the results. The following lines are the only thing showing up in the ssl_error_log from the web server: [Tue Jan 01 11:00:09 2013] [error] [client x.x.x.x] File does not exist: /usr/local/squirrelmail/www/favicon.ico [Tue Jan 01 11:00:20 2013] [error] [client x.x.x.x] PHP Strict Standards: Non-static method DO_Sieve::decode_script() should not be called statically in /usr/local/squirrelmail/www/plugins/avelsieve/include/sieve_getrule.inc.php on line 67, referer: https://webmail.gemneye.org/src/webmail.php Possibly unrelated, but the following PHP error is displayed when choosing to "Reply" rather then choosing "Compose" : Strict Standards: Non-static method Message::parseStructure() should not be called statically in /usr/local/squirrelmail/www/functions/mime.php on line 36 Strict Standards: Non-static method Message::parseBodyStructure() should not be called statically in /usr/local/squirrelmail/www/class/mime/Message.class.php on line 296 The "From" field is also not present when choosing to "Reply". Thank you for your response. Scott |