For local database manipulation I still use Sequel Pro. Why? Well, all the derivatives (Like Sequel Ace) have a smaller feature set, and alternatives (like MySQL WorkBench) are too complex, and even limited. (How hard is it to provide a socket based connection, or an SSH tunnel TCP connection…)
Anyhoo, a quick note to myself for fixing the error
Double-check that the socket path is correct and that you have the necessary privileges, and that the server is running.
MySQL said: Authentication plugin ‘caching_sha2_password’ cannot be loaded: dlopen(/usr/local/mysql/lib/plugin/caching_sha2_password.so, 0x0002): tried: ‘/usr/local/mysql/lib/plugin/caching_sha2_password.so’ (no such file), ‘/System/Volumes/Preboot/Cryptexes/OS/usr/local/mysql/lib/plugin/caching_sha2_password.so’ (no such file), ‘/usr/local/mysql/lib/plugin/caching_sha2_password.so’ (no such file) Continue reading “A quick note regarding MySQL error about caching_sha2_password.so not being able to be loaded”
You may have already noticed or heard from your clients:
WordPress Multi-Domain Multisite (not subdomain nor subdirectory) has an annoying problem since version 6.8;
Every time you switch from one subsite to another, you have to log in again, and you are logged out of the other subsites.
Let me save you the time and effort:
No, it’s not a Cookie Domain problem, it’s not a Cookie Path problem, and there isn’t some sneaky software logging you out just for fun. It’s a side effect of the new password hash implementation in WordPress 6.8. Continue reading “WordPress 6.8 Multisite Forced Re-Login – Solved!”
Deprecated: pathinfo(): Passing null to parameter #1 ($path) of type string is deprecated in /data/sites/web/remonpelnl/www/wp-content/plugins/crayon-syntax-highlighter/crayon_langs.class.php on line 84
So. Fair warning. RANT incoming!.
Recently been working on an issue regarding GravityForms. When a visitor submits a file, the file is stored in a ‘secure’ location, which uses wp_hash to determine this ‘secure’ filepath. The link in the email is also ‘secured’ with this hash. Now, is this wrong? no. but it is also NOT correct. As you see, wp_hash uses the AUTH salt and key, which are used for user authentication, aka, login. One of the security measures we take is to prefix the AUTH tokens with a few things that make sure the user is logged out (for example) when the internet connection changes. (Your laptop gets stolen, that sucks, but your website login is invalid, so that stays safe.)
Local, the development environment for WordPress by LocalWP is great, but I am a terminal type of person. So I adapted an earlier script to work with the new Local version.
This script lets you do (nearly) all you need to do with Local from the CLI. Surely, a click of a button is not hard? true. But why use the mouse when you can use the keyboard. For instance
lbl ssh
opens a new Terminal shell specifically for the site you are in. (not chrooted, but it is set-up correctly).
Yes, I know. It’s been a long time since my last post, but I have a good reason. I have been busy, very very busy with a new 3D project.
Base on the fantastic work of David Given (https://cowlark.com) on FluxEngine I am in the process of developing a stand-alone device to read/write floppydisks (both 5,25 and 3,5 inch) to/from disk images. Please see David’s website on FluxEngine for more information on this part of the project.
You would say that the FluxEngine is the most difficult part made easy by David, and yes, that is true. What I am bringing to the party is the housing, fully 3D printed, the electronics to make it stand-alone, power supply, cooling etc. Interested? Please read on :)
A vulnerability has been discovered in Contact Form 7 that allows an attacker to upload malicious scripts. The publishers of Contact Form 7 have released an update to fix the vulnerability.
I recently replaced my trusty Synology RT1900ac with a “great, problem solving, multi-room Wi-Fi kit” from Asus, the Lyra MAP-AC2200. “The best of the best”. Yeah, … right.
Out with the old …
The problem with my apartment is that is about 60 years old, and some rooms are behind load-bearing walls. Not load-bearing for my ceiling, but load-bearing for the entire complex. Like 20cm thick reinforced concrete! Wi-Fi is problematic there. So this multi-room Wi-Fi set would solve that problem.
… in with the new.
Well it did; I got Wi-Fi, strong, fast, … for about 2 hours. Then a reboot of the closest Lyra node was needed. On top of that, incoming connections to the main node would no longer get through after about 4 days, so twice a week a full reboot of all nodes was needed, just to get a little Wi-Fi. After 6 months of this getting worse and worse, I was done. [Edit: turns out there is so much Wi-Fi signals here, the Lyra set gets confused … It’s a Wi-Fi jungle out here …]
In the end I had ping-spikes and drop-outs like crazy; sitting right next to the main node, pinging my ISP Modem through the Wi-Fi;
What the hell, Asus? You call this “superb Wi-Fi coverage”? This is a ping from Laptop -> 1 meter open air -> Asus Lyra Main Node -> 2 meters ethernet cable -> ISP Modem.
Playing online games was simply impossible. So I took out my RT1900ac again and settled with Wi-Fi being poor or even non-existent in some rooms.
A few days ago, however, I had enough of that too and I took a leap and bought the Synology RT2600ac + MR2200ac combo. The set-up of the RT2600ac was a breeze, but I had seen that before, as this works exactly like the RT1900ac. In fact; I downloaded a configuration backup on the RT1900ac, uploaded it to the RT2600ac and done. Unplugged the old, installed the new. All done.
The Synology RT2600ac Router
Well, almost; I still had the Mesh-node MR2200ac to set-up.
Yeah, I know. It’s been over a year since my last entry. I’m not the person to monetise online presence, I just post stuff about problems I faced and how I solved them. No biggie, right?
[Edit: This script is defunct since Local rebuilt the application and ditched the virtual machine. This script works only with the old “Local by Flywheel” and not with the “Local Lightning” app. For the latter, see my lbl script]
Local (by Flywheel) is great, but for a terminal type of person as I am, I find it way more convenient to SSH into a VM and use the WP-CLI to perform WordPress tasks. With a platform like Vagrant, one has the
vagrant ssh
command to shell into the virtual environment.
With Local, you can do this with the push of a button in Local, but as said, I like the terminal better.
lbf ssh
is waaaaay faster than going to the Local app, find the site, click the SSH button.
My blog uses Google Analytics, Adsense and OneSignal Push software for which cookies are set. All services have been set-up to be completely anonymous. - read more on cookies, privacy and GDPR
I'd like to include my twitter-feed for your entertainment;
Save preferences
