technomad42
Forum Replies Created
-
Forum: Reviews
In reply to: [Gutenberg] What idiot…Basically, everything: The UI is obscure, the presentation poor and inconsistent and it is simply impossible to coherently create or edit a post. The underlying implementation is broken: slow, lagging, breaks and fails to support many of the common tools in our (and many other peoples’) workflows. Revert, Replace, Rethink.
Solved using the Gist mu-plugin code.
Forum: Plugins
In reply to: [UpdraftPlus: WP Backup & Migration Plugin] Restoring MultisiteHad I but known that, I could have saved myself two days work this week. As it was, the messages from the plugin on a fresh WP install were so unhelpful and damning that I simply reverted to my second-level SQL backups (NOT Updraft) and managed recover the data directory from the faulty EBS volume.
Here’s an irony – on a successful restore, i’d immediately have gone out and taken out a sub to the full version: as it is, you’ve turned off this potential customer for life.
Thanks – that could be considered a bit of a testing failure though!
Forum: Plugins
In reply to: [WP Hide Post] New update errors+1 Today’s update completely white-screened my entire multisite installation. removing the plugin brought it back. So what didn’t get tested?
Here’s one of the log lines – as you can see, it’s a standard xmlrpc.php call. I obviously don’t want to open up xmlrpc calls, so can I whitelist on any basis? I’m assuming that user login wouldn’t actually work as it needs to be authenticated via the xmlrpc call before the firewall knows whether to block it or not…
06/Apr/17 08:20:53 #4119297 high – xxx.xxx.xxx.xxx POST /xmlrpc.php – Access to WordPress XML-RPC API (system.multicall method) – [/xmlrpc.php] – domain.com
27/Apr/16 12:57:51 #2424456 critical – xx.yy.zz.aa POST /index.php – Blocked file upload attempt – [test.jpg, 218,665 bytes] – <domain>.org
It shows me as whitelisted:
“admin (you are whitelisted by the firewall)”Under firewall policies, Disallow uploads was disable: my understanding is that this shouldn’t affect whitelisted users. Switching it to Allow Uploads however solves the problem. But obviously reduces security
Here’s an example from a live log.
1. I create a gallery from Lightroom. It works, but then tells me I’m blocked.
2. After the timeout period, I try to upload a bunch of images. It succeeds but gives me the blocked by host message from the plugin again.HTH
Richard[22/Mar/16:16:45:48 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:46:41 +0000] – xxx.xxx.xxx.xxx “POST /wp-admin/admin-ajax.php” “https://domain.name/wp-admin/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17” “-” “domain.name”
[22/Mar/16:16:48:46 +0000] – xxx.xxx.xxx.xxx “POST /wp-admin/admin-ajax.php” “https://domain.name/wp-admin/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17” “-” “domain.name”
[22/Mar/16:16:50:47 +0000] – xxx.xxx.xxx.xxx “POST /wp-admin/admin-ajax.php” “https://domain.name/wp-admin/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17” “-” “domain.name”
[22/Mar/16:16:51:15 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:51:17 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:51:19 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:51:50 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:51:52 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:51:54 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:51:58 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:00 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:02 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:06 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:08 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:09 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:13 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:15 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:16 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:20 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:22 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:24 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:28 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:30 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:31 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:33 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:35 +0000] – xxx.xxx.xxx.xxx “POST /xmlrpc.php” “-” “Lightroom/6.4 CFNetwork/760.4.2 Darwin/15.4.0 (x86_64)” “-” “domain.name”
[22/Mar/16:16:52:49 +0000] – xxx.xxx.xxx.xxx “POST /wp-admin/admin-ajax.php” “https://domain.name/wp-admin/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17” “-” “domain.name”Forum: Plugins
In reply to: [Page Builder by SiteOrigin] post loop "additional"Greg, as this post isn’t closed, what do I need to use in the additional field to exclude a single category?
Thanks
Before the problem arose, in Network Admin>Sites, I had each domain showing against the relevant site – ie the site Domain was set to the routed domain, e.g. <name>.com. I then had each domain listed in Settings>Domains, with each as a primary. The list included a list of the format:
<name>.com
<name>.org
…
<subdomain>.<primary domain>.comAnd that was all working fine. Then, at some point during an update, all the routed domains listed in Settings>Domains vanished, leaving only the single <subdomain>.<primary domain>.com entry. The individual sites though were still set correctly to their host domains. I’d also misspelt the remaining sub-domain entry! That’s the point at which I got into that endless authentication loop on everything except the host primary domain. Once I realised that the other domain entries had vanished, just re-entering them (and correcting the sub-domain entry) fixed the problem.
So, in my case, the problem seems to have been a combination of an update glitch and my failing to check that all settings were preserved.
HTH
Resolved. Turns out to be a slight misconfiguration (mine) in MU Domain Mapping that – for some reason – I was getting away with under WP 3.8 but which then broke in the described manner under 3.9.