Programmed posts that are not published

Some time ago I had problems with the scheduled posts ( yesterday we talked about this matter ). I usually write as I have the day of inspiration and I do not always publish all the same day. Here for example, in WordPress Help, I usually schedule many posts to be able to always offer at least one trick or guide per day, then I also publish everything that is rabidly current.

 posts-programmed "title =" posts-programados "width = "500" height = "285" class = "aligncenter size-medium wp-image-3922" /> </a></p>
<p> Well, to what I was going, after <a href= the initial migration of May I verified that the programmed posts never finished publishing, when the time came that they had to come to light they began as an infinite loop in which every time the counter of time was up for the post in question to be published.

After a lot of research, I came up with the solution that, of course, had to do with something strange that happened in the migration, when I discovered it I shared it in the support forums of Mediatemple but today I have fallen in that I never mentioned it here, a big mistake that I'm going to solve now.

Bi in, then the issue is that it has something to do with the file ' wp-cron.php ' and the server configuration …


  1. Type the following command through SSH (of course, you must have access to your server by this means)

    If everything is fine you will see a message of "OK". But if there are problems you will see an ugly 404 error message in the terminal window. If you have this bad luck you should follow these steps …

  2. Open your file ' etc / hosts '
  3. See if the DNS you point to is not the DNS address of your domain (eg. : if the DNS of your domain is and the hosts file points to
  4. Change the wrong DNS in the file ' etc / hosts ' to the real DNS of your domain
  5. Check again if your file ' wp-cron.php ' works correctly by typing the same thing as before …

    If you get an "OK" you already have it

Also, of course, you you can find in the situation where you do not have access via SSH . In that case you can always ask the technical service of your accommodation to do this check, for that you pay no?

NOTICE : this publication is two years or more ago. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

Check if your blog is online or not • WordPress Help

There are times when the host where our blog goes down or there are errors in the database or in the DNS of the domain . Errors that can be repaired, but only if we notice on time or if someone notifies us in time of it. For our luck there is ServerMojo a great service that will check every certain state of our server. We can ask ServerMojo to monitor our database, or our DNS, or our server or even a specific page of our blog.

The service is quite simple and will notify us by mail, Twitter or IM if it detects that something is not working as it should, and so we can solve it more quickly.

Of course, there are also more options: BasicState Ezine Monitor ] Montastic and many more. It is only a question that you find your ideal service and begin to know the times that your server falls and leaves without access to all your visits …

Migrate WordPress to another server

Changing your site to a new accommodation can be a tedious process. You can compare it to change house or office . Fortunately, it is much faster than that. With these instructions you can migrate your website in a very short time minimizing the impact on your readers and search engines. Find out that will take you at most one day and even at the best one hour or less.

The List

Get ready. Make sure you have the following.

One or more of these things will change during migration:

  1. IP Address: the Internet address of your web hosting. If your blog does not change servers, it is quite likely that the IP will not change either.
  2. Domain name : . You may have acquired a new domain name. And maybe not. Now would be the perfect time for this type of change.
  3. Route : what comes out in the URL after the domain name, usually separated by a slash (/), or a sub-site, such as / blogs / yourname / ). Many blogs start as sub-sites in an existing domain, but eventually become their own sites, with their own domain.

Note how all of the above is currently. It also points the new addresses or elements as they will be after the change.

Do not forget the basics :

  1. If you change the web hosting IP address and access information for your new web hosting. Either by FTP or SSH.
  2. The management information of the database of your web hosting (s). Whether you use phpMyAdmin, a web hosting control panel, or command line, this information is crucial.

Do you have it? Ok, then we started. From now on you should not modify anything in your "old" blog. Do not accept more comments, pingbacks or trackbacks, do not publish more posts or upload more files. This can be easily controlled from your control panel.

Domain name preparation

Do this step only if you are going to keep your domain name ( ), but you blog will change your IP address (eg in a new hosting company).

To do this successfully you need to take control of your domain name. You manage this with your DNS provider (and this is a good time to learn how to manage your DNS by yourself). Well, here are the steps:

  1. Record your TTL (the time-to-live, which is usually between 3600 or 86400 seconds).
  2. Decrease the TTL to 5 minutes.
  3. Now we have to wait. If your TTL was 86400 seconds (1 day), wait one day. Sit and take something.

The WordPress settings  construction.jpg

Skip this step if you are not migrating to a new web hosting. Use your favorite FTP client to copy the WordPress files from your current hosting to the new hosting folder. All files mean all: uploaded files, plugins, everything in your WordPress folder. Make sure you keep the permissions of the files and folders while you move them – if, for example, the uploads folder had write permissions, moving it should result in a folder of uploaded files with write permissions on the server web of the destination accommodation. At this point, you may not yet have a domain name pointing to your domain, in this case you must use the IP address of the new hosting. Nothing happens.

The configuration of the database

Are you still here? Perfect.

  1. Using your favorite utility (usually phpMyAdmin) for database administration, create a new and empty one in the new hosting. If you are not going to change hosting do it anyway.
  2. Create a new username and password. Give the user enough privileges in the database.

Do not do more in this respect at the moment.

The transfer of contents

If your domain name and route are not going to change during the migration, skip this step

Now is the time to reconfigure the information in the database, so that your complete blog fits completely with your new URL. I recommend using WordPress AutoLink . You will use it to move all your posts automatically – replace all absolute URLs with references to the "slugs" (name of the URL). The result? Your posts will no longer point to old URLs. It greatly diminishes the possibility of broken links in your posts and comments, and will also facilitate the following steps. Try it out.

Normally this process is quite tedious since it involves editing the WordPress settings and all the hyperlinks in your posts, comments, plugin settings and blogroll. But there is a bombproof way to do it:

  1. Exports the database to a file. Using the database administration tool (usually phpMyAdmin) of your old hosting, export the entire database as a series of SQL statements.
  2. Download it to your computer.
  3. Open it in your favorite text editor
  4. Search for any match to the old address and change it to the new URL. All. You can try and use the automatic replacement of the editor (I do not recommend it) or do it one at a time and make sure you're changing.

You can even do it in the command interface of your operating system (Linux or Mac OS X ) with the following order cat blog.sql | sed 's | http: // oldaddress / | http: // newaddress | g'> newblog.sql – but it may be too much for you, if you do not deal with UNIX commands. The best thing is that you do it with your web editor or plain text. You may still have some adjustment but it will depend on whether your posts refer to absolute routes ( / route / to / some / post / ) instead of full URLs ( http: // tublog / route / to / post / ). In any case, your goal in this stage is to adjust the URLs in your content to point to the new place.

Oh, and to be sure, you should audit the changes using a tool that allows you to visualize the changes, be it the to be. Once you finish, send this modified SQL file to your newly created database in the new hosting

The domain change

There are two types of domain change:

  • From towards
  • The domain is the same but the IP address changes

Obviously, if the domain and the IP do not change you skip this step.

If the IP address (that is, Web hosting) changes

Make the DNS change. In essence, what you have to do is make your DNS point to the new hosting. This takes a while – during the DNS change many servers continue to access the old site. After the TTL expires (time-to-live, which you changed to 5 minutes), this will change and your new site will be available.

After making the change, increase the TTL to something reasonable (yes, 86400 seconds is reasonable). This will prevent a future DNS request storm.

If you change your domain name

just have your new domain name point to the IP address of the new Web host. That is all. If you were not aiming at anything, it will be a short time until your new site is active, but if it was already directed to another site you will have to wait until the TTL expires.

Final Steps

Have you done everything? Do DNS work? Ok, now:

  • Edit the famous file wp-config.php and enter the information in the database, just like you did the first time you created your first blog.
  • Enter the address of your blog in the browser.

Your blog should work.

Redirect 301: an important detail

At this point I will make a master suggestion: if you changed to the address of your blog (the route and / or the domain name) you should have the old address make permanent redirects from the old address to the new address.

This will not always be possible, since you can not control the web server configuration in the previous host, but It is important since both readers and search engines will be redirected to the new site. Oh, and remember to make redirects go to real pages. For example, if you had a post on the redirection should go directly to post / . Do not confuse your readers by redirecting them to the main page of your blog.

Tip: this is easily done through the configuration of the file .htaccess . And if you do not know or do not dare you can use some plugin like one of these two .

You got it!

NOTICE : this publication is from two years ago or plus. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you: