poormans cron not running after update on 17 jan 2010, there is a 'page not found' warning in the logs:

Type: page not found
Lokatie: http://fqdn/poormanscron/?q=run-cron-check
Message: run-cron-check
Weight: warning

This is with ?q= added to the url in the poormans.js script, as suggested in other issues:
> $.get(Drupal.settings.cron.basePath + '/?q=run-cron-check');

If I leave the ?q= out the url, the message becomes:
Type: page not found
Lokatie: http://fqdn/poormanscron/run-cron-check
Message: poormanscron/run-cron-check
Weight: warning

The poormanscron module contains:

Looking for run-cron-check, results in:
poormanscron.js: $.get(Drupal.settings.cron.basePath + '/run-cron-check');
poormanscron.js.org: $.get(Drupal.settings.cron.basePath + '/run-cron-check');
poormanscron.module: $items['poormanscron/run-cron-check'] = array(
poormanscron.test: $this->drupalGet('poormanscron/run-cron-check');
poormanscron.test: $this->drupalGet('poormanscron/run-cron-check');
poormanscron.test: $this->drupalGet('poormanscron/run-cron-check');

I use clean urls, like; http://fqdn/admin/settings/poormanscron

What to do, to make poormanscron working again?


hawkdrupal’s picture

Same problem with 2.2. It used to run, but now I get "page not found" instead. No cron triggering...

Perhaps there's a path problem -- maybe a redirect needed to assure poormanscron is always found? If so, what should the redirect be -- unclear since it used to work without anything explicit.

HOWEVER -- perhaps the problem is that 2.2 is not just running as a script, it is reacting in a way that causes the browser to think a page should be displayed, but is "not found"?

I wonder because DOMAIN/poormanscron/run-cron-check seems to work. It yields "false", not sure if that's good, but at least the "check" script is found. So either the problem is that the default script is behaving differently, or it's not being found reliably.

Dave Reid’s picture

This is with ?q= added to the url in the poormans.js script, as suggested in other issues:
> $.get(Drupal.settings.cron.basePath + '/?q=run-cron-check');

Where was this recommended with the 2.x version?

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)
jvieille’s picture

Same problem.
I have a multi-site install, only one has this problem.
I tried to uninstall and reinstall it without success

The link for running cron manually is
the page non found it looks for is http://www.controlchainmanagement.org/node/1000
Enable/disable cleanurl does not affect this.

trying to run cron from wbesite/cron.php gives the same: works on all sites but this one.
So this might not be a problem from poormanscron

I solved the issue by emptying search_dataset and search_index tables

wapnik’s picture

Using poormanscron and search404 i've ran into the same issue. Don't know why and how. Disabling (after that running cron) and enabling search404 back magically solved the problem.

1timer’s picture


ikeigenwijs’s picture

same issue

Type page not found
Datum donderdag, 3 maart, 2011 - 03:01
Gebruiker Anonymous
Locatie http://www.revaki.ugent.be/?q=nl/poormanscron
Bericht poormanscron
Zwaarte waarschuwing

BigMike’s picture

Drupal Core 6.22
Poormanscron 6.x-2.2

I just discovered my site is also experiencing this issue. The suggestion of #5 to disable Search 404, Run Cron, enable Search 404, did not work for me.

When I view the source file of my site, I find this:

"cron": { "basePath": "/poormanscron", "runNext": 1313805685 }

which is located in the page's HEAD region beneath the Poormanscron js call, like this:

<script type="text/javascript" src="/sites/all/modules/poormanscron/poormanscron.js?m"></script>
<script type="text/javascript">
jQuery.extend(Drupal.settings, { "basePath": "/", "...............................................},

"cron": { "basePath": "/poormanscron", "runNext": 1313805685 },


What if we used a URL Redirect (admin/build/path-redirect) and just redirect /poormanscron to the path /admin/reports/status/run-cron ? This would solve the 404 Page Not Found error at least

But I'm worried if it will call cron by mistake when a bot is crawling around or something fluke occurrence.

What do you guys think? Would a path redirect to the cron URL be a safe temporary "fix" ?