How to migrate your WordPress hosting using Duplicator


This post is aimed at people who have a blog in WordPress and want to change it from one hosting to another. You may have taken this decision for many reasons: because your web hosting does not offer you good technical support, because it is expensive, either because it goes too slow or falls too often. Probably, you will ask: what can be done? How to change all the content in the process of server migration from a WordPress blog to another hosting?

In this article we will try to answer your questions. You will discover that it is very easy to do. You will not lose information during the process in which you move your blog from one hosting to another and you will be able to access without problems or worries. For this, we will use the plugin Duplicator . Although there are other plugins to make backup copies, sometimes they are not quite perfect to make a complete transfer of the blog and some things are lost along the way. Let's see in 4 simple steps how the process can be carried out.

  1. Make a backup with the Duplicator plugin

Before starting to make the smallest change, if you do not want to take any risk, what It corresponds now is to carry out a backup of the blog. Therefore, go to the control panel of your blog, enter your username and password, and first install the plugin.

  • Click on> Plugins> Add new> Duplicator 0.5.6> Install> Activate plugin [19659009] Next, click on "Create new" to create a duplicate package.
  • Finally, download the file "installer.php" on your desktop, as well as the package.

If you have followed these three steps, you will have a copy of your blog on your desktop, which we will use later

  1. Create a DB in your hosting

Now, if you are going to create a new web hosting account, You will have to do some things to move your WordPress blog here.

  • Enter the control panel of the new hosting you are going to.
  • Enter the database and MSQL part.
  • Make a new database.
  • Put a new user and password.

You must be very clear about what you want to do with your web domain. If you want to keep it in your old hosting, or maybe you prefer to pass it to your account in your new hosting. If you decide on the first, you must point the domain to the IP of the new server you have hired (get in touch with technical support to get it if you can not find it). If you buy a new domain in the domain registrar of the hosting, you will not have to do anything and everything will be much simpler.

You can also keep the domain, but send it from one server to another. Contact technical support if you have questions, that's what they are for. By the time you have your domain prepared in the control panel, you can continue with the next point.

  1. Upload your backup to your new hosting

Once you have made the backup, there is only that upload it to the new hosting to leave everything on your site. You can place it better by FTP using the free software Filezilla Client or you can also do it from the file manager that will be in the hosting panel.

If you decide to upload the file with Fillezilla Client, you need to know the minus three important data of your FTP account, that you will have created first from the control panel:

  • Server: you must write the name of your domain without the www
  • Username: write the same one that you have put on the panel control when doing your FTP.
  • Password: the same.

When you have written these three data, put them in the boxes, click on "fast connection" and you will be in your new hosting. That's where you have to upload the file installer.php .

  1. Restore the backup copy in the new hosting

Is all the above already? Then type substituting "yourdomainname" for your actual address. You will get a window with the information of the restoration assistant of the backup that you created before.

  • Deploy: you will see information of the hosting, user and password and the name of the bbdd.
  • Update: you will find the name of the old domain and the path where your blog was, as well as the new where it will be installed.
  • Test: the last point is to check if your blog works well, delete files and save the permanent links.

If everything is fine, you will have finished migrating your server to WordPress quickly and easily. Consider that sometimes the configuration of the DNS may take some time, maybe up to 48 hours. Many times it will happen much faster and your blog will be ready to be seen from the new hosting.

I trust that this article has helped you to make your hosting migration. For any questions you may have, leave us a comment here.

NOTICE : this publication is from two years ago or more. 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:

TimThumb abandoned

 abandonware "width =" 500 "height =" 500 "class =" aligncenter size-medium wp-image-76429 "srcset =" https : // 500w, 150w, https : // 800w "sizes =" (max-width: 500px) 100vw, 500px "/> </a></p>
<p> The famous <strong> clipping script images TimThumb </strong>massively used by themes and plugins, has been <strong> abandoned by its developer </strong>moving to the now famous list of <a href= abandonware .

Not lacking in guilt by different exploits that this script has suffered great on the other hand, the author has decided to abandon its development and support, and recommends developers of plugins and themes that stop using it .

] If you use algu n topic or plugin that uses it " encourages " to its developer that use some alternative method because if already until now TimThumb was vulnerable not to mention once abandoned the development and updates of it.

The best alternative to TimThumb is, of course, the native support of WordPress featured images which are gradually adopting mostly theme developers, as well as other alternative solutions to TimThumb .

A very interesting one is the following code which does the same thing as TimThumb with images from your server (does not work with external images or hotlinked ) but without its vulnerabilities:

; Other possible alternatives are the Photon module from JetPack, which also dynamically resizes images or the plugin BFI Thumb .

What is clear is that you have to leave to use TimThumb now, yes or yes.

NOTICE : this publication is from two years ago or more. 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:

User mentions in bbPress

The plugin for creating forums, which integrates wonderfully with BuddyPress does not inherit this great functionality at the moment but, as long as it does not join the bbPress kernel or plugins appear that facilitate it, ] can be easily added by a simple function .

You just have to add the following code to the file bp-custom.php of the BuddyPress installation:

] Once you save the changes you will be able to use those nice and practical mentions to users also in the forums of your social network created with BuddyPress.

Guest articles without registration • WordPress Help

If you have a blog and you allow guest articles it's sometimes a hassle to ask users to sign up to do so.

Also, you have to customize user profiles, control which categories they can use publish, review, etc. But the part that complicates the issue is clearly the registry, because you lose possible interesting collaborations of users who do not know WordPress.

Fortunately, this has an easy solution, because you can use plugins like Really simple guest post .

Once active you just have to create a page (or entry) and, in addition to the text you want to include, add the short code ( shortcode ) below:

When you post the changes on the page or entry in the place of shortcode will appear a simple form with the necessary basics for the sending of entries of your readers.

The entry will not be published directly but will remain in pending status, waiting for your approval . Simple and effective.

Of course, there are much more advanced systems, but this is simple, functional and easy to manage, do not you think?

Choose language of entries in WordPress • WordPress Help

 wordpress-post-language-logo "width =" 525 "height =" 525 "class =" aligncenter size-full wp-image- 76375 "srcset =" 525w, 09 / wordpress-post-language-logo-150x150.png 150w, 500w "sizes =" ( max-width: 525px) 100vw, 525px "/> </p>
<p> With the recent changes in the <strong> internationalization in WordPress </strong>that <a href= since WordPress 4.0 already allows to choose language since installation and changes later in the general settings, there is an initiative for to translate this functionality also to each publication .

WordPress is mainly downloaded in English, with huge difference, but there are languages ​​like Chinese, German or Spanish that suppose u a huge installed base and it seems sensible to incorporate the concept of internationalization to every aspect of the system.

Currently there is no possibility of specifying the language in which a publication is written an element that once incorporated into the WordPress core and adopted by developers, would allow to personalize and define more and better the target audience of each entry or page, making WordPress a complete multilanguage publishing system without the need for external applications, practically all incompatible with each other.

The idea is that WordPress, among the current publishing options, allows to define the language in which each entry is written, something that could visually be solved in this way:

It would be a new field in which to specify in which language the entry is written, pu Logically, this type of change will require the incorporation of WordPress functions that, as of today, are not available, and could be the following:

Input language values ​​

] They should be accessible as template tags:

  • the_post_language ()
  • get_the_post_language ()

And possibly they would affect some values ​​like the following:

  • get_bloginfo ('language')
  • get_bloginfo ('text -direction ')
  • (and consequently to language_attributes () )

Or it could be implemented by a new attribute in each entry, similar to post_class () : [19659003] Something like this:

Y , could, in addition, differentiate microformats .

Finally, it is probably not a good idea to have this input language functionality active by default. It could be activated by a constant to include or enable in the configuration files wp-config.php so for example: define ('WP_POST_LANGUAGE', true) or, perhaps better , using a filter of this type: add_filter ('post_language', $ locale)
or even by a box in the general settings, inactive by default.

Logically, all this will require, as with any new function, that the developers incorporate it in their future themes and plugins, for a total compatibility and use of the feature, as with any other function such as the highlighted entries or the input formats.

If you dare , you can try a first version at the early stage of development on the same page of the project, or from the following link:

[download id=”76379″]

In any case it is only a proposal, which requires development through code and acceptance n of the idea by the community so that, if possible, be available in a future version of WordPress .

Personally I think a great, great idea. Do you agree?

NOTICE : this publication is from two years ago or more. 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:

BuddyPress 2.1 incorporates important changes • WordPress Help

Just released version 2.1 of BuddyPress, with few but sufficient and important improvements.

Soon you will guess which of news is the most important for me, but these are all:

Of course, by far, in my view the best are the improvements in translations, in sync with WordPress 4.0 and for you?

Do not do it! but … this is how emails are exported from comments • WordPress Help

 image of arroba with padlock

This is one of those tricks that one doubts before sharing, because has more danger than one pump case but as the responsibility is yours, and there are situations where you may need something like that, for ethical reasons of course, for me not to be left.

And, I repeat, do not do it ! and if you use it before it notifies your visitors that your emails will be archived, otherwise you will be not complying with a basic data protection okay?

Ea, well, come on to it, because the explanation and danger is longer than to get it.

You just have to install the plugin Export emails . Once you have it active you go through the new menu located in "Tools -> Export emails."

There you will see two boxes, well, without anesthesia. In the first are all emails of registered users in your WordPress, extracted from the user table of your database, and in the second the emails of all visitors who have ever commented , in this case extracted from the table comments also from the database.

 export-emails "width =" 520 "height =" 348 "class =" alignnone size-full wp-image-76359 "srcset =" 520w, 09 / export-emails-500x334.png 500w "sizes =" (max-width: 520px) 100vw, 520px "/> </p>
<p> That's it, now what you do with those lists, which you can copy and paste where you want ( flat text, spreadsheet, etc.), it's up to you, you know, <a href= a great power carries a great responsibility

The fault of telling you this has it WPBeginner

NOTICE : this p Publication is from two years ago or more. 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:

How to customize the related JetPack entries

 Related entries jetpack

Ok there are many plugins with which to show related entries for years, you can even show related entries without plugin but it is also clear that JetPack is becoming a standard and many people take advantage of what they have before looking for other alternatives, even if they are better .

The problem with the module related entries of JetPack is that, by default, it does not allow virtually any customization, or location, or aspect, is as it is, whether you like it or not.

 Related entries jetpack settings

But this is not entirely true, as there are customizations that can be made to the related input module of JetPack, through codes offered by developers which you can include go in a specific plugin or in the file functions.php of the active topic, so let's see them.

Change the number of related entries that are displayed

default, the module of related entries adds 3 entries as much. You can change this number using the filter jetpack_relatedposts_filter_options it's done like this:

In this example 6 related entries will be displayed

Move related entries to the top of the content

Related entries are placed before the comments s, and this is not always the best option. If you want you can change this behavior by default and move them to the top above the content of the entry with the filter jetpack_relatedposts_filter_options like this:

Insert Related entries in the content

Another interesting option may be to display the related entries in any part of your c

Doing so is as simple as including the shortcode right where you want it to appear in your post, without leaving the WordPress editor, this:
[jetpack-related-posts] [19659004] The best thing of all is that if you insert this shortcode the entries related to the bottom of the entry do not leave, so to speak, it "kills" the behavior by default.

Put the related entries anywhere on the subject to choose

If you want to control exactly where the related entries will be displayed, and you do not want to put them on top or want to be putting shortcodes each time, nothing better than making a modification permanent.

The first thing is to add the following code to your plugin functions or functions.php with which you delete the related entries from the default site:

You can now display the related entries in two ways, or by using the shortcode from the previous trick, which is not practical, or add the following code to the part of the loop of your active theme (usually in the loop of the file single.php ) where you want to display the related JetPack entries:

Change the "Related" text that exits on the related entries

Another simple trick. This time we change the default text, "Related", for something like "Maybe you're interested too …"

Replace one of the related entries with a result defined by you, a specific entry

What you need to do is indicate the ID of the entry that we want to appear always, whether related or not.

In this example code we use the entry ID 2345 which, of course, you must change to the one you want.

Exclude specific entries so that they do not appear in the relationship nadas

A variation of the above would be not to include, but exclude specific entries, so that they never appear in the related ones.

Again, the numbers in the code example are input IDs that we want to exclude:

Exclude whole categories so that their entries do not appear in related ones

It happens many times that you have some generic category that, to include keywords of all a, often appear in the related entries, and you would prefer to exclude them.

Nothing, in the following example we managed to exclude the category with the slug "things-mias":

That no related entries appear in specific entries

If you know of specific entries where you do not want readers to be distracted by these attractive related entries you can make them not appear simply by using the following trick, where we put the ticket IDs where there will be no related list: [19659301] // No related entries in the following entries
function jetpackme_no_related_posts ($ options) {
    if (is_single (array (17, 19, 1, 11))) {
        $ options [‘enabled’] = false;
    return $ options;
add_filter ('jetpack_relatedposts_filter_options', 'jetpackme_no_related_posts');

// No related entries in the following entries

function jetpackme_no_related_posts ( $ options ) {

if ( is_single ( array ( 17 19 1 11 ) [19659013]) ) {

$ options [ 'enabled' ] = false ;


return $ options ; ]


add_fi lter ( 'jetpack_relatedposts_filter_options' 'jetpackme_no_related_posts' ) ;

You can also use a lot of conditional tags on the line with the array is_single .

Include pages in the results of related entries

If you add Next to your functions plugin you will also search related results between the pages you have, not just entries.

For Of course, all this you can do if you have a full and free WordPress, not in services like

Well, what do you think ?, are a lot of good tricks No?

Well hala, you have to share yours! . If you know any more tell us in the comments.

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: