• Resolved geirarnesen

    (@geirarnesen)


    The plugin is on the latest version 1.5.0
    The site is running with the latest version of WordPress 6.6.1, – we’re now getting this error, –
    upon every time the the plugin is executed.

    When updating the settings page, – its failing, – with a critical error.

    Any tip ??

    PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function GetUrlCron::geturlcron_add_action_cronjob(), 0 passed in /nas/content/live/oslokameraklub/wp-includes/class-wp-hook.php on line 324 and exactly 1 expected in /nas/content/live/oslokameraklub/wp-content/plugins/get-url-cron/geturlcron.php:1042#012Stack trace:#012#0 /nas/content/live/oslokameraklub/wp-includes/class-wp-hook.php(324): GetUrlCron->geturlcron_add_action_cronjob()#012#1 /nas/content/live/oslokameraklub/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)#012#2 /nas/content/live/oslokameraklub/wp-includes/plugin.php(565): WP_Hook->do_action(Array)#012#3 /nas/content/live/oslokameraklub/wp-cron.php(191): do_action_ref_array('geturlcron_even...', Array)#012#4 {main}#012 thrown in /nas/content/live/oslokameraklub/wp-content/plugins/get-url-cron/geturlcron.php on line 1042

    Geir

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author berkux

    (@berkux)

    Hi Geir,
    thank you for tying my plugin. I tried several things to reproduce the error.
    Are you using PHP 7 oder 8?
    The settings page is the “Basic settings” page or the page where you define the cronjobs?

    I’m testing hoping to find the bug. Anyone else with this?

    Best regards,
    Bernhard

    Plugin Author berkux

    (@berkux)

    Hi Geir,
    some fixes in verson 1.5.1 hopefully fix the issue. Can you check, please.

    Thank you,
    Bernhard

    Thread Starter geirarnesen

    (@geirarnesen)

    Hi Bernhard

    Thanks for a good try. Though this didn’t work either. When trying to watch the log in the plugin it I got a 5xx page. The error log shows this:

    PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /nas/content/live/oslokameraklub/wp-content/plugins/get-url-cron/geturlcron.php on line 303

    I would just add that the WordPress is hosted on WPEngine.

    Geir

    Plugin Author berkux

    (@berkux)

    Hi Geir,

    ok, this is something different. The plugin is loading a file and is using it. For that the plugin / wordpress needs some memory from the server.
    <<Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes)>>
    This means that 512 MB are available for the total wordpress. but now not even 20 kB are available.
    Maybe you have a very big logfile, then such a error can happen. At the settings of the plugin you can limit the days the logindata is kept. or you set the days to -1 to delete all logs.
    Is this an option to delete the logs?

    Bernhard

    Thread Starter geirarnesen

    (@geirarnesen)

    I tried this, – set the the days to -1.
    After this I tried to save the Set Cron Jobs, – and save the form, – which blowed out with a 5xx and logged this:

    PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 333480048 bytes) in /nas/content/live/oslokameraklub/wp-content/plugins/get-url-cron/geturlcron.php on line 1368


    It seem like the -1, – didn’t emptied, – the log.

    Geir

    Plugin Author berkux

    (@berkux)

    Hi Geir,
    ok, not good.
    Would you mind posting at
    https://jsoncontentimporter.freshdesk.com/widgets/feedback_widget/new?searchArea=no
    Via that I can provide you with a beta version trying to fix that.

    Thank you,
    Bernhard

    Plugin Author berkux

    (@berkux)

    Hi Geir,
    I worked on that:
    As a workarround this should held deleting the logfile:
    1. Set “Max. age of logentries” to -1 at “Basic Settings”
    2. Klick on “Show Logs”: This deletes the log file
    3. Manually execute a Cronjob at “Set Cronjobs”: This should work and create no logfile

    Do you have many cronjobs running very often? Then the logfile gets big fast…

    Bernhard

    • This reply was modified 2 months, 4 weeks ago by berkux.
    • This reply was modified 2 months, 4 weeks ago by berkux.
    Plugin Author berkux

    (@berkux)

    Version 1.5.2 further improves the handling of the log files. Additionally, “Plugin Check 1.1.0” has also been passed.

    Thread Starter geirarnesen

    (@geirarnesen)

    This last change seem to have done the trick. Now, – plugin is back up working again…. Now I can turn-off my raspberry pi which I used for triggering the urls as I have no control over crontab in the WP engine environment.

    Thanks.

    Geir

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.