Tagged: autoblogging Toggle Comment Threads | Keyboard Shortcuts

  • Jay Versluis 10:52 am on February 12, 2009 Permalink | Reply
    Tags: autoblogging, , , , , ,   

    Categories: Linux ( 96 )

    How to setup a Cron Job in Linux and Plesk 

    Wouldn’t it be great if something could be triggered even when you’re not around? Say once an hour, once a day, once a week or whenever you like in predetermined intervals?

    Then you want to do this with what’s known as a Cron Job, or Scheduled Task.

    Unfortunately, this is a bit beyond what WordPress can do, and it means getting down to the nitty gritty of the internal workings  of your server (after all, that’s where WordPress lives). Bear with me here, I’ll try my best to explain and show solutions.

    I’m using a Cron Job with Manu Flury’s excellent Photo Q Plugin. It posts one of my pictures over at http://www.versluis.com every so many hours. But for this to work properly, both the WordPress Plugin and my (Linux) server need to be setup correctly.

    Some WordPress Plugins (like Rob Felty’s Postie or Charles Johnson’s Feed WordPress) have similar functionality built in, but they rely on a visitor coming to your site at predetermined intervals. That’s not something you can control really. In most cases it works reliable enough for these plugins to work, however many others just don’t have that functionality, or require more accurate control. That’s where your Cron Job comes in.

    So what on earth is a Cron Job?

    In a nutshell, it’s a task that’s triggered at predetermined intervals. But it’s a bit like sitting in front of a Linux Prompt on your SSH connection, and all you have at your displosal is a keyboard with a black screen and white text to type in. What’s worse, your server doesn’t speak “WordPress”, or PHP for that matter. So all you can do really is to give him Linux commands.

    In all likelyhood, you probably want to call a PHP file so that WordPress does something for you (such as check if it’s time for a new post, or maybe a database backup). And you can’t just tell Linux to go to that file, becasue it wouldn’t know what to do with it. I’ve tried this without success many times over (they nearly put me in a mental institution, seriously… I can assure you I’m much better now though).

    So you need to find a command that calls your PHP file as if it were a browser. Lucky for us, the command “wget” will do the trick.

    Wget is really designed for downloading a file to your server, but it’ll work fine for triggering a PHP file, just as a browser would do. The command for calling the Photo Q file for example looks like this:

    /usr/bin/wget -O - -q -t 1 http://www.yourdomain.com/wimpq-cronpost.php

    Confused? Don’t be! Let me explain:

    • “/usr/bin/wget” tells the server where the wget command is (it’s a path to a file if you hadn’t guessed)
    • “-O – -q -t -1” are some random parameters, let’s not concern ourselves with those right now (if you really want to find out, type in “wget –help” at your SSH prompt)
    • http://www.yourdomain.com/wimpq-cronpost.php” is the actual file you want to call, just like what you’d type into your browser

    Now that we know how to call upon a PHP file from our command prompt, we need to tell our server to do this without us being there, and at what times he needs to do this. He’ll be more than happy to oblige, after all, that’s what he was designed to do.

    How to setup a Cron Job in Plesk

    I’ll focus on how to do this in Plesk 9 here, which refers to it as Scheduled Tasks (earlier versions of Plesk call it Crontab).

    Here’s how you get there:

    • from the main menu on the left, select HOME
    • select DOMAINS
    • select the DOMAIN you want to run this task on
    • under Additional Tools, select SCHEDULED TASKS
    • choose the SYSTEM USER you would like this task to be run as
    • select SCHEDULE NEW TASK

    OK, this was complicated enough to figure out – now comes the part nobody ever really talks about. It’s hard to explain, so please bear with me if I’m not making a whole lot of sense at first. In essence, you’re telling your server WHEN to do something, followed by WHAT to do.

    • Each field requires an entry. Don’t leave them blank.
    • The first tick box is to “switch on” the task. That’s what you want, unless you want to suspend the task. Tick it for now.
    • Now tell your server WHEN your task shall be run.
    • a “*” (i.e. star or asterisk) means “every”. So a star in minute would run the task “every minute”, likewise for hours and days of the month
    • You can also create the command “*/5” if you want your task run every 5 hours, every 5 days, every 5 minutes – you get the drift
    • Alternatively, put in the specific date (i.e. “Monday” and “17” for Monday at 5pm)

    After all that, you’re left with one last line, which is the actual command or task you’d like to be run.

    Like I explained above, for a PHP file to be called, use the wget command like so:

    /usr/bin/wget -O - -q -t 1 http://www.yourdomain.com/wimpq-cronpost.php

    Obviously change the path to your file, including “http://”

    Click OK on the bottom and your task should be setup. No need to reboot anything.

    If at any time you feel you want to amend the task, you can do so by just modifying the parameters, or uncheck the “run task” tickbox to suspend the task completely.

    If you want to know even MORE about Cron Jobs, check this out:

    http://www.hingham-ma.com/sendstudionx/admin/resources/tutorials/cron_intro.html

    Good Luck, and have fun 😉





     
    • Brian 5:05 pm on February 14, 2011 Permalink | Reply

      This post was not very helpful. The title is “How to setup a Cron Job *in WordPress*”. This does not seem to be any different than setting up a cron for any other PHP script, other than you’re using wget, rather than PHP directly. The title leads you to believe you explain how to setup your .php file to use pieces of WordPress and $wpdb, but your post contains no such information.

      For anyone looking to do this, all you need to do is include the /wp-load.php file in your cron file and you will have you DB Config and WPDB Class.

      • Jay Versluis 5:46 pm on February 14, 2011 Permalink | Reply

        Hi Brian,

        I’m very sorry you didn’t find the info useful – and reading back over the article I can understand why: the title is indeed misleading. I have changed it to “How to setup a cron job” because that’s what it’s about – nothing to do with WordPress.

        Thanks for contributing the wp-load.php tip – I’ll check it out!

        • Sandy Nerja 6:45 pm on December 6, 2011 Permalink | Reply

          My website takes xml feeds from local estate agents, and imports their properties to display on my holiday accommodation website. The whole thing is written in wordpress, and up to now I have been manually triggering the script that imports the rental properties from the agents sites.

          Finally I have got round to automating the process and the missing link was the wp-load.php. Use it like this at the start of your script:

          require( ‘wp-load.php’ );

          This assumes your script is in the same folder as wp-load and from then on your script acts like it has been called from WordPress.

          I hope this is useful to someone else.

    • Pranny 10:15 pm on August 8, 2011 Permalink | Reply

      That’s really helpful for me !

    • Jonas 6:43 pm on November 10, 2011 Permalink | Reply

      Thanks for the article!

      How do you prevent from someone triggering the cron job by just visiting http://www.yourdomain.com/wimpq-cronpost.php ? Is there a way to make sure only the server can trigger the task?

      • Jay Versluis 3:33 pm on November 17, 2011 Permalink | Reply

        Hmmm… good question. Since this is a public file it needs to be triggered via http. However, if you move the wimpq-cronpost.php file to somewhere above public level you should be able to trigger it via PHP from the command line queue for example – but I don’t know what the implications of the PhotoQ Plugin will be. I believe the developer said it needs to be in the root folder.

        I suppose it doesn’t really matter if you (or someone else) triggers the file more often than it needs to be called since the actual time in between automatic posts is determined via the Plugin Settings. Say you call this file every 5 minutes, but you setup PhotoQ to only post a new picture once every hour, then it will only post it once every hour.

    • Roy M J 8:37 am on January 31, 2012 Permalink | Reply

      Hi,

      I am using a plesk panel with godaddy and i cannot find how to set up a cron job. What i would like to know is whether wordpress has any plugins or set-up a cron job.

      Many thanks

      Roy M J

      • Jay Versluis 10:43 am on January 31, 2012 Permalink | Reply

        Hi Roy,

        WordPress has a built-in cron function which plugin developers can use. This however relies on somebody visiting your site regularly so it can appear to be unreliable. They do a good job for internal functions, but you can’t easily trigger a script without writing a plugin.

        Plesk calls Cron Jobs “Scheduled Tasks”, you can find those under Tools and Settings (in Hosting Provider View) or under Websites and Domains – Advanced (in Power User View).

    • taipres 2:27 am on February 14, 2012 Permalink | Reply

      The way you prevent a user from triggering your cron php script early is simply ignore all IP’s/Hosts besides your servers.

      if (getenv(HTTP_X_FORWARDED_FOR)) {
      $ipaddress = getenv(HTTP_X_FORWARDED_FOR);
      } else {
      $ipaddress = getenv(REMOTE_ADDR); }

      if($ipaddress != “1.1.1.1”){
      //do nothing
      }

      I use it on my site http://cheapvpsdeals.info for various things.

      • Jay Versluis 4:22 pm on February 16, 2012 Permalink | Reply

        Superb tip, thank you so much for sharing this. It’ll certainly come in handy 😉

    • nSathees 9:24 pm on February 20, 2012 Permalink | Reply

      @Brian: Hammered the nail on the head! Thanks for that wp_load point! That’s all I needed to know.

    • nSathees 9:33 pm on February 20, 2012 Permalink | Reply

      just a thought!

      what if I setup a php file with
      header(Location:’http://example.com’) which is my WordPress setup
      and trigger that php page via corn job.

      Would that work?

    • David Feldt 7:47 pm on September 5, 2012 Permalink | Reply

      Very useful – thanks!

  • Jay Versluis 4:20 pm on February 9, 2009 Permalink | Reply
    Tags: autoblogging, , , , , , ,   

    Categories: Domains and Hosting ( 4 )

    What is a CRON Job? 

    Although I’ve been dealing with webshoting and webdesign since 1995, it took me a whilw to figure this one out. If you’re used to shared shosting packages, it’s likely that you’ve never come in contact with this. Hence, this article is aimed at people who don’t know what it is.

    As explained in Wikipedia:

    Cron is the name of a program that enables unix users to execute commands or scripts (groups of commands) automatically at a specified time/date. It is normally used for sys admin commands, like makewhatis, which builds a search database for the man -k command, or for running a backup script, but can be used for anything. A common use for it today is connecting to the internet and downloading your email.

    So a cronjob is a scheduled action, which is executed by and on your web server. WordPress itself doesn’t do this for you. It’s like having a monkey sitting at a command prompt, typing something in every minute/hour/day – in regular intervals – you get the drift.

    In order to setup this automatic execution, you need to be in control of your own dedicated or virtual server. If you’re on shared a shared hosting plain, you can ask your provider to setup a cron job for you. Just tell them “I want (this particular file in this particular directory) executed every Thursday evening at 9”. Otherwise, use your own administrative panel (like Plesk or Webmin) to set this up.

    Want to know how? Read the following article: How to setup a Cron Job?





     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel