perituswebdesign

I do have the same issues as described by @nevma. Even worse: It loads a lot of js-files too.

These are all not needed when loading the frontend.

Thanks,
David

Hi there,

Thanks so much for the quick response.

And one thing I forgot: I really do love WP Speed of Light! I use it on nearly every on of the sites I manage!

The most important thing here is, that I can’t activate the cache because of the failed file_exists and is_writeable-tests, even if define('WP_CACHE', true); is already in my wp-config.php.

Thanks,
David

By the way… wp-config.php shouldn’t be writeable at all, so why don’t you just tell the user to add define('WP_CACHE', true); by themselves if wp-config is not writeable?

In my case the problem were some left-over WP-Super-Cache .htaccess-Rules. When I removed those everything started to work again.

+1 I’m having the exact same issue.

@gdebrion Your solution worked very well, but it’s not a long-time solution, it’s a hack.

Is there an official solution?

Was resolved with Version 1.0.3.

Thanks a lot!

I think your problem lies here:

In eemail.php:26-29 you expect the return of eemail::send to be a boolean true, while in reality it is the json-body of the response.

26:$rs = eemail::send($to, $subject, $message, $headers, $attachments);
27:  if ($rs !== true) {
28:    return eemail::wp_mail_native($to, $subject, $message, $headers, $attachments, $rs);
29:  }

In ElasticEmailClient.php:70 you simple return the response-body (which is json):

70:  return $response['body'];

The interesting thing is, that in ElasticEmailClient.php:68 you json_decode the response-body, but never use it. So I think you need to fix either ElasticEmailClient.php:70 to look like that:

70:  return isset($jsonresponse['success']) ? $jsonresponse['success'] : false;

or in eemail.php eemail::send to json-decode the body and return the success flag as boolean.

I really hope this will be fixed very soon as I just gave you a solution.

Thanks in advance.

David

Here’s the error-message I get:

2017/12/06 07:46:15 [error] 49#49: *45 FastCGI sent in stderr: “PHP message: eemail::wp_mail_native: [email protected] (The Subject) Error: {“success”:true,”data”:{“transactionid”:”050d9112-418f-c1a3-e061-87830e66ba62″,”messageid”:”73NrEPYQNa1kECkkI5zwbQ2″}}” while reading response header from upstream, client: *.*.*.*, server: , request: “POST /path/to/php.php HTTP/1.1”, upstream: “fastcgi://unix:/run/php-fpm.sock:”, host: “my.host”, referrer: “https://my.host/referrer”