AskKim

A lot of “daily execution” plugins such as backup plugins rely on WP-Cron. It’s my understanding that wp-cron relies on a visitor accessing the site to serve as a trigger to kick some of those things off. So, in theory, if a plugin were doing that, disabling it on visitor-facing pages could prevent the wp-cron trigger perhaps? Or am I thinking about this wrong? (Or has something changed in wp-cron’s triggering since last time I needed to look at it, LOL)
Kim

Can disregard – sort of – turned out it was the prompt to install the contact form that was doing it. Probably should fix that, but at least I managed to dismiss it on another page.

Hmmm… hitting a roadblock. A “half-stack” of my plugins causes one copy of the message to turn up inconsistently. Meaning not on every refresh (or even every third refresh). I’ve been chasing this for a long while tonight and it’s maddening that it’s totally flakey.

It *may* be that it’s only turning up after enough time has lapsed to trigger an auto-save to kick in.

I haven’t given up yet, but calling it a night and will be out of the office the next day or two.

Kim

PS: Andrew thanks for your plugin awesomeness. I use that plugin on nearly every site I own or manage. Good stuff and mucho appreciated ??

I’m looking through plugins now but it’s more than a single plugin interaction so I’m having to track down multiples that may be playing a role and look if there are cross reactions too.

The extension of TinyMCE is the plugin TinyMCE Advanced and as far as I can tell is not my culprit.

I may not get this wrapped up tonight but am definitely investigating since after Mark mentioned it, I proved that it does not replicate on my test account on the same host.

Form what I can tell at the moment, several plugins either cause it or are involved in causing it. It may actually be that several plugins cause one copy of the memo to appear and multiple plugins can can cause one instance end up cumulatively being additive. Not sure yet.

Feedback courtesy of Joost de Valk: Shows DiggDigg should be properly using the WP HTTP API but isn’t.

I am the thread originator and have changed user IDs.

Here’s a quick followup

Grabbed the most recent update that you just released (thank you)

Now, however, instead of getting a redirect loop, after the authorization is clicked, it redirects to an api.twitter.com/login?redirect_after_login=”%2Foath…. etc etc. that is a 404 “Sorry this page doesn’t exist” error message.

So I went to the instructions in the FAQ.

I enabled logging, and clicked save.

Then, intent to demonstrate the issue, I tried again, and suddenly it worked.

I have no clue why that would have played a role but it did. (I’ve since turned off logging).

Thanks Ajay,
Kim