• Resolved smackayht

    (@smackayht)


    Currently converting many sites to PHP7.2. When activating this plugin I get a 502 page “The page request was canceled because it took too long to complete”
    This is on WPEngine network.

Viewing 15 replies - 1 through 15 (of 70 total)
  • Sunny Lal

    (@sunny454)

    Hi @smackayht,

    The latest version of PHP (7.1 and 7.2) uses vast amounts of RAM memory. It causes in most users hosting accounts, the import feeds to hang, and can also cause the error you describe due to lack of available memory.

    In WPEngine, this seems to be a common problem with the PHP 7.2 upgrade.

    Until they can optimize memory, I suggest downgrading your account to PHP 7.0. This will release enough memory for proper function of the calendar.

    Thread Starter smackayht

    (@smackayht)

    I will contact WPE and have them investigate further. We are an enterprise client and have our own servers.
    I also just tried activating it on a brand new instance with no other plugins or content. Same result.

    Sunny Lal

    (@sunny454)

    Hi @smackayht,

    Thanks for the report. I have submitted a bug report for our Dev Team to accomodate this issue and it should be fixed for the next release of our plugin (sorry, I don’t have a specific ETA).

    Thread Starter smackayht

    (@smackayht)

    Thanks, I will keep an eye out for it.

    Any news Sunny on when the next release is coming. I have just found the same problem after migrating to 7.2 on WP Engine. It now 502 bad gateways if I active the plugin. WP engine say it writing to memory it doesn’t have access to. It’s a real problem for me.

    Hi @apphut,

    I don’t have an ETA, but it is currenly being worked on.

    I recommend regarding error you receive to make sure that you have all PHP extensions enabled.

    Just want to add that I have just also had to deactivate the plugin due to 502 errors that were killing the entire site. We are also on WpEngine. Deactivating the plugin solved this. I advised the client that their wonderful plugin will be back after the next update. ??

    Please reply when the update is live as Im tracking this thread.

    thank you.

    • This reply was modified 5 years, 11 months ago by NormanBird.

    Hi @normanbird,

    In the next couple of days, keep an eye out for updates available in your Plugins section — you will see the update for the All In One Events Calendar.

    Hey guys @normanbird @smackayht @apphut

    We have fixed the plugin for PHP version 7.2.

    I need users who are willing to test the new version of our core calendar — all you have to do is contact me by sending an email to sunny @ time.ly (remove spaces), then I will send you the new plugin version.

    You will then need to rename your existing directory under /wp-content/plugins/

    from

    all-in-one-event-calendar

    to

    all-in-one-event-calendar-bak

    Then upload the new folder to the same directory:

    all-in-one-event-calendar

    Then report to me if there are any other issues (there shouldn’t be).

    Once we confirm this is working flawlessly, a release will be issued for everyone else.

    I have emailed you, happy to test asap.

    Thanks

    I received and tried the fix. exact same error. no change at all. as soon as I activate the 2.5.33 version, I see the 502 error.

    That’s a shame, thanks for letting me know.

    FYI. Version 2.5.33.1 released by our system admin, solved all errors for one user on WPEngine, after he reported errors with 2.5.33 (Undefined index: enabled_mobile ). Original error from this user was 502 Bad Gateway.

    If anyone else would like to try this version, email me at sunny @ time.ly (remove spaces).

    FYI everyone – All In One Calendar version 2.5.35 has just been released and fixes other read errors that some users reported.

    Unfortunately, the 502 bad gateway errors occur as soon as you activate the plugin. Just tried 2.5.35. The same problem is still present.

Viewing 15 replies - 1 through 15 (of 70 total)
  • The topic ‘php7.2 502 error’ is closed to new replies.