Quantcast

Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Kevin Buckley
OS              NetBSD 7.0_STABLE
Software Stack  PkgSrc
SquirrelMail    1.4.23pre14605
Apache 2        Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/1.0.1u DAV/2
PHP/7.0.13
PHP             7.0.135.6.28-1


Before I start, a bit of info on the SquirrelMail version, because I
was told that we are reasonably up-to-date, in that the PkgSrc commit
says:

----------------------------
revision 1.131
date: 2016-11-18 04:10:07 +1300;  author: taca;  state: Exp;  lines: +2
-3;  commitid: TckPzUpbAFssFuuz;
Update squirrelmail to 1.4.23pre14605, latest snapshot.
PHP 7.0 support should be improved, too.

   - Added new "smtp_helo_override" hook; allows plugins to override
     the HELO host sent to the SMTP server when sending messages
   - Added STARTTLS support for both IMAP and SMTP connections
   - Added PDO support for database connections, so no external
     database module needs to be installed
----------------------------

furthermore, I also note that this issue echoes that described in
this (Dec 2016) devel list posting

    - https://sourceforge.net/p/squirrelmail/mailman/message/35527151/

except that ours

1) is only using a secure (https) connection
2) exhibits the "blank page" but DOESN'T send a message.
3) is using PHP7, not the PHP5.

but here we go with the actual issue.

