-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Matt Ruzicka, On Thursday, August 25, 2005, you wrote:
> (Not sure if this should go to squirrelmail-devel, but I thought I > would start here.) > I was wondering if there was any word on when SM 1.4.6 would be > released in stable form. Soon. I'll work on getting it out after my vacation. I'll be back next weekend. > We recently needed to upgrade to PHP 4.4 and then ran into the > "Fatal error: Call to a member function on a non-object in > src/read_body.php on line 423" error discussed here: > http://article.gmane.org/gmane.mail.squirrelmail.user/25363 > We went ahead and upgrade our SM installation to the 1.4.6 snapshot > from 20050812 (though we would MUCH prefer to be on a stable source) > and that error was fixed. The changes between the release, and the current snapshots is actually not that huge. > However, our users were now (still?) getting page cannot be > displayed errors, at seemingly random intervals, when clicking send > after new compositions, replies and forwards. Since 20050823 came > out in the meantime, and there were some changes in the src between > the two, we then upgraded to 20050823. > Our users are still getting the page cannot be displayed error and > after turning on PHP debugging we've been seeing the Following errors > in the logs, that appear to coincide with the errors our users are > seeing. > "PHP Fatal error: Call to undefined function: error_message() in > squirrelmail.stable-20050823/functions/imap_messages.php on line 808" Hrm, interesting. Well, I'd have thought it would have been included by the calling page, however the function is actually called from multiple places so could in fact be the result of another location not having the include. The better solution would be to include the file to ensure it is in fact there. > In short: > 1. Is the lack of the require statement for display_messages.php in > functions/imap.php a bug which needs to be fixed in the current > snapshot code? Yes, I'd consider so, though I'm curious as to what the calling page is so we can find out why that might not have it included. > 2. Is there any chance that 1.4.6 and what appear to be it's > necessary PHP 4.4.0 fixes going to be coming to stable any time soon > so that I can factor out bleeding edge code bugginess and sit down > to track potential bugs in the current stable code? I'd not worry too much about "bleeding edge code" in the stable branch. We don't make major changes there, and any features that do get into that branch are usually trivial. I count maybe 53 commit emails since the release, take off a handful for trivial things like ChangeLogs, and locale changes, and I guess maybe 30 commits are code changes, I'm guessing they're all bug changes except the addition of a handful of themes right after the release. - -- Jonathan Angliss <[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFDDpvdK4PoFPj9H3MRAo1jAJ95TNDm3dG6iUZkd5wr4qEmZ2BGLACgmxoI ASGphnaHeaV/pl8INb0kM9A= =NIW5 -----END PGP SIGNATURE----- ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- squirrelmail-users mailing list Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
