meuro

no sorry, the issue is NOT RESOLVED, you say explicitly here that your plugin is compatible with Gutemberg and wordpress 5, but it’s not!
Even you suggested to switch back to the old editor!

so i am still waiting an answer for this issue, thanks

Hello @alexgff, thanks for the reply,
i know classic editor is working since we did some testing and we are currently using the method you mentioned to publish our posts.
I just wanted to check if the block editor issue we are having is something related to our configuration -maybe some setting we missed- or it’s a global issue you were already aware of.

As for my testing, it seems that if you write and publish the original post using classic editor and then reopen the post with the new block editor you can translate the post without overwriting the original. Hope it helps.

thanks,
Mauro

Thanks @alin Marcu for the interest. yes now i realize we were using a different version of encryption, not entirely disabling it!
it sure is (or was, as now i have just re-edited the file and reverted to the original value and it’s working) an issue with the server configuration on our side. It was too strange that we happened to have the same error *and* the same provider!

however, thanks to @carapaucostante ??
..and Alin, keep up with the good work you are doing here!

yes of course is not the optimal solution because you opt out from the extra security layer given by the data encryption.
but if you think… 2 days ago it was working then it stopped for us… so i’m assuming the ‘SSL thing’ has been introduced with the last update and before we all used non-encrypted data transfer. But, again, it’s my assumption.

This is just a patch (or a ‘dirty hack’) to make it work again *temporarily*, so if you feel insecure/vulnerable you may want to revert to the original code.

oh ok i think i ‘ve found a workaraound by looking at the error log posted by CarapauCostante
it says exception 'Google_IO_Exception' with message 'SSL connect error' in /web/htdocs/www.carapaucostante.it/home/ccwp/wp-content/plugins/google-analytics-dashboard-for-wp/tools/src/Google/IO/Curl.php:86

so if you open up that file you’ll see some lines before (exactly @ line #59-60):

// 1 is CURL_SSLVERSION_TLSv1, which is not always defined in PHP.
        curl_setopt($curl, CURLOPT_SSLVERSION, 1);

you have to disable SSL by setting this param to 0 (ZERO)

// 1 is CURL_SSLVERSION_TLSv1, which is not always defined in PHP.
        curl_setopt($curl, CURLOPT_SSLVERSION, 0);

keep in mind that this is a temporary workaround and the next plugin update will reset this setting to it’s initial value

maybe we can ask the Dev to insert a checkbox in the settings to disable/enable SSL?

same error, same provider…