Mother Blog – Troubleshooting Guides
I realize I have many, many things.
It’s not clear if those things will be of use to other humans but, at worst, here is something you can ignore. At best, take some hard-won experience and avoid the hassle.
These five things solve 98% of our mother blog syndication issues for students.
On the professor side . . .
This is my supporting documentation for the #PressEd WordPress conference that I’ll be doing via Twitter on Thursday. The Topic Given I’ve been playing around in WordPress since what feels like the dawn of time, I’ve heard lots of people say lots of things about it. I’ve heard it’s too complex. I’ve heard it’s too easy. I’ve been told it won’t allow you to map/GIS information and that it can’t be used for any number of other things. I’ve been told it won’t do things that you can do in this other CMS or that other LMS. As with most things, these boundaries are mostly imaginary and live more in people’s heads than they do in the software itself. My goal here will be to take you on a tour of what you can do to impact the authoring experience in WordPress. We’ll start by removing complexity from WordPress itself but staying within the typical authoring patterns. We’ll do that in the easiest ways first and then move to more involved interventions. After that, we’ll jump to non-standard authoring patterns and run around seeing where the edges are. Minimalism/Reducing Complexity Screen Options There’s quite a bit of control you have just within the Screen Options settings available to the author. If you can check/uncheck a box these options are available […]
There are lots of ways users can end up associated with many sites in a WordPress multisite install. That’s no big deal if it’s only five or ten but sometimes it’s way more. It’s not just messy, it actually degrades performance when you’re logged in because the admin menu bar loads all those sites. This can really become a drag as you pass a hundred or so sites. Previously, I’ve just given up on the user and made a new one. I’ve also gone through https://theSite.us/wp-admin/network/users.php and opened up a number of sites and removed the user from each one manually. That’s a pretty awful pattern but being in a hurry leads to all sorts of bad choices.Proper water bailing form is rarely considered when the boat is barely being kept afloat. Today I got the request to remove around six hundred sites from a particular faculty member. The request coincided with time and mental bandwidth so I opted to do this in an intelligent way. There was also no way I was going to do this by hand. First step would be to get the user’s id from the wp_users table. You can look up users here by user_login or user_email and get to what you need pretty quickly. If you’re using Sequel Pro rather than the terminal don’t […]
So I’ve installed WPMU on one of our externally hosted servers and with Jim’s patient assistance have been trying to get it in shape. One of the things I needed was the theme editor. So I was going through the steps to get it installed and things are looking good when . . . I hit the theme editor tab and the video below happenedand happened every single time I hit the theme editor tab. In all honesty, the first time it happened it scared the hell out of me. I frantically thought of all the vague warnings I’d received, reconsidered what I’ve done with file permissions, wished I’d backed things up and then realized I already had. I’ve since been wrestling with the .htaccess file and other fairly dreadful nerd stuff. Unfortunately, this server is running both PHP 4 and 5 and has some custom .htaccess stuff set up to password directories down the line. This has led to all kinds of hassle for me (and as a result hassle for Jim 🙂 who has insisted I blog about the easter egg so he can reblog itIsn’t the Internet a weird place).