Otto Kek?l?inen

I fixed this now with a mu-plugin:

commit 4b6579336ab7e966c2fd5cc4c52c2fa0d3de737e (HEAD -> master)
Author: Seravo Admin <[email protected]>
Date:   Thu Oct 29 12:40:02 2020 +0200

    Always use "Remember me" to circumvent bug in plugin Samesite
    
    https://www.ads-software.com/support/topic/cant-log-in-after-installing-your-plugin/#post-13559023

diff --git a/htdocs/wp-content/mu-plugins/always-remember-login.php b/htdocs/wp-content/mu-plugins/always-remember-login.php
new file mode 100644
index 0000000..0c200d0
--- /dev/null
+++ b/htdocs/wp-content/mu-plugins/always-remember-login.php
@@ -0,0 +1,9 @@
+<?php
+function login_checked_remember_me() {
+  add_filter( 'login_footer', 'rememberme_checked' );
+}
+
+add_action( 'login_enqueue_scripts', 'login_checked_remember_me', 100 );
+function rememberme_checked() {
+  echo "<script>document.getElementById('rememberme').checked = true;</script>";
+}

When I log in and it fails:

set-cookie: wordpress_test_cookie=WP+Cookie+check; path=/; secure
set-cookie: wordpress_sec_dcfecb4f7f4693ded9f0540a1d77266b=seravo%7C1603390318%7CWwBZ0e1TqBKjL6xX8qH0ZHW9sru0e0TNsgDnSgMHfGU%7C13e42107dd0073bf6a0b648f38ae4af81830b30c50f0d0a9e90a26b1333bd5df;expires=Thu, 01-Jan-1970 00:00:00 GMT;Max-Age=0;path=%2Fwp-content%2Fplugins;domain=;secure;httponly;SameSite=None
set-cookie: wordpress_sec_dcfecb4f7f4693ded9f0540a1d77266b=seravo%7C1603390318%7CWwBZ0e1TqBKjL6xX8qH0ZHW9sru0e0TNsgDnSgMHfGU%7C13e42107dd0073bf6a0b648f38ae4af81830b30c50f0d0a9e90a26b1333bd5df;expires=Thu, 01-Jan-1970 00:00:00 GMT;Max-Age=0;path=%2Fwp-admin;domain=;secure;httponly;SameSite=None
set-cookie: wordpress_logged_in_dcfecb4f7f4693ded9f0540a1d77266b=seravo%7C1603390318%7CWwBZ0e1TqBKjL6xX8qH0ZHW9sru0e0TNsgDnSgMHfGU%7C0de35ac9c7667d2c21aa85c70177c419bc449454b909278f862a96986413ed3b;expires=Thu, 01-Jan-1970 00:00:00 GMT;Max-Age=0;path=%2F;domain=;secure;httponly;SameSite=None
set-cookie: wordpress_user_sw_dcfecb4f7f4693ded9f0540a1d77266b=+; expires=Mon, 21-Oct-2019 18:11:58 GMT; Max-Age=0; path=/
set-cookie: wordpress_user_sw_secure_dcfecb4f7f4693ded9f0540a1d77266b=+; expires=Mon, 21-Oct-2019 18:11:58 GMT; Max-Age=0; path=/
set-cookie: wordpress_user_sw_olduser_dcfecb4f7f4693ded9f0540a1d77266b=+; expires=Mon, 21-Oct-2019 18:11:58 GMT; Max-Age=0; path=/

Note expiry time!

When I select “Remember me” and it works:

set-cookie: wordpress_test_cookie=WP+Cookie+check; path=/; secure
set-cookie: wordpress_sec_dcfecb4f7f4693ded9f0540a1d77266b=seravo%7C1604427186%7Cn6NprWMvzxd17i2VtsX7ZFI79ygZZpKDXLroG3JZylB%7C730c7e29358b26d6fab4c28628a1cade618b19224f22d386a459486b05d64b74;expires=Wed, 04-Nov-2020 06:13:06 GMT;Max-Age=1252800;path=%2Fwp-content%2Fplugins;domain=;secure;httponly;SameSite=None
set-cookie: wordpress_sec_dcfecb4f7f4693ded9f0540a1d77266b=seravo%7C1604427186%7Cn6NprWMvzxd17i2VtsX7ZFI79ygZZpKDXLroG3JZylB%7C730c7e29358b26d6fab4c28628a1cade618b19224f22d386a459486b05d64b74;expires=Wed, 04-Nov-2020 06:13:06 GMT;Max-Age=1252800;path=%2Fwp-admin;domain=;secure;httponly;SameSite=None
set-cookie: wordpress_logged_in_dcfecb4f7f4693ded9f0540a1d77266b=seravo%7C1604427186%7Cn6NprWMvzxd17i2VtsX7ZFI79ygZZpKDXLroG3JZylB%7C3d8c3509c9db07390241cbcde794ea4b55bea126c94837b3e1e244ec07ad2164;expires=Wed, 04-Nov-2020 06:13:06 GMT;Max-Age=1252800;path=%2F;domain=;secure;httponly;SameSite=None
set-cookie: wordpress_user_sw_dcfecb4f7f4693ded9f0540a1d77266b=+; expires=Mon, 21-Oct-2019 18:13:06 GMT; Max-Age=0; path=/
set-cookie: wordpress_user_sw_secure_dcfecb4f7f4693ded9f0540a1d77266b=+; expires=Mon, 21-Oct-2019 18:13:06 GMT; Max-Age=0; path=/
set-cookie: wordpress_user_sw_olduser_dcfecb4f7f4693ded9f0540a1d77266b=+; expires=Mon, 21-Oct-2019 18:13:06 GMT; Max-Age=0; path=/

This seems like a duplicate of https://www.ads-software.com/support/topic/refreshes-login-screen-when-logging-in/

Login only works if “Remember Me” is selected, otherwise users are just redirected back to the login screen.

Ping?

Why don’t you reply?

No way to contribute, or..?

I wrote this patch to fix the failure mode of Flow-Flow. Currently if the database connection is flaky, there is an unhandled error thrown. The least that should be done, is to prevent the error from being cached. Currently the Flow-Flow error is just a normal HTTP 200 OK respons like any other, which is a design flaw in my opinion.

--- /data/backups/data/wordpress/htdocs/wp-content/plugins/flow-flow/includes/db/FFDB.php	2020-06-06 10:01:59.000000000 +0300
+++ FFDB.php	2020-06-06 10:14:41.258273222 +0300
@@ -45,3 +45,2 @@
                } catch(\Exception $e){
+                        header($_SERVER['SERVER_PROTOCOL'] . ' 500 Internal Server Error (Flow-Flow bug)', true, 500);
+                        nocache_headers();

The link above does not work anymore..

I guess this is still unresolved. If somebody want’s to automate negating the stupid option, and in effect prevent any user from selecting it, but this in your cron:

wp db query "UPDATE wp_wfConfig SET val=0 WHERE name='other_hideWPVersion';"

Users are often qualified to install plugins, edit the theme etc but we don’t trust all admin users to correctly configure plugins that contain “bad” options.

The example by @janwoostendorp is great. It will help smart developers to protect site settings being messed up by less smart developers. It is a great suggestion and a good compromise if you don’t agree on completely removing the readme.html renaming in the first place.

We are not interested in a workaround, we already have plenty of them, but we wish the author to provide us with the final fix.

This example by @janwoostendorp is great. Please, please @mmaunder add this filter so that developers can disable the feature no matter how many times users try to select it.

An error message like this is usually related to a too big query, field or something else in the database. Try analyzing your database – is something unhealthy big? Clean it up. If not possible, find a server expert and get help to migrate to a bigger server with bigger database limits.

Yes. Just use the same theme on both sites and the branding will look the same.

What output do you get if you run ping www.ads-software.com or curl -IL www.ads-software.com on the server? It seems the connection to www.ads-software.com is somehow blocked.