Well, we could not get multi-network to work correctly with WordPress in its own folder. It almost worked. Except that in the second network, the root blog, its admin pages, and the network admin pages were either coming up as 404’s or were unusable because jQuery and CSS were not loading. In the error logs we could see that WordPress simply did not have a big chunk of the path it needed to get the files it was looking for as PHP includes, and in the access logs we could see that the same chunk was missing from the URLs for jQuery and CSS. Why the main page of the blog was coming back as a 404 I have no idea. Why it didn’t have that path in a constant, I have no idea, since it had everything it needed for other blogs in the network to work perfectly.
If this topic is interesting to you, you may also like the text of my WordCamp Raleigh 2015 talk, Continuous Deployment: WordPress Code, Configuration, and Content.
Atlassian’s Bamboo seems to rarely be discussed in WordPress World ™, but it is entirely possible to marry the two. Most of the problems I had – and I feel pretty confident in using past tense at this point – were due to my own inexperience with WordPress. Our Bamboo server also did not have any PHP code installed or running, so our server admin had to take care of a few installs and related tasks to get everything running.
Over the last several months, I have installed and broken WordPress in so many different ways that I can’t remember them all. This process of installing, breaking, and fixing means that I understand WordPress so, so much better than I would have had I just done a straight up five minute install and moved on.
I didn’t mean to break it all those times. I am very glad, however, that I did.