You are using phpFox version earlier than 4.7.0? Please refer instruction for this article here.

Requires: phpFox 4.7.0+

  • The following tutorial is a basic guide. All hosts have different setups. It could be that the path doesn't work for your server configuration. In that case, please contact your host for the proper path.
  • If your site hasn't been set up SSL, please use the URL with HTTP. In this article, we assume that the site has been set up SSL and all URLs will be used HTTPS

Cron jobs system of phpFox is required the site admin have to set it up manually. Cron jobs of phpFox are used for some core features such as Groups converting, Groups notifications, Downgrade Expired Subscribers... So, it is necessary to set up Cron jobs system to make sure that the phpFox site can work well as design.  Below is some instructions to help the admin can set up the phpFox cron job system easily.

The first step to set up new cron jobs system is getting the URL for cronjob of your phpFox site

 1. Log into AdminCP, and select Cronjob under Settings menu.
Token is like the password for your cronjob, you have to have the correct token on cronjob URL so you can execute the cronjob. Here you can set up the token for yourself, enter any phrase you want to set as token and hit Save Changes

2. You now will obtain your site's cronjob URL with a pre-defined token from the first step.


The Cron URL with token will be in format: https://<your-domain>/cron.php?token=<your-defined-token>

Copy the URL.
Next step, we need to configure Cron job on the server. There are several ways to configure Cron job, depend on your web server environment.


Via Web Hosting Control Panel

 cPanel





DirectAdmin

Set up with Command line (Linux server)

$ > crontab -e
*/10 * * * * curl -s https://<your-domain>/cron.php?token=<your-defined-token>

Set up on Window Server

Create a schedule task to execute the command "wget https://<your-domain>/cron.php?token=<your-defined-token>
(https://<your-domain>/cron.php?token=<your-defined-token> is the URL we received in first part)