I hate hearing "this should be a quick one" from the client. Especially when your code base is a fucking legacy with no documentations, no testing, and a multisite that shares the same classes where functions has some crazy if conditions just to satisfy each site's requirements.

A week ago, the team that hired me asked me to fix the s**t they made when they hosted around 30 WordPress sites in a single Bluehost shared server. Several of those were multisite installations. The server eventually gone down because of the load. And the most disturbing part was they were taking money from some of their clients to host the sites, in stead of not having a reseller licence. The server was going down quite frequently so I suggested moving some sites to another host or another server. They asked me to do it, but when I asked for the permission to edit the nameservers, they asked me to make a subdomain and point it to the new server. Which was kind of impossible because the new host was already having some subdomains and it's not easy to work with sub-sub domains. So, on an open statement they said that I am unprofessional and not fit for work. Before that they disturbed me and bursted on me when I was off working hours. -_-

Worked on a WordPress Multisite project that required digging around to find ways to hook into areas that weren’t meant to be hooked, create and add custom core files that would withstand updates, ensure certain plugin capabilities were available even if the current site didn’t load them, and a variety of other black magic that I’m too fried to remember off the top of my head.

By the end of the project I more or less felt like a god in WordPress—There’s little I could ever want to get it to do that I didn’t know how to do.

Then again, this is all probably a long way of saying I learned some very bad ways to do things. Mercifully, it’s fully documented with PHPdoc blocks down to the loop level so that even a 3-year-old should be able to figure out the logic...

All this to say, I’m definitely ready for a new project.

FUCK YOU WORDPRESS wtffff with that shit , i can't use multisite if running in 8081 port ?, fuck you! your """ cli """, your media folder with that month and year stupid subfolders, your plugins and your fucking unit test running on a complete WP instance. GO FUCK YOURSELF! stop with that shit and remake all that shit.

Modifying .htaccess for WordPress multisite so that my custom url(slug) will redirect to wp-login for security reasons.
It is like performing a neuro surgery where the slightest of mistake will get u paralyzed.
I have already reached a vegetative state..
I wonder what more damage I could do? FML.

As if working with WordPress isn't annoying enough, now we are mixing in multisite. I had such high hopes for today...

Getting ready to finally launch a WordPress Multisite project I've been working on for over a year this weekend...and version 5.1 drops today.

And has significant additions in Multisite functionality that I should implement prior to launch while it's comparatively painless, rather than when we've got a bunch of sites with data to reconfigure.

Blah.

I run two servers, one that runs WordPress multisite and one that runs a vpn. As a self taught sysadmin I learn best through projects. I’m also interested in databases and backends for iOS (swift) apps. Do you have any suggestions for what I should make my servers do next? Thank you.

For WordPress devs:
We have a multisite structure and I have created a menu on one of the site, how to use that menu on another subsite, googling didn't help :/ please guide