• Resolved csgaraglino

    (@csgaraglino)


    Any reason why the “All-in-One Event Calendar Extended Views by Time.ly” add on would deactivate itself?

    The page I need help with: [log in to see the link]

Viewing 15 replies - 16 through 30 (of 42 total)
  • Generally good but very occasionally down. I do NOT have to log into time.ly again though, I just have to reactivate the plugin via the plugin page in WP-admin.

    But what you are saying has me thinking….there is code in the time.ly plugin that deactivates when certain errors occur:

    “deactivate_plugin” is present 4x in \plugins\all-in-one-event-calendar\lib\exception\handler.php

    I’m not a super-amazing php coder (CF is my thing) so I’m not positive these instances are responsible.

    • This reply was modified 6 years, 8 months ago by ohliza.

    OK< from support I just got word that if my server is down at all, the API for the add-on can’t connect and so it deactivates.

    This is very likely what is happening.

    I’m looking at two options now:

    1. Moved to Cloudflare so if server is down it isn’t really down, though I’m unsure if that will be enough to prevent the API from deactivaitng the plugin.

    2. Asking time.ly to NOT deactivate the plugin if it doesn’t get a server response. Or perhaps removing that code myself. The actual calendar never deactivates, only the add-on.

    I wouldn’t know the calendar code to that depth. That’s something Time.ly themselves will have more knowledge of. If collected anecdotal experience can point to a possible cause I’m happy to share it.

    At this point it might be faster to just write my own Frontend Submission form.

    I appreciate your help, in any case, dday61.

    Hi @ohliza,

    Addons will deactivate if the calendar is not logged into the Timely Network API, under Events > Settings >

    Please be sure you are logged into the Timely Network under Events > Settings > Viewing Events tab.

    If you are already logged in on that page, please log out, then log back in — they try your addon again.

    If you require further assistance, please log into your Timely account and open a ticket by clicking on the Get Help link, or click here: https://dashboard.time.ly/account/get-help.

    Thanks for jumping in @sunny Lal – I’ve got a 30+ message support email going with Ben about this and we haven’t been able to solve it yet. I started it in January.

    I am logged into time.ly before and after the random deactivations occur.

    Only once did I have to re-log in, and that was when this update was done and everyone got logged out without notice. https://time.ly/latest-update-wordpress-plugin-addons/

    This issue is different. The plugin deactivates and I have to click the “Activate” link in the WordPress plugin page to reactivate it. Then it works for anywhere form a few days to a couple of weeks, then randomly deactivates again. I got rid of Wordfence, that didn’t stop it.

    I’m still trying to find a solution with Ben but I welcome more minds looking into this. It seems a fairly common problem, I’ve found a dozen or more threads about it both here and on your site, with multiple people saying they have the problem too.

    UPDATE – I have uptime robot watching the site and it has not been down for any length of time since Feb 24th and the plugin has definitely deactivated more than once since then. So I don’t think that’s it.

    Hi @ohliza,

    Ok.

    In your specific case, the cause for deactivation is that the Timely API “thinks” your calendar is disconnected from it, even though you have logged in and reset the login. This can be caused by security settings, and most likely, another 3rd party security plugin that you may have installed. If you do, I suggest checking the settings, adjusting the security level, or, adding the URL for time.ly to an “allow” list (if available) so that there is no chance of the connection being severed.

    I disabled Wordfence awhile ago at Ben’s suggestion. Just today I also disabled Sitelock. Hopefully THAT will do it…also using Cloudflare now.

    Thankhyou @ohliza,

    Please update with results. I would be good to know what is causing this error on your website. I suspect Cloudfare can also cause this problem with API connectivity.

    Apologies for the troubles.

    Ben said he thought Cloudflare would be OK as several of your users use it without issue. I’m watching closely and Will update.

    I do need to use some kind of security plugin, unfortunately.

    I use WordFence on my live site without the deactivation problem. I do not use it on my test system.

    Again – might, or might not mean anything as they are both very complex plugins. Just another anecdote that might, or might not, lead somewhere worthwhile.

    Thanks @dday61.

    Hi @ohliza,

    Can I get you to check one more thing?

    I found a core calendar user whose addon deactivated due to the Timely Network being blocked by his WP-Cerber plugin which he was using “as a firewall and auto-optimize for caching/compression”. Can you check and confirm if you have any similar plugin, and also, check with your host, if there is a firewall, and if so, if “time.ly” is blocked at all? And if so, add to safe list.

    The only firewall I had was Wordfence, and Sitelock, both of which are gone. The add-on hasn’t deactivated since then, but it’s always been an occasional thing.

    I really wish I could have the add-on run locally, it would be SO much easier.

    • This reply was modified 6 years, 8 months ago by ohliza.

    Same problem happening here. Been going on for awhile. Besides Cloudflare, not using any of the above mentioned security plugins. Logged in all the time. And yeah, totally random. Very frustrating.

    Hi @doulos12,

    Since each case is unique, please log into your Timely account and open a ticket by clicking on the Get Help link, or, click here: https://dashboard.time.ly/account/get-help so I can further look into your account.

Viewing 15 replies - 16 through 30 (of 42 total)
  • The topic ‘Plugin Deactivateg Itself?’ is closed to new replies.