piantadosi

Thank you, Tara. Yes, if only Google hired people who didn’t exclusively fix things that aren’t broken, we’d be fine. Check with me before you go through any test server fun times (or I will check back in if I get an answer sooner); the truth is, the publisher is also considering moving all the websites, including the three WP sites I built, to another CMS (don’t even ask) that is used by the one relatively gigantic news site he recently acquired. If that happens, it’s probably time for me to hang up my gloves and look for a shuffleboard team.

Meantime, don’t know if you saw this, but here’s something I hadn’t heard about: https://www.wordable.io. If it works, it could be worth the high-ish cost for someone like you (or me) who needs to move a bunch of Docs all at once to one or more sites.

Thank you!

• This reply was modified 7 years, 2 months ago by piantadosi.

Thanks, Cindy! That was it. I had a Links widget active in the footer of the problem site (but not on the other working site running the same theme). I deactivated it — and the errors went away, and the edit shortcuts returned. Thank you so much for the reply.

That was dumb of me. For some reason I totally missed noticing the second row of settings tabs. Thank you!

Yes, thanks, but this slider is set to display dynamic post slides, so how does it determine (or how do I know) which slide is No. 1? There is no static list of slides, since it is updated dynamically from the posts in the specified category.

Plus you didn’t really answer the question — does the slider respect the sticky post setting or not? I’m guessing not.

Thanks again.

I am having the same problem, and I would disagree that 1.5.7 fixed this problem. I just installed 1.5.7, after deactivating and deleting WP Super Cache a month ago because it just stopped working — and within minutes of activating it, no one could read any pages on our site, unless they are into white on white.

The log is filled with a few hundred of these:
PHP Fatal error: Call to a member function get() on null in /home/x/x/x.com/public_html/wp-includes/cache.php on line 123

Sorry, Tara. Yeah, for now we can focus on other apocalypses we all fear. ??

Nevermind. Cron problem.

Marking as resolved.

Hey Matt,

I made the fix and, as you say over there, Bob’s your uncle.

Whomever your uncle is, you can tell him I have only good things to say about his nephew Matt.

Thanks once again.

Roger

PS: Unless it’s really complicated to explain to a non-coder like me, let me know if there’s a way that I can see what’s coming over from Google. I tried downloading a few Docs files as rtf and html, but the text formatting was done in a totally different way in the downloaded documents.

Um, afraid to ask but . . . has anyone else noticed that bold and italic attributes are not being caught? Maybe it’s just me. It’s probably just me. Or maybe Google changed something again. It was working fine two days ago.

I have double- and triple-checked that Matt’s additional code is indeed there in docs-to-wp.php (we just switched hosts, so I’ve been doing a lot of copying and verifying). Should I check if the PHP version on the new host is new enough? No errors or warnings in the log.

Also, Matt, if you’re there, I can’t seem to get the Google tracking code removal patch you created to work. It does get rid of the preceding https://www.google.com/url?q= just fine but the “&sa=” and the long tracking code following that are still there, so the base url is correct but it arrives at the destination and tries to execute a variable or find a page that doesn’t exist.

If anyone else has noticed a change in the way the Drive API is coding text or link attributes, let me know. I’m going to check my horoscope now.

Roger

Thanks very much for all of this, Matt.

Many thanks to you, Matt — and, in other support threads, @tararebeka — for your help getting the plug-in working again and definitely making this a way luckier day than iIthought it would be when it started.

@traceylaizzi, that Google Docs add-on died without warning on July 1, and the developer’s website is also gone. we are also a local news organization and we had also been using it, or trying to, for the last year. I could be wrong but I don’t believe Matt has anything to do with the browser-based add-on. However I wanted to confirm that you are not alone — and also that this WP plug-in works, and way more reliably, than the add-on ever did.

Roger

Also, comments in the Doc and a link to open it for editing from WP also no longer transfer.

Got 0.4 working again, at least until the Google hammer comes down. Thank you and good luck to you, too. I await word from our esteemed plug-in authors.