Our School's webservers updated to PHP7 over the weekend and one of the
issues in the wake of that has been that SquirrelMail works to a degree
(we're a Uni, but no pun intended) but no longer seems to be able to
send out mail, either when doing a "Compose" or a reply to.

The webserver logs tell us that, following a click on the "Send" button
we're falling foul of these four routines

squirrelmail/class/html.class.php
squirrelmail/class/mime/Disposition.class.php
squirrelmail/class/mime/Language.class.php
squirrelmail/class/mime/ContentType.class.php

which give error (not warning) messages akin to

PHP Deprecated:  Methods with the same name as their class will not be
  constructors in a future version of PHP;

although that might not be the whole story as some parts of SquirrelMail
clearly still work.

I tried adding in "proper" __constructor functions, in the manner of the
fix described here

    - https://cweiske.de/tagebuch/php4-constructors-php7.htm

to those four files, however that just moves the same issue down into
(or possibly across) the SquirrelMail stack, and we see some other
webserver error logs, three indicating similar "deprecated constructor"
stuff from different fucntions:

squirrelmail/functions/addressbook.php
squirrelmail/functions/abook_local_file.php
squirrelmail/functions/abook_ldap_server.php

however, two more exhibit different errors

PHP Deprecated:  Non-static method Message::parseStructure() should not
be called statically in

squirrelmail/functions/mime.php  on line 36,
squirrelmail/class/mime/Message.class.php on line 296,

both with the same referrer

referer:
https://our.host/squirrelmail/src/right_main.php?PG_SHOWALL=0&sort=0&startMessage=1&mailbox=INBOX


Reading around the interweb thing, especially this posting in the
squirrelmail-devel list

    - https://sourceforge.net/p/squirrelmail/mailman/message/35457393/

suggests that there's a snapshot version out there in which all this may
have been
fixed ?

What I'd like to know is whether there is an identifiable set of patches
that I could use, so to to patch the PkgSrc version of SquirrelMail, rather
than go straight to a /newer/the most recent/ snapshot version that will
have extra (or even reduced) functionality, which the PkgSrc folk clearly
decided wasn't the way forwards for them.

I suppose what I am asking is, did you do the PHP7 updates in an SVN branch
that I could take the top off, rather than taking the most recent branch and
extracting out only the "solution" to the "deprecated" errors ?

I also suppose that the errors we're seeing could be something else
altogether!

Either way, and it pretty much covers most "ways", any insight would be
useful,

Kevin Buckley
eScience Consultant
School of Engineering and Computer Science
Victoria University of Wellington
New Zealand

------------------------------------------------------------------------------
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Kevin Buckley
On 05/12/16 15:10, Kevin Buckley wrote:
> OS              NetBSD 7.0_STABLE
> Software Stack  PkgSrc
> SquirrelMail    1.4.23pre14605
> Apache 2        Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/1.0.1u DAV/2
> PHP/7.0.13
> PHP             7.0.135.6.28-1


> I tried adding in "proper" __constructor functions, in the manner of the
> fix described here
>
>     - https://cweiske.de/tagebuch/php4-constructors-php7.htm
>
> to those four files, however that just moves the same issue down into
> (or possibly across) the SquirrelMail stack, and we see some other
> webserver error logs, three indicating similar "deprecated constructor"
> stuff from different fucntions:
>
> squirrelmail/functions/addressbook.php
> squirrelmail/functions/abook_local_file.php
> squirrelmail/functions/abook_ldap_server.php
>
> however, two more exhibit different errors
>
> PHP Deprecated:  Non-static method Message::parseStructure() should not
> be called statically in
>
> squirrelmail/functions/mime.php  on line 36,
> squirrelmail/class/mime/Message.class.php on line 296,
>
> both with the same referrer
>
> referer:
> https://our.host/squirrelmail/src/right_main.php?PG_SHOWALL=0&sort=0&startMessage=1&mailbox=INBOX

A closer look at the logs (you'll appreciate that we have a lot of lines
in the logs after the update) suggests that the two

PHP Deprecated:  Non-static method Message::parseStructure() should not
not be called statically in

messages actually occured along with the

class/html.class.php
class/mimeContentType.class.php
class/mimeDisposition.class.php
class/mimeLanguage.class.php

not _after_ I'd tried the "adding an __constructor()" fix, so it's
possible that what we're seeing isn't purely "PHP Deprecated" related.

I'll try and feed back, as I m able to determine more.


------------------------------------------------------------------------------
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Kevin Buckley
On 05/12/16 16:27, Kevin Buckley wrote:

> OS              NetBSD 7.0_STABLE
> Software Stack  PkgSrc
> SquirrelMail    1.4.23pre14605
> Apache 2        Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/1.0.1u DAV/2
> PHP/7.0.13
> PHP             7.0.135.6.28-1
>
> ...
 >
> try and feed back, as I m able to determine more.

I put the original coee back as it was, as it appears we've been
getting away with filling up the log files for a while now and so
perhaps the "Deprecated ..." isn't the issue.

We've now found another line in the logs that's clearly "fatal",
to whit:


PHP Fatal error:  Redefinition of parameter $ignore in
/usr/pkg/share/squirrelmail/class/deliver/Deliver_SendMail.class.php on
line 92, referer:
https://our.box/squirrelmail//src/compose.php?mailbox=INBOX&startMessage=1

Yet to investigate that as need to go home.

------------------------------------------------------------------------------
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Kevin Buckley
On Mon, December 5, 2016 17:57, Kevin Buckley wrote:

> I put the original coee back as it was, as it appears we've been
> getting away with filling up the log files for a while now and so
> perhaps the "Deprecated ..." isn't the issue.
>
> We've now found another line in the logs that's clearly "fatal",
> to whit:
>
>
> PHP Fatal error:  Redefinition of parameter $ignore in
> /usr/pkg/share/squirrelmail/class/deliver/Deliver_SendMail.class.php on
> line 92, referer:
> https://our.box/squirrelmail//src/compose.php?mailbox=INBOX&startMessage=1
>
> Yet to investigate that as need to go home.

This is an absolutely marvellous issue !

Here's that function

    function initStream($message, $sendmail_path, $ignore=0, $ignore='',
$ignore='', $ignore='', $ignore='', $ignore=false, $ignore='',
$ignore=array()) {
        $rfc822_header = $message->rfc822_header;
        $from = $rfc822_header->from[0];
        $envelopefrom = trim($from->mailbox.'@'.$from->host);
        $envelopefrom =
str_replace(array("\0","\n"),array('',''),$envelopefrom);
        // save executed command for future reference
        $this->sendmail_command = "$sendmail_path $this->sendmail_args
-f$envelopefrom";
        // open process handle for writing
        $stream = popen(escapeshellcmd($this->sendmail_command), "w");
        return $stream;
    }

Note that not only $ignore used SEVEN times in the function signature,
but is set to two different things in there "0" and false, and the
values really are "ignored" within the function.

Renaming the multiplicity of $ignore-s to be $ignore1, $ignore2,
and so on, sees the ability to send mail return, to our installtion
anyway.

This is currently the only "fix" I have applied to our installtion,
so if there are any thoughts on my attempts to remove all of that
"Deprecated" crud by adding in a __constructor method (or whether
this /has been/is being/ done in some branch of the codebase), they'd
be appreciated.

Kevin

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Kevin Buckley

Thought I might as well feedback what I have found so far,in respect
of getting rid of the "Deprecated" messages that comw about simply
because the various classes don;t have an __construct() method.

Clearly the developere will be aware of this info, but the info might
be useful to anyone else, who follows this thread, and who might want
to try and get rid of those messages, whilst the official changes get
added into the codebase.

These files appear to be the ones that supply a class


squirrelmail/class/html.class.php:class html {

squirrelmail/class/deliver/Deliver.class.php:class Deliver {
squirrelmail/class/deliver/Deliver_IMAP.class.php:class Deliver_IMAP
extends Deliver {
squirrelmail/class/deliver/Deliver_SMTP.class.php:class Deliver_SMTP
extends Deliver {
squirrelmail/class/deliver/Deliver_SendMail.class.php:class
Deliver_SendMail extends Deliver {

squirrelmail/class/helper/VCard.class.php:class VCard {

squirrelmail/class/mime/AddressStructure.class.php:class AddressStructure {
squirrelmail/class/mime/ContentType.class.php:class ContentType {
squirrelmail/class/mime/Disposition.class.php:class Disposition {
squirrelmail/class/mime/Language.class.php:class Language {
squirrelmail/class/mime/Message.class.php:class Message {
squirrelmail/class/mime/MessageHeader.class.php:class MessageHeader {
squirrelmail/class/mime/Rfc822Header.class.php:class Rfc822Header {
squirrelmail/class/mime/SMimeMessage.class.php:class SMimeMessage {

squirrelmail/functions/abook_database.php:class abook_database extends
addressbook_backend {
squirrelmail/functions/abook_ldap_server.php:class abook_ldap_server
extends addressbook_backend {
squirrelmail/functions/abook_local_file.php:class abook_local_file extends
addressbook_backend {
squirrelmail/functions/addressbook.php:class AddressBook {
squirrelmail/functions/addressbook.php:class addressbook_backend {
squirrelmail/functions/db_prefs.php:class dbPrefs {
squirrelmail/functions/options.php:class SquirrelOption {

Of those,

these don't even have a constructor named as the Classname, which is the
deprecated
functionality causing the messages.

VCard
AddressStructure
Message
MessageHeader
Rfc822Header
SMimeMessage

For all of the others, a patch, akin to that described in the URL
referenced in my
opening email, that provides an __construct() matching the function
signature of the
original "class name Constructor", and then simply using that original
funtion to
pass through the parameters to the new  __construct() function, seems to
apply
cleanly to the codebase, without so far, affecting functionality.

I'm not sure if attaching such a patch-diff here is the right thing to do ?


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Kevin Buckley

Now to return to the two "new" Deprecated mesages that fixing the
exiting ones produced, namely

Non-static method X should not be called statically

which occured at

/usr/pkg/share/squirrelmail/functions/mime.php on line 36

and

/usr/pkg/share/squirrelmail/class/mime/Message.class.php on line 296


These two lines are, respectively

$msg = Message::parseStructure($read,$i);

and

$msg = Message::parseBodyStructure($read, $i, $sub_msg);


Replacing those two lines with, what this posting

http://stackoverflow.com/questions/4684454/error-message-strict-standards-non-static-method-should-not-be-called-staticall

suggests is "valid PHP from 5 to 7", so


$msg = (new Message())->parseStructure($read,$i);

 and

$msg = (new Message())->parseBodyStructure($read, $i, $sub_msg);


does appear to get rid of the "Deprecated" messages that were
being seen, whisly not affecting the functionality of our
SquirrelMail installation.

Hoping again, that that's useful.


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

oonet
In reply to this post by Kevin Buckley
Thanks for sending this. It looks like your problem is with php7. One of many problems with php7, in fact, which is why we returned to php5. I hope your feedback helps squirrelmail get working with php7!

I wonder if you continue to see your problem with http as well as https? (We also only use https, but it was helpful to confirm that http works correctly.)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Paul Lesniewski
In reply to this post by Kevin Buckley


On 2016年12月05日 14:05, [hidden email] wrote:

> On Mon, December 5, 2016 17:57, Kevin Buckley wrote:
>
>> I put the original coee back as it was, as it appears we've been
>> getting away with filling up the log files for a while now and so
>> perhaps the "Deprecated ..." isn't the issue.
>>
>> We've now found another line in the logs that's clearly "fatal",
>> to whit:
>>
>>
>> PHP Fatal error:  Redefinition of parameter $ignore in
>> /usr/pkg/share/squirrelmail/class/deliver/Deliver_SendMail.class.php on
>> line 92, referer:
>> https://our.box/squirrelmail//src/compose.php?mailbox=INBOX&startMessage=1
>>
>> Yet to investigate that as need to go home.
>
> This is an absolutely marvellous issue !
>
> Here's that function
>
>     function initStream($message, $sendmail_path, $ignore=0, $ignore='',
> $ignore='', $ignore='', $ignore='', $ignore=false, $ignore='',
> $ignore=array()) {
>         $rfc822_header = $message->rfc822_header;
>         $from = $rfc822_header->from[0];
>         $envelopefrom = trim($from->mailbox.'@'.$from->host);
>         $envelopefrom =
> str_replace(array("\0","\n"),array('',''),$envelopefrom);
>         // save executed command for future reference
>         $this->sendmail_command = "$sendmail_path $this->sendmail_args
> -f$envelopefrom";
>         // open process handle for writing
>         $stream = popen(escapeshellcmd($this->sendmail_command), "w");
>         return $stream;
>     }
>
> Note that not only $ignore used SEVEN times in the function signature,
> but is set to two different things in there "0" and false, and the
> values really are "ignored" within the function.

It's used eight times. It's explained in the function comments, so
please look there if you're curious.

This was an untested code path (most people seem to use SMTP), so thank
you for reporting this - it is now fixed.

> Renaming the multiplicity of $ignore-s to be $ignore1, $ignore2,
> and so on, sees the ability to send mail return, to our installtion
> anyway.
>
> This is currently the only "fix" I have applied to our installtion,
> so if there are any thoughts on my attempts to remove all of that
> "Deprecated" crud by adding in a __constructor method (or whether
> this /has been/is being/ done in some branch of the codebase), they'd
> be appreciated.

Deprecated notices are just that, and they do not impact using an
application one way or the other. You may want to turn off E_DEPRECATED
notices in your logs if they are creating too much noise.

Those things are on my list, but I haven't had time to get to them. If
you are interested in submitting patches for any issues you find, yes,
you're always invited to send unified diff (diff -u) files to this list.
We're always grateful for your contributions.

Cheers,
Paul

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Paul Lesniewski
In reply to this post by Kevin Buckley


On 2016年12月05日 19:31, [hidden email] wrote:

>
> Now to return to the two "new" Deprecated mesages that fixing the
> exiting ones produced, namely
>
> Non-static method X should not be called statically
>
> which occured at
>
> /usr/pkg/share/squirrelmail/functions/mime.php on line 36
>
> and
>
> /usr/pkg/share/squirrelmail/class/mime/Message.class.php on line 296
>
>
> These two lines are, respectively
>
> $msg = Message::parseStructure($read,$i);
>
> and
>
> $msg = Message::parseBodyStructure($read, $i, $sub_msg);
>
>
> Replacing those two lines with, what this posting
>
> http://stackoverflow.com/questions/4684454/error-message-strict-standards-non-static-method-should-not-be-called-staticall
>
> suggests is "valid PHP from 5 to 7", so
>
>
> $msg = (new Message())->parseStructure($read,$i);
>
>  and
>
> $msg = (new Message())->parseBodyStructure($read, $i, $sub_msg);

That's a band-aid solution that will work in cases where you're not
familiar with or in control of the called code.  The best thing to do is
inspect the called source... ideally, you'd never want to be calling
static functions in the first place, but in this case, the solution is
to label the called functions as static, which I have done.

Thanks for your reports.

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Paul Lesniewski
In reply to this post by oonet


On 2016年12月05日 23:14, oonet wrote:
> Thanks for sending this. It looks like your problem is with php7. One of many
> problems with php7, in fact, which is why we returned to php5. I hope your
> feedback helps squirrelmail get working with php7!

SquirrelMail works with PHP7 and you should not make claims to the
contrary unless you can show something concrete. Your issue is likely a
configuration/setup issue in your web server, but you provided no
helpful information whatsoever (please read the mailing list posting
guidelines next time).

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Rolan Yang
In reply to this post by Kevin Buckley
Did you examine what's being loaded or not loaded by the browser from within the developer console?
(CTRL-SHIFT-j in Chrome)  Load the page once with http and a second time https and compare the two under the Network pane.
 
Could be a web server config issue.

~Rolan

On Mon, Dec 5, 2016 at 10:10 PM, <[hidden email]> wrote:

Thought I might as well feedback what I have found so far,in respect
of getting rid of the "Deprecated" messages that comw about simply
because the various classes don;t have an __construct() method.

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Paul Lesniewski
In reply to this post by Kevin Buckley


On 2016年12月05日 19:10, [hidden email] wrote:

>
> Thought I might as well feedback what I have found so far,in respect
> of getting rid of the "Deprecated" messages that comw about simply
> because the various classes don;t have an __construct() method.
>
> Clearly the developere will be aware of this info, but the info might
> be useful to anyone else, who follows this thread, and who might want
> to try and get rid of those messages, whilst the official changes get
> added into the codebase.
>
> These files appear to be the ones that supply a class
>
>
> squirrelmail/class/html.class.php:class html {
>
> squirrelmail/class/deliver/Deliver.class.php:class Deliver {
> squirrelmail/class/deliver/Deliver_IMAP.class.php:class Deliver_IMAP
> extends Deliver {
> squirrelmail/class/deliver/Deliver_SMTP.class.php:class Deliver_SMTP
> extends Deliver {
> squirrelmail/class/deliver/Deliver_SendMail.class.php:class
> Deliver_SendMail extends Deliver {
>
> squirrelmail/class/helper/VCard.class.php:class VCard {
>
> squirrelmail/class/mime/AddressStructure.class.php:class AddressStructure {
> squirrelmail/class/mime/ContentType.class.php:class ContentType {
> squirrelmail/class/mime/Disposition.class.php:class Disposition {
> squirrelmail/class/mime/Language.class.php:class Language {
> squirrelmail/class/mime/Message.class.php:class Message {
> squirrelmail/class/mime/MessageHeader.class.php:class MessageHeader {
> squirrelmail/class/mime/Rfc822Header.class.php:class Rfc822Header {
> squirrelmail/class/mime/SMimeMessage.class.php:class SMimeMessage {
>
> squirrelmail/functions/abook_database.php:class abook_database extends
> addressbook_backend {
> squirrelmail/functions/abook_ldap_server.php:class abook_ldap_server
> extends addressbook_backend {
> squirrelmail/functions/abook_local_file.php:class abook_local_file extends
> addressbook_backend {
> squirrelmail/functions/addressbook.php:class AddressBook {
> squirrelmail/functions/addressbook.php:class addressbook_backend {
> squirrelmail/functions/db_prefs.php:class dbPrefs {
> squirrelmail/functions/options.php:class SquirrelOption {

FYI, I handled most all of this. Might have missed some, but got the
most frequent offenders.

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

chandrakant
In reply to this post by Kevin Buckley
I am also facing similar problem with squirrelmail version 1.4.22,  PHP version 5.4.16, httpd version Apache/2.4.6 (CentOS), CentOS Linux release 7.2.1511 (Core)

For some messages after clicking on forward button while composing mail entire msg becomes blank. What could be the solution?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Squirrelmail returns blank page after send (PHP 7: Warning: contains logs )

Paul Lesniewski
On 12/18/16, chandrakant <[hidden email]> wrote:
> I am also facing similar problem with squirrelmail version 1.4.22,  PHP
> version 5.4.16, httpd version Apache/2.4.6 (CentOS), CentOS Linux release
> 7.2.1511 (Core)
>
> For some messages after clicking on forward button while composing mail
> entire msg becomes blank. What could be the solution?

Upgrade.

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
Loading...