Yes, I’m frustrated, as well – seems to be a problem with the API driving Freemius; I’m trying to get an update on that.
I finally had to disable it. Cheer up! Your plugin is fantastic! 🙂
It’s a problem with the Freemius site and a 10 second delay on the api call. Their entire site is screwed up. It is absolutely ridiculous you are making this call out on every page. Our client bought your PRO version of plugin and wasn’t even aware of this freemium malware that was installed with it and if it wasn’t for caching, their site would have been down. It took an hour to profile/debug the slowdown and I will absolutely be reporting this plugin as call outs are not allowed by the TOS without user consent.
That call should *not* be made on every page, only as part of the opt-in process. Can you provide a support request to let me know more information about where the call is being made inappropriately?
Question: are either of you using the WP to Twitter front-end widget?
No, only backend.
And could NOT opt out from Freemius selection.
I’ve released an update which should help, although I don’t know for sure. It may be that the Freemius API isn’t ready for the volume of requests I’m sending, in which case I’ll strip it out and release an update without it by the end of the day.
All right. Thanks in advance!
Here in Germany, the Freemium Service seems down.
> That call should *not* be made on every page, only as part of the opt-in process.
It is being called on every page, including admin-ajax. This is probably why Freemius is having issues because you are DOSing them. Run a profiler and see for yourself.
Yes, I’ve just had a conversation with Vova from Freemius, and they’ll be making some changes to their SDK to limit when it runs. I implemented it following their recommended methods, which it turns out are too aggressive for their API when run at this scale. I just released an update which will limit it.
However, based on conversations with Vova, they may not be ready for this scale, in which case I’ll release another update later today.
Joe’s calling Freemius exactly as he’s supposed to. So if there’s an error, it’s in Freemius’s own logic.
If it’s supposed to track on the front and back end, though, I’m surprised they tell you to put it in the main plugin file. You’d think a wrap of is_admin() would be smarter, and that would only run on the admin pages.
- The topic ‘Last update kills website’ is closed to new replies.