Request letter for Cron Setup for Hosting System that does not allow manual configuration
Some hosting providers do not allow the user to implement cron jobs / scheduled tasks to configure FeedSync or the WP All Import Pro cron jobs.
Use the letter below to submit a support ticket
Hi Support,
We need your team to configure the following cron jobs/scheduled tasks for CUSTOMER_NAME.
SITE_URL
This site is currently in the final stages of development and nearly ready to launch and is located here:
STAGING_URL
---------------------------------
CRON JOBS to Configure
---------------------------------
NOTE: Disable all email notifications as they are not needed and we can check if they have worked from within WordPress
------------
#1 FeedSync
------------
Lightweight Processes ZIP/XML files.
-- See Help tab for alternative commands
Located here:
FEEDSYNC_URL
Schedule
Every 8 minutes each hour/day/week/month/year
Command
CRON_COMMAND
*/8 * * * *
------------
#2 WP ALL Import Pro - TRIGGER
------------
WordPress import plugin
-- This begins the import
Schedule
Once per hour at 10min past hour/day/week/month/year
Command
CRON_COMMAND
10 * * * *
------------
#3 WP ALL Import Pro - EXECUTION
------------
-- This imports a couple records each time to minimise server load
Schedule
Once every ~2/3/4 mins each hour/day/week/month/year
Command
CRON_COMMAND
*/2 * * * *
---------------------------------
WP ALL IMPORT Cron Scheduling Instructions.
---------------------------------
-- This is why one is required every 2/3 mins
------
Cron Scheduling
To schedule an import, you must create two cron jobs in your web hosting control panel. One cron job will be used to run the Trigger script, the other to run the Execution script.
Trigger Script
Every time you want to schedule the import, run the trigger script.
To schedule the import to run once every hour, run the trigger script every 24 hours. Most hosts require you to use “wget” to access a URL. Ask your host for details.
Example:
DETAILS ABOVE
------
Execution Script
The Execution script actually executes the import, once it has been triggered with the Trigger script.
It processes in iteration (only importing a few records each time it runs) to optimize server load. It is recommended you run the execution script every 2 minutes.
It also operates this way in case of unexpected crashes by your web host. If it crashes before the import is finished, the next run of the cron job two minutes later will continue it where it left off, ensuring reliability.
Example:
DETAILS ABOVE
Notes
Your web host may require you to use a command other than wget, although wget is most common. In this case, you must asking your web hosting provider for help.
See the documentation for more details.