I had another tick, a big one, though this time it didn’t leave a mark at all.Continue reading post "#3405"
After another strong anxiety attack, I’ve been off and on sickly for over a week.Continue reading post "#3402"
I had another health incident yesterday. It kind of makes me feel like I’m dying.Continue reading post "#3389"
xmlrpc.php file of my WordPress blog recently got hit by a single bot some 5000 times over a half hour period recently. I temporarily disabled all visitors and then limited it to just blocking the specific IP via Apache conf (htaccess).
I woke up in the middle of the night last night fighting a strong feeling of sickness. I think it was just a stomach bug.Continue reading post "#3325"
I bought a short domain name in part so I could have a short email address that was easy to share. Unfortunately, I’m finding it to sometimes confuse people or require more effort than expected to spell out.Continue reading post "#3314"
The installation of a new version of nodejs via MacPorts took nearly two hours.Continue reading post "#3312"
I guess npm doesn’t find a version of a package that matches the current environment when doing
npm install whatever.
I successfully switched my regular Firefox profiles back from Developer Edition to regular edition by waiting for the version to update.Continue reading post "#3305"
One of Cogneato’s clients noticed that Recaptcha wasn’t working on their site. The checkbox wouldn’t check at all. I noticed that there was an error like “Unexpected token in JSON at position 0” in the browser’s console log. Since this was one of our really old sites, I figured it might have some sort of inadequate polyfill for
JSON.parse(). I saw that the site was using Prototype.js, so I looked through the script to see if it was overriding that method, but it wasn’t. That did put me on the right track, though, to find the Stackoverflow answer that solved it for me.
Prototype was overriding the now browser standard
reduce() method of
Array.prototype with its own, incompatible functionality. The solution was simply to remove that method from the “prototype.js” file. We weren’t using the special Prototype functionality anywhere, so this didn’t cause a problem. If we were, we’d probably have to duck punch the browser’s functionality to handle both method signatures.