I was using poormanscron 6.x.1.0 and it was find until I installed Boost module. This new module projected me to use latest version of poormanscron and when I installed, everything was white. I was not able to get into my admin page even. Also, update.php did not find my new installation.

I changed my system table's status to '0' for poormans cron and now when I could enter into my admin page but getting the error in all the pages;

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'poormanscron_run_cron_check_access' was given in /home/tbeez/public_html/includes/menu.inc on line 452.

Dont know whetehr it is a problem with poormans crn or I am making some mistake. Please help. Thnaks in advance.

Comments

dave reid’s picture

Status: Active » Postponed (maintainer needs more info)

You would need to run update.php because the new version includes JavaScript that calls a new path defined by the module. Because the menu hasn't been rebuilt yet (via update.php), it's throwing that error when using that menu callback.

You need to run update.php. If you're not able to run that, you have a much bigger problem with your site.

mukilank’s picture

I tried reinstalling again but my update.php could not rcognize the new module.

Boost module is looking for poormancron 6.x.2.x version and I am trying to use poormanscron-6.x-2.0-beta1.tar.gz or poormanscron-6.x-2.x-dev.tar.gz.

Am I using a right version?

Thanks for your reply.

mukilank’s picture

Solved the problem but not sure why update.php was not working fine.

My site is hosted in siteground and Update Status was not functioning properly. Not sure whether it took more time or never worked but made the cron job to fail. Now, disabled Update Status module, refreshed cache, add poorman, everything seems to be working fine.

dave reid’s picture

Status: Postponed (maintainer needs more info) » Fixed

Thanks for the update! Glad to know it's working for you.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.