After creating the first account, I got a page with a warning at the top about some error. Upon checking the log, it turned out to be the "cron hasn't run" warning.

I don't know what triggers that warning, but it would be a better initial experience if it were suppressed upon startup. Perhaps it would work to check how often the admin account has logged in.

Comments

danbh’s picture

danbh commented
Priority: Normal » Minor

The CVS version does just what you have requested. I am setting this to minor priority.

ajk’s picture

ajk commented
Status: Active » Closed (works as designed)

I think it better to remind an admin that they have not set-up cron from the outset is better than let them believe all is well and then suddenly something goes wrong later (which often results in email/support posts saying "everything worked then this suddenly happened without changing anything").

Perhaps it just needs to eb documented as normal. Drupal-5 docs regarding installation, as yet, haven't even been published and I suspect they'll be updated given the major change in the admin UI.

Gary Feldman’s picture

Gary Feldman commented

danbh said:

The CVS version does just what you have requested. I am setting this to minor priority.

Does this mean the status should be set to Fixed (and not by design)?

AjK said:

I think it better to remind an admin that they have not set-up cron from the outset is better than let them believe all is well and then suddenly something goes wrong later (which often results in email/support posts saying "everything worked then this suddenly happened without changing anything").

This isn't a reminder. It can't be a reminder until the user gets told to do it in the first place. And, as far as I know, it's also not an indication that cron isn't set up, only that it hasn't run yet.

In this case, what will happen instead will be email/support posts saying "I did everything as instructed and got this error."

Perhaps it just needs to eb documented as normal. Drupal-5 docs regarding installation, as yet, haven't even been published and I suspect they'll be updated given the major change in the admin UI.

This is a classic example of trying to fix a usability problem with more documentation. That's not the way to solve usability problems.

RobRoy’s picture

RobRoy commented
Status: Closed (works as designed) » Active

I think this is still an active issue in HEAD, albeit very minor. The issue is that the cron error comes up the first time you visit your admin page saying cron is not configured, when it actually could be already set up to run every hour.

The message currently says "One or more problems were detected with your Drupal installation. Check the status report for more information....Cron has not run. It appears cron jobs have not been setup on your system. Please check the help pages for configuring cron jobs. You can run cron manually."

We could improve the message a bit, so it doesn't assume that cron is not properly setup even if it is AND doesn't seem so harsh as this should not be called a problem with this Drupal installation. (There is no error message if you run cron once every 6 months.)

Gurpartap Singh’s picture

Gurpartap Singh commented
Category: bug » feature
Priority: Minor » Normal

Would vote for auto first time cron run, set a message, cron ran successfully, else error report. Something like that makes intelligence sensee, but needs an intelligent guy to comeup with this too. ;)

Please change issue states if necessary.

RobRoy’s picture

RobRoy commented
Version: 5.0-beta1 » 6.x-dev

Moving this to 6.x.

Gurpartap Singh’s picture

Gurpartap Singh commented
Status: Active » Fixed

Fixed in 6.x

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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