{"id":14081,"date":"2015-04-11T05:07:14","date_gmt":"2015-04-10T19:07:14","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=14081"},"modified":"2015-06-28T18:23:30","modified_gmt":"2015-06-28T08:23:30","slug":"wordpress-blog-sticky-post-crontab-curl-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/wordpress-blog-sticky-post-crontab-curl-tutorial\/","title":{"rendered":"WordPress Blog Sticky Post Crontab Curl Tutorial"},"content":{"rendered":"
\"WordPress<\/a>

WordPress Blog Sticky Post Crontab Curl Tutorial<\/p><\/div>\n

As you might have guessed from yesterday’s WordPress Blog Category List Primer Tutorial<\/a> as shown below, weeeeeee””’rrrrrreeee baaaaaaaccccccckkkk!!!<\/p>\n

You might also have guessed that we’d be talking about “WordPress Blog Sticky Posts”, particularly as it mentions it in the title … daaaaaaaaaarrrrrrrrnnnnnnnnn.<\/p>\n

But did you know that English sentences shouldn’t start with “but” … maaaaaaaaatttttttttteeeeeee (sorry to break into twaaaaaaaaangggggg).<\/p>\n

Seriously, though, WordPress, and probably other blog software products allow you to have “Sticky Posts” that stay in position, and only happen for a WordPress blog’s “landing page” scenario, which, in the case of our WordPress blog (subdomain) would be this landing page<\/a>. This “intelligence” can be found in a WordPress.org blog’s MySql “wp_options”<\/i> table and we are very graaaaaaateful today for the great advice regarding this that we got from this useful link<\/a> … taaaaaaaaaaa!<\/p>\n

Using that useful information we cranked up good ‘ol phpMyAdmin<\/i><\/a> (& read more here<\/a>) …<\/p>\n


\nSELECT wp_options.option_value FROM wp_options WHERE wp_options.option_name='sticky_posts';
\n<\/code><\/p>\n

… and got the result set …<\/p>\n


\na:2:{i:0;i:316;i:1;i:7666;}
\n<\/code><\/p>\n

… which tells me that both 316<\/a> and 7666<\/a> were “Sticky” at the time of running the query, and, yes, that was true.<\/p>\n

So, reckon we are not on a sticky wicket to say that we can now plan our next holiday<\/strike> put the queries as per yesterday’s software_posts.sql<\/a> and as above to have all the information we need to derive the SQL to update the database every now and then, for variety, to change that second “Sticky Post” to be … to be … to be or not to be … but we digress … to be another WordPress blog posting ID from that list of yesterday (which happened to be a list of WordPress blog posting IDs with category “Software” more than 8 days old).<\/p>\n

Do you get what we want to do now? Hopefully yes … and do you get why the 8 days? … that is so a “Recent Post” is not one of the WordPress blog posting IDs chosen, as to allow this to happen, and it did happen, would be a bit dumb.<\/p>\n

The SQL to update the MySql database goes something like … where we are making the new “Sticky Post” WordPress blog posting ID 10021 …<\/p>\n


\nUPDATE wp_options SET wp_options.option_value='a:2:{i:0;i:316;i:1;i:10021;}' WHERE wp_options.option_name='sticky_posts';
\n<\/code><\/p>\n

… so the derivation of 10021 is via a randomly selected category “Software” ID that is not 7666 and is older than 8 days.<\/p>\n

Okay we have three pieces of SQL and, ideally, we’d like them to run in the order …<\/p>\n

    \n
  1. software_posts.sql<\/a><\/li>\n
  2. SELECT wp_options.option_value FROM wp_options WHERE wp_options.option_name=’sticky_posts’;<\/li>\n
  3. UPDATE wp_options SET wp_options.option_value=’a:2:{i:0;i:316;i:1;i:10021;}’ WHERE wp_options.option_name=’sticky_posts’;<\/li>\n<\/ol>\n

    … where 10021 is up for grabs. So let’s put all this into some PHP code you could call sticky_post_list.php<\/a> and unit test via Linux command line (on the www.rjmprogramming.com.au domain web server) via the use of Curl<\/a> …<\/p>\n


    \ncurl http:\/\/www.rjmprogramming.com.au\/PHP\/sticky_post_list.php
    \n<\/code><\/p>\n

    … it works and it creates a new sticky_posts_list_new.php<\/a> each time, for verification purposes.<\/p>\n

    So, implementation wise we come back to all those choices of ways and means of making this happen, and we’ve decided on good ‘ol Crontab to do it with the “crontab<\/a> -l” relevant record entry …<\/p>\n


    \n13 *\/8 * * * curl http:\/\/www.rjmprogramming.com.au\/PHP\/sticky_post_list.php
    \n<\/code><\/p>\n

    … in other words, we do it every 8th<\/super> hour and do it at 13 minutes past.<\/p>\n

    Enjoy today’s tutorial<\/a> and just remember a change is as good as a holiday …<\/p>\n

    \nHey, Mac … you remember that plan our next holiday<\/strike> … well strike<\/strike> I mean unstrike that … the holiday’s back on!\n<\/p><\/blockquote>\n

    \n

    Previous relevant WordPress Blog Category List Primer Tutorial<\/a> is shown below.<\/p>\n

    \"WordPress<\/a>

    WordPress Blog Category List Primer Tutorial<\/p><\/div>\n

    You may well be aware that a WordPress blog, such as the one you are viewing, has a MySql database which is like its signature … well, more than a signature … basically most of its identity, because no matter what styling and theming you apply (and in any case some of the styling and theming ideas get stored in the database as well) the data behind the blog is what makes it what it is.<\/p>\n

    The WordPress PHP software has a “Fred and Ginger”<\/a> relationship with its MySql database. Who’s Fred, and who’s Ginger? … leave that for you.<\/p>\n

    But as with most decent dances you used to be able to tap somebody on the shoulder and ask for a changed arrangement … are you all rolling around on the floor yet? … the older of us have gone to the fridge to get a banana muffin I expect?!<\/p>\n

    Anyway, to cut a long story short, we are going to separate ourselves from WordPress PHP, and write our own, that sits outside and makes changes to the WordPress blog by adjusting the WordPress blog’s MySql database from this removed position. Okay, if you want to be dramatic … “in a backdoor way”. And what do you need to do this?<\/p>\n