[Plugin: Post Expirator] 1.6.1 not working
I tried the plugin v1.6.1 with 2 separate WP instances v3.4.2 with all plugins disabled to ensure they don’t affect the post expirator. It does not work on any instance I tried with.
I guess the issue regards the cron. I checked my ISP’s spec and here are their cron requirements (apologies for Google-trans):
Recurring scripting “Cron” is based on the programmed call appropriately named script, located in the root directory of your server in home.pl.
Time to execute a script can be strictly defined by time:
every five minutes,
every week (weekly)
each month (monthly)
a strictly specified time (accurate to 5 minutes).
What are the file extensions I use the CRON function?
Available upgrades for the CRON function is:
To use the CRON home.pl on the server?
To use the solution to the root account, put the script with the name of principle:
cron [hourly | daily | monthly | weekly]. [extension]
The exact hour of starts:
hourly – full hours *: 00,
daily – every day at 1:15,
weekly – on Saturday at 1:30,
monthly-first of each month at 1:45.
For example, the file “cron-daily.php” will run every day at 1:15, using the PHP interpreter.
IMPORTANT! You can not call script periodically with. Php3
Other examples of the use of CRON function:
File “cron-13.php” runs every day at 13:00 by PHP.
File “cron-04.php” starts at 04:00 by PHP.
File “cron-1545.php” will be performed daily at 15:45.
Maximum precision is 5 minutes – for example, will not work file called “cron-1546.php”.
cron-[xx] minutes. [extension] – where xx is the minute. Allowed values are – 5, 10, 15, 20, 30
File “cron-5min.php” will be performed every 5 minutes, starting with the publication of a file in the root directory of the server home.pl.
Good to know
Environment that causes recurring scripting is identical to the environment in which the scripts are run on virtual servers. In practice, this means that calling such a little different from the usual call after HTTP GET.
In order to protect yourself before calling cron file by any user, block access to it in the file. “Htaccess”. You can do this by typing in the contents of the file. “Htaccess” the following code:
: Location / cron-daily.php
Access deny all
File “. Htaccess” with content that will block calls CRON file should be placed in the root directory of the server. In the line that starts with the phrase “: Location” CRON define the file name to be locked before calling.
I used 1-hour option (not the 1-min interval, which is incompatible with my server. Is there anything I could do to fix it?
- The topic ‘[Plugin: Post Expirator] 1.6.1 not working’ is closed to new replies.