Two examples of PHP scripts that use WP-CLI. I like to do it this way rather than as a shell script because a) shell scripts are unreadable; and b) I don’t know how to write shell scripts. The first updates an option based on plugin activation and the current option value; the second selectively activates or de-activates a plugin based on the current theme.
A fix for a new bug. You read it here first.
Earlier this month I led two sessions at Seton Hall University as part of our Digital Humanities Summer Series. You’ll find links to my presentation materials about two-thirds of the way down the page.
A mistake so stupid that I couldn’t find any reference to it on the Web.
Catching un-moderated comments that are left hanging. Nuking (or freeze-drying) obsolete blogs. Adding large groups of users.
It got to the point where I needed to make WP-CLI go, or be doomed to outdated plugins and themes forever.
Now in its fourth iteration since I took over in the early part of this century. If you said, “hey that looks like Divi,” you win the big prize. Even with all its advanced features, this theme still needs some tweaking to keep it from looking horrible in spots. The main difficulty was in getting…
This is seemed pretty easy. The desktop app for WordPress, “Calypso,” turns out to be a snap to install. Doing anything more complicated gets to be, well, complicated. It’s got a long way to go before I’d turn a client loose on it.
I’m trying to make a simple customization to an Elegant Themes product, and their own support forums are giving two highly dubious responses.
There’s a couple of little things you can do with a little elbow grease and the Google. We’ve changed the header around, organized the portfolio module better, replicated the contact information bar in a footer widget, added next/previous links to our portfolio items. Hope this helps someone.