In responding to some data requests, I delved into the WP tables to pull some rampages data.
All users ever . . .
I need to set up something more automated but for this I dumped the MySQL tables as CSVs and then just imported them to Google Sheets. With very minimal functions, I got this data.
Had someone cut/pasting from Google Docs into WordPress and it was ending up littered with internal style elements and super irritating span classes. I found this post which got me 95% of the way there and just added .removeAttr(‘style’) to get rid of the inline styles. Now I can just re-cut/paste and get a clean chunk of text.
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 […]