Updating feeds by cron requires some permissions. This isn't ideeal at all, especially if one is using poormanscron and the cron run may be from any arbitrary user. I have fixed this before by saving the global $user variable in a temp variable and user_load uid 0 in the cron hook and putting it back.

Comments

drumm’s picture

This is in contributions/for_review now:
4493.drumm.update-requires-user-permissions.patch

(loads user 1 not 0)

drumm’s picture

I moved the patch to the correct location having misread the convention.

Moshe gave me the goahead to commit it, but this can be done by only temporarily swapping out the uid for 1 because that is what user_access checks. I am going to make a new patch implemented that way and remove the access check in the cron hook as it will always evaluate to true.

drumm’s picture

Commited a patch

Anonymous’s picture