When I was trying to migrate my site and export the database I realised that the cache_form field is enormous. According to suggestions I have found online the proper way to solve this is to run cron. So I try to run cron by going to the admin/config/system/cron page, and in there it said that cron was last run 3 weeks ago.

When I press run cron or when I visit the link with the cron key provided in that admin/config/system/cron page, they have both led me to user/0/edit instead of running cron. I did a quick search among the files I have made changes to in the site directory in these three weeks and none of them are leading to user/uid/edit. I wonder what else can I do to solve this properly?


  • thanks @arpitr , but i have checked all the page/files i have made changes in and none of them are leading to ('user/'.$GLOBALS['user']->uid.'/edit'), so I am not sure what else can i do – Jessica Sep 18 '15 at 7:01
  • do you have custom cron jobs running? You check the codes for custom implementation of hook_cron – arpitr Sep 18 '15 at 7:02
  • @arpitr I just checked and no custom cron jobs are running other than some regular ones included in modules like backup and migrate or capatcha – Jessica Sep 18 '15 at 7:10
  • Check this exactly the problem you are facing: drupal.stackexchange.com/questions/25025/… – jas Sep 18 '15 at 7:12

I think your not logged in, that's why going to " user/0/edit " path because you have not permission to run cron. Please check it.

| improve this answer | |
  • No, cron.php doesn't check you are logged in; in fact, in most cases it runs from tools that run in automatic. – kiamlaluno Sep 18 '15 at 7:01
  • Yes, and I am also the logged in with the only account with administrative rights in the site so it should not be the cause of the problem – Jessica Sep 18 '15 at 7:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.