Fatal Error

  • Resolved linguamasteri

    (@linguamasteri)


    4 years, 12 months ago

    Hi there,
    I updated to your new version today but have had to undo by reverting back to my last backup as it was causing a fatal error on my site.
    Love the plugin usually though.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author George Tudor

    (@geowrge)

    4 years, 12 months ago

    Hi. Sorry to hear that, we are aware of some errors. Is it possible to check your server’s error logs and paste her whatever is related to the plugin? Thanks

    Thread Starter linguamasteri

    (@linguamasteri)

    4 years, 12 months ago

    I’m not really sure how to do that! Sorry. Happy to with guidance but I’m sure you have other stuff you need to deal with.

    Plugin Author George Tudor

    (@geowrge)

    4 years, 12 months ago

    If you have a shared hosting and have access to Cpanel, you will be able to see some menu called Error Log or Logs. If you can find it, it will be great.

    Other than that, can you write a list of all the plugins that you have enabled? Thanks

    satonacchi

    (@satonacchi)

    4 years, 12 months ago

    I’m having a similar failure on my site.

    The error message is as follows:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 180224 bytes) in /home/*********/demo/chrea/wp-includes/wp-db.php on line 2056

    WordPress databaseerror: [Commands out of sync; you can't run this command now]
UPDATEchrea_optionsSEToption_value= '1622677075' WHEREoption_name` = ‘action_scheduler_lock_async-request-runner’
    WordPress databaseerror: [Commands out of sync; you can’t run this command now]
SELECT COUNT(DISTINCT claim_id) FROM chrea_actionscheduler_actions WHERE claim_id != 0 AND status IN ( ‘pending’, ‘in-progress’)
    WordPress databaseerrorー: [Commands out of sync; you can’t run this command now]
SELECT a.action_id FROM chrea_actionscheduler_actions a WHERE 1=1 AND a.status=’pending’ AND a.scheduled_date_gmt <= ‘2021-06-02 23:36:55’ ORDER BY a.scheduled_date_gmt ASC LIMIT 0, 5`

    best regards.

    • This reply was modified 4 years, 12 months ago by satonacchi.
    Plugin Author StaxWP

    (@staxwp)

    4 years, 12 months ago

    Hi, please update to latest version 2.1.1 and any issues related to migration should be solved.

    Let me know

    Thread Starter linguamasteri

    (@linguamasteri)

    4 years, 12 months ago

    Fantastic. It’s working great now. Thank you.

    Plugin Author StaxWP

    (@staxwp)

    4 years, 12 months ago

    Awesome!
    Thanks for your patience and we hope you like the new improvements and the fact that it will allow more conditions to be added in the future.

    Cheers

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Fatal Error’ is closed to new replies.