You may note that when you cut/paste from Google Docs into the WordPress editor you get a bunch of span tag and inline CSS garbage. It’s awful . . . so you could paste into the plain text editor . . . but you may also find that you want to keep a bunch of the other HTML in there like links and lists and stuff. via GIPHY Jonathan Nicol figured this out way back in 2015 and I keep having to re-Google it or remember which theme I had it in so I’m putting it here to help me find it more easily. You can see my slightly tweaked version below. All credit to Jonathan and thanks to him for documenting it publically.
If you cut/paste from a Google Doc into the WordPress WYSIWYG editor you get more than I want. Mainly a bunch of inline CSS that sets the font weight (see below). This is a pain because it’s going to take priority in CSS land and undoing it by hand is a hassle. Some internet wandering led me to Jonathan Nicol’s fix for some span elements and bit of adjustment allowed me to also deal with the inline CSS elements. The extra nice aspect of this as a fix is that it only applies on paste actions so you can still write the stuff in the HTML editor if you want.
I did a workshop on productivity and now know that I took a bunch of knowledge for granted that could be helping people. So my new goal is to do a better job documenting stuff just in case it’s of use to people. To be clear, I don’t really care what people do with the time they reclaim from trivial and/or unpleasant tasks. I just hope to alleviate some degree of suffering. Maybe they’ll use their extra time to go for a walk or pet a puppy or something. You might also note the sub 60 seconds video tutorial time.1 1 I just want to tell you something as quickly as possible. Video tutorials seem to tend towards lengthy meditation sessions although now that I can control the playback speed very exactly they may become tolerable.
flickr photo shared by The National Archives UK with no copyright restriction (Flickr Commons) Suppose you wanted to automate a chunk of your CV creation. Suppose they’d let you do it digitally via Google Docs (if not aspects of this could still work but it wouldn’t be nearly as interesting) and that you’d like to link to the “proof” files. I am further supposing that you might be willing to think about doing this slightly differently. Usually people build the CV/tenure document and then go back and find/link to their evidence. The path I’m suggesting would allow you to gather the evidence as you came across it and then build the index to it automatically. You’ll still want to construct the overarching narrative but this takes the grunt work of listing/linking and puts it on the computer where it belongs.1 This is the proof of concept scenario. You could make it much better depending on your needs/wants but this ought to get you started with how it could work. This script does create a spreadsheet of all your content with a variety of useful links and creates a Google document with all the files as ordered list items under their respective folder headings.2 Given one folder called CV POC . . . in that folder are your three folders of […]
I was looking to have some people in my class publish lesson plans to their WPMU blogs via Google Docs. So I consulting the dean of WPMU, The Right Reverend Jim Groom, and he made it look so easy. Yet, I failed. Feeling stupid I started drinking looked at the differences in our set up. I began to worry it was because I wasn’t using dynamic subdomains. I reached such a depth of despondency that I actually read one of the error messages from Google itself. It said “Hey Dummy, you haven’t turned on XML-RPC publishing for that blog. Why don’t you go turn it on?” I did and everything now works. There’s a video on how to do that below in case it helps. pub2wpmu