Simon

One of my clients that use auto generated coupons has the same issue. The fix mentioned above worked.

Thank you so much.

What was the fix? I have the same issue.

I solved this by completing the update process (which I didn’t know was pending).

I experience the same issue. Using the Divi theme.

I experience the same issue. Alt-tags are not added to the images on the product pages.

I am not able to activate debug mode for Minify. I cannot check the checkbox.

I have the same issue. Divi’s support team says that when minify is activated in W3 Total Cache, then it breaks some functionality in the Divi Builder.

Here is what their support wrote me:
I have gone through and saw that the issue is due to plugin conflict W3 Total Cache when minify setting is enable. I would recommend contacting the plugin’s author/developer to let them know that when Minify Setting is enabled, it breaks your builder layout. They should be able to provide an insights for it as to why it is occurring. Feel free to contact them first and let me know what they said so I have a better idea and can look more closely to it.

I have disabled the minify setting temporarily.

Chouby: I’ve already done that several times. The debug log shows nothing relevant when the white screen error emerges. There are no clues to this issue to be found there.

The only clue that let me to think of Polylang, was that when the white screen error happened, the URL showed the english version (/en/) instead of the danish version (/da/) which is the standard one. So it seems like, when this happens, that Polylang tries to redirect to the english version but without success, resulting in the white screen. But why it tries to do that, I do not know.

So here is what I just did.
First I reactivated Polylang (along with all the other plugins) = the white screen error emerged.
Then I deactivated all other plugins and only kept Polylang active = No visible error.
Then I activated each other plugin one by one and checked = No visible error.

I also turned on the debugging log. Nothing to mention there..

So right now there is no issue, but it won’t be long until it happens again as it has on/off for a very long time. I’m not sure how to proceed with this.

Hannah’s reply answered my question. Thank you!

Thank you for your reply.
I tried changing the configuration according to the Google Suite guidelines but nothing worked. I also checked that ‘Allow less secure apps’ was turned on (it was).

I then tried using the Gmail configuration with the API solution instead and now it gives this error instead:

Versions:
WordPress: 4.9.1
WordPress MS: No
PHP: 5.6.11
WP Mail SMTP: 1.2.2

Params:
Mailer: gmail
Constants: No
Client ID/Secret: Yes
Auth Code: Yes
Access Token: No

Server:
OpenSSL: Yes
PHP.allow_url_fopen: Yes
PHP.stream_socket_client(): Yes
PHP.fsockopen(): Yes
PHP.curl_version(): Yes
Apache.mod_security: No

Debug:
cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Error while sending via Gmail mailer: cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

I’m experiencing my forms using the same ID for all entries. It didn’t always work like that and I really need it to define a unique ID for each entry.

Can someone tell me if it’s safe to manually use the truncate function in wp_wfconfig? We have the same problem as mentioned in this thread, but in our case the database user didn’t have the correct privileges. We fixed that, but the table is still filled up to the extend where our websites crashes. I would like to know if it’s safe to manually truncate wp_wfconfig.

Thanks. That is sufficient.