I am now getting a message saying:
"extension missing open ssl"
I have run phpinfo, and openssl is definitely installed.
I have tried all combinations of tls, ssl, starttls, and ports 465 and 587
I get the least number of errors with ssl and 465 and with the following code snipper included (seemed better to put just the one line than attach a page that had my login credentials all over it; am tired and don't want to break anything by editing it out).
I read on a PHPmailer forum that it was advisable to insert the underneath line; and it did seem to reduce errors.
<?php echo (extension_loaded('openssl')?'SSL loaded':'SSL not loaded')."\n"; ?>
I will delete if you advise.
But I believe that that is what tells me that SSL is loaded OK.
Since my php and Apache also seem to have the relevant openssl enabled, I am mystified.
Thank you for your kindness,
I am presently very tired, so it is a job to stay coherent.
I cannot recollect how it happened, but I suddely got refusals to load the Contact Form page I am creating because it was attempting to load:
My security certificate (QuickSSL from Geotrust) is in fact for:
only for "xxxxxxxxxx.com", without that "www.".
Therefore, I tried inserting the following code snipper immediately before calling Universal Email, and to strip out that "www.":
header('HTTP/1.1 301 Moved Permanently');
This garnered a mild success in that the openssl not open error message went away …
the only thing to be seen in the browser window was the line:
Absolutely nothing else was present. At least the openssl not open error had gone.
I therefore tried introducing the following code snipper to reintroduce the "www":
I now again had a visible contact page, … BUT …
that wretched openssl not loaded error was right back up at the top of the browser window again, although the page with contact form was built.
I am now too tired to mess around with further WebAssist code, but feel that I need to find other instances where this stripping trick might work as the page is being treated.
I perhaps should also try a more efficient method of checking on the "www." code?
I found a snipper from a third party that might provide a test, but it is not wise to do anything else right now.
If you could kindly devote some fresh eyes to this, I would be grateful.
To be clear, I sandwishced UE with code that first stripped the www., and then reintroduced it afterwards. That made the openssl not loaded error disappear, but would not load the page except for the error message at the top saying SSL loaded