I'm a web developer/sysadmin/host (NERD TRIPLE THREAT!) and this is my attempt to write about...leaving the house. Sometimes. Like, to go backpacking. And take some pictures. And justify spending the money on all the gear WHY SO MUCH?!?
Feel free to write and complain.
This didn't end well...
Remember that previous thing? MAKE SURE YOU DO THIS PART BECAUSE I DIDN'T AND I AM A CAUTIONARY TALE
deny from all
in root folder .htaccess. You want things to work in all the folders, right?
It seems there are few things that setting allow_url_fopen to "On" cannot fix.
I feel guilty about getting all worked up about Mitt Romney. #TheSecret
So, ever try to permanent store a self-signed SSL certificate in Firefox whilst in private (PR0N!) browsing mode? Really? ARE YOU SURE?!?
Seems you can't do it, anyways. What you CAN do is first load the site in question in non-private mode, accept the cert permanently, THEN reload site in private browsing and you're good to go.
So a customer requested an update to their PHP configuration file (we give them their own .ini file but they cannot access it directly because WE ARE JOB CREATORS). Evidently a WordPress plugin needed the max_input_vars increased (it's 1000 already ARE YOU TRYING TO NAIL DOWN EVERY SHINGLE ALL AT ONCE? Strong roof, that). Easy change, just modify the line and back to the BBQ.
I checked --the right php.ini file is loaded. The new change took, but now previously edited items are showing undefined values. Whuh?
Well, it seems phpinfo will not necessarily inform you if you have a syntax error in the php.ini file. You know, something dumb like using a colon instead of a semi-colon for a comment. DUHRRR.
Important safety tip: Check your colons, people.