cron.php permissions after every update

[webmaster305]

Do we always have to change permissions of cron.php to 777 after each update?

[twhiting9275]

you should be able to just run php -q /path/to/cron.php

Now, if you're using the piping method (not pop import, but pipe forwarders), then yes, you do, at least with cPanel, due to the mess that is how cPanel handles things

[webmaster305]

Ok got it. Yes I am using cpanel with the piping method. I forgot to change permissions after my last update and had no email working for a couple of days until I ran into the solution on some page. This point should really be highlighted in the upgrade tutorial page though.

thanks

[WHMCS ChrisD]

Ok got it. Yes I am using cpanel with the piping method. I forgot to change permissions after my last update and had no email working for a couple of days until I ran into the solution on some page. This point should really be highlighted in the upgrade tutorial page though.

thanks

 

We generally recommend 755 for the pipe.php files, it should function on those permissions

 

I look into adding a cron note to the upgrade documentation

[WHMCS John]

Hi,

Thanks for the suggestion. I have updated our documentation to remind upgraders to check file permissions afterwards:

 

http://docs.whmcs.com/Upgrading#For_a_Full_Release_Version

http://docs.whmcs.com/Automatic_Updater#Performing_an_Update