GeKo maintainer @franziska reports that the automatic update to WordPress 5.0, which is actively promoted in the dashboards we provide, currently breaks the editing workflow with the new Gutenberg editor. This concerns all WordPress maintainers
@AnandaVimal @gandhiano @captainplanet @LankaGAIA @saritamoreira @robert.orzanna @yova
The problem is described in https://wordpress.org/support/topic/publishing-fail-after-update-to-wordpress-5-0/
After editing the siteurl
and home
configuration options in the web interface, no logins were possible anymore. https://codex.wordpress.org/Login_Trouble did not help to resolve the situation.
A manual update of both keys in the wp_options
table to https://www.geko-berlin.de/
in the database helped resolving the issue after recreating the app
container.
From the recent attempt to upgrade the dysnomia
WordPress farm to version 5.0, we recall that some sites could not be verified.
From https://hack.allmende.io/s/ecobytes-wordpress-40#Verify (via https://lab.allmende.io/ecobytes/lab/wordpress/issues/40#note_14440) we inherit:
Sorry didn’t mean to give you extra work, since I never had an answer I assumed that either you had fixed it or weren’t going to so I closed the issue in my head. Btw the chat at Riot doesn’t seem to work, is there a new chat or should I always use the email?
@LankaGAIA was so kind to inform us on June the 4th to support@ecobytes.net, that they are getting login errors at https://gaia.org.pt/wp-admin
Your access to this site has been temporarily limited by the site owner.
A quick research ¹ shows that apparently Wordfence permanently disables the login and needs to be switched off and on again to regain access.
¹ * wordpress Your access to this site has been temporarily limited by the site owner. at DuckDuckGo
Ah Lanka, that seems automatic then. So I wouldn't have had to disable the Wordpress plugin after all?
Intervention happened today, not back then. So I might as well restore it to its original location, then. And the hour that I spent investigating this was not needed, after all.
mv /data/domains/dysnomia.ecobytes.net/data/plugins/wordfence.bak /data/domains/dysnomia.ecobytes.net/data/plugins/wordfence
Closing here.
Yes my access was reatored after 24 hours, don’t know if automatic or because of Intervention?
We learn which plugins are in use of non-archived sites in the farm /data/domains/dysnomia.ecobytes.net
with
# docker-compose exec -T mariadb sh -c 'mysql -u${MYSQL_USER} -p${MYSQL_PASSWORD} -h localhost ${MYSQL_DATABASE} -e "select blog_id,domain from wp_blogs where archived = 0;"'
blog_id domain
1 dysnomia.ecobytes.net
5 climatedenial.org
7 dante.ecobytes.net
8 gaia.org.pt
11 musikkneipe-klampfe.de
19 ttwitzenhausen.de
20 spiritsoundart.dysnomia.ecobytes.net
22 hbml.dysnomia.ecobytes.net
23 schuetz-it.com
27 juliatulke.com
28 luas.de
# docker-compose exec -T mariadb sh -c 'mysql -u${MYSQL_USER} -p${MYSQL_PASSWORD} -h localhost ${MYSQL_DATABASE} -e "select blog_id,domain from wp_blogs where archived = 1;"'
blog_id domain
4 eyfa.org
6 hyokyaalto.net
18 vanillaway.net
25 tango-empatico.dysnomia.ecobytes.net
26 pro-werraquerung.de
29 bunte-liste-wiz.de
# docker-compose exec -T mariadb sh -c 'mysql -u${MYSQL_USER} -p${MYSQL_PASSWORD} -h localhost ${MYSQL_DATABASE} -e "select blog_id from wp_blogs where blog_id = 1;"' | tail -n +2 | xargs -I {} docker-compose exec -T mariadb sh -c 'mysql -u${MYSQL_USER} -p${MYSQL_PASSWORD} -h localhost ${MYSQL_DATABASE} -e "select option_value from wp_options where option_name = \"active_plugins\";" | tail -n +2 | cut -d":" -f3- | printf "{}:\n$(cat -)\n"'
1:
{i:4;s:23:"wordfence/wordfence.php";i:5;s:24:"wpforms-lite/wpforms.php";}
# docker-compose exec -T mariadb sh -c 'mysql -u${MYSQL_USER} -p${MYSQL_PASSWORD} -h localhost ${MYSQL_DATABASE} -e "select blog_id from wp_blogs where archived = 0;"' | tail -n +3 | xargs -I {} docker-compose exec -T mariadb sh -c 'mysql -u${MYSQL_USER} -p${MYSQL_PASSWORD} -h localhost ${MYSQL_DATABASE} -e "select option_value from wp_{}_options where option_name = \"active_plugins\";" | tail -n +2 | cut -d":" -f3- | printf "{}:\n$(cat -)\n"'
5:
{i:0;s:19:"akismet/akismet.php";i:1;s:41:"wordpress-importer/wordpress-importer.php";}
7:
{i:0;s:19:"akismet/akismet.php";i:1;s:41:"wordpress-importer/wordpress-importer.php";}
8:
{i:2;s:60:"advanced-custom-fields-link-picker-field/acf-link_picker.php";i:3;s:19:"akismet/akismet.php";i:4;s:44:"amazing-post-widget/amazing-posts-widget.php";i:5;s:47:"attachment-file-icons/attachment-file-icons.php";i:8;s:28:"category-posts/cat-posts.php";i:10;s:39:"contact-form-to-email/form-to-email.php";i:11;s:25:"subscribe2/subscribe2.php";i:12;s:68:"the-events-calendar-extension-registration/wp-event-registration.php";}
11:
{i:0;s:19:"akismet/akismet.php";i:1;s:23:"gwolle-gb/gwolle-gb.php";i:2;s:29:"hide-featured-image/index.php";i:3;s:21:"newsletter/plugin.php";i:4;s:33:"post-expirator/post-expirator.php";i:5;s:92:"removehide-author-date-category-like-entry-meta/remove-author-date-and-category-metadata.php";i:6;s:49:"responsive-full-width-background-slider/rfwbs.php";i:7;s:28:"robo-gallery/robogallery.php";i:8;s:37:"show-hide-author/show_hide_author.php";i:9;s:17:"so-css/so-css.php";i:10;s:17:"sticky/sticky.php";i:11;s:43:"the-events-calendar/the-events-calendar.php";}
19:
{i:0;s:19:"akismet/akismet.php";i:1;s:55:"all-in-one-event-calendar/all-in-one-event-calendar.php";i:6;s:41:"wordpress-importer/wordpress-importer.php";}
20:
{i:0;s:41:"wordpress-importer/wordpress-importer.php";}
22:
{i:0;s:23:"gwolle-gb/gwolle-gb.php";i:2;s:17:"so-css/so-css.php";i:4;s:27:"theme-check/theme-check.php";i:5;s:41:"wordpress-importer/wordpress-importer.php";}
23:
{i:0;s:48:"capability-manager-enhanced/capsman-enhanced.php";i:1;s:25:"subscribe2/subscribe2.php";}
27:
{i:0;s:19:"akismet/akismet.php";}
28:
{}
In our case the plugin is provided on the farm level and needs to be disabled for instances that are using it.
root@panda ~ # mv /data/domains/dysnomia.ecobytes.net/data/plugins/wordfence /data/domains/dysnomia.ecobytes.net/data/plugins/wordfence.bak
@LankaGAIA Could you have a look and try if your access has been restored after this intervention?
@LankaGAIA was so kind to inform us on June the 4th to support@ecobytes.net, that they are getting login errors at https://gaia.org.pt/wp-admin
Your access to this site has been temporarily limited by the site owner.
A quick research ¹ shows that apparently Wordfence permanently disables the login and needs to be switched off and on again to regain access.
¹ * wordpress Your access to this site has been temporarily limited by the site owner. at DuckDuckGo
As a Kubernetes user, I want to have a Wordpress operator, so that I am able to deploy and upgrade Wordpress sites by creating a Kubernetes object.
Implementation notes:
Acceptance criteria: