Comment créer facilement un site de staging pour WordPress (étape par étape)

205 commentairesLaisser une réponse

1. Syed Balkhi says

   Mai 8, 2024 à 2:24 pm

   Hey WPBeginner readers,
   Did you know you can win exciting prizes by commenting on WPBeginner?
   Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
   You can get more details about the contest from here.
   Start sharing your thoughts below to stand a chance to win!

2. Lynda Joy says

   Mar 11, 2016 à 7:05 am

   Hi,

   I just did the first five or so steps of this, and then got lost at « upload your WordPress content to. So now I have completely messed up my site and I would like to know how to undo what I have done.

   Thanks.
   – Lynda

   Répondre

3. Rachel says

   Jan 13, 2016 à 6:33 am

   Thanks so much for this – I am very much a beginner but trying to figure out how to do these things myself so I can launch a new design by first using a test site in order to get it right. I have managed to follow your instructions perfectly until this part:

   « After copying your database, you need to copy your WordPress files, plugins, themes, and uploads. First download a fresh copy of WordPress from WordPress.org. Upload the contents of WordPress to your staging site. Note, do not run the WordPress install yet »

   Can you please advise as to how this is done or direct me to another instruction article? I can’t seem to find out how to do it otherwise. Many many thanks in advance

   Répondre

4. Sanket D. says

   Déc 10, 2015 à 12:41 pm

   So I’ve managed to create my staging environment successfully — I’ve all my media, themes, plugins, everything else properly transferred. However, I’d made some changes to my theme (not through any codes, but through the theme’s inbuilt settings — basic stuff like a custom logo (which I can see in my media library), theme color, homepage layout, etc. These changes are the only thing that for some reason are missing from my staging site. Anybody knows why this might be?

   Répondre

   • byberkan says

     Jan 13, 2016 à 5:27 pm

     I’m hoping you can find the solution. Same problem exists for me.

     Répondre

5. Joe says

   Déc 6, 2015 à 1:02 pm

   It seems we have to do the steps in here after we have our theme, plugin etc.

   Répondre

6. Mark Park says

   Nov 10, 2015 à 4:25 am

   Great article! Just one thing that isn’t clear to me.

   If I have the current non-wordpress website on a domain name example.com and I want to build a new website using WordPress and develop it on a staging environment on a sub-domain dev.example.com – is this possible?
   Can I make a sub-domain dev.example.com and install WP on the same server used by the current non-WP website?
   Later when the website is finished I want to connect my WP developed site with the domain name example.com.

   Thank you for your help.

   Répondre

   • WPBeginner Support says

     Nov 10, 2015 à 10:58 am

     Yes this is possible. Make sure you block search engines on your development subdomain.

     Répondre

     Administrateur

     • Maria says

       Jan 9, 2016 à 2:23 am

       Thanks for a Very helpful article! I am in a similar situation as Mark, however my current website is a WordPress site. Can I still develop the redesigned website on a staging site within a sub domain? And if so do I have to create a new database?

       Répondre

       • byberkan says

         Jan 13, 2016 à 2:50 pm

         You really didn’t read the article, do you?

7. Benito says

   Oct 30, 2015 à 7:05 am

   Hello, great article, but what if I don’t want to use XAMPP, and I just want to use a subdomain as a staging site and then push changes to live? What would be the best way to deploy the changes?

   Répondre

8. Raj says

   Oct 3, 2015 à 12:08 pm

   Will this process create a Database User and add it to the database we created while copying giving it all privileges by itself? or do we need to create a database user at some point?

   Répondre

   • Raj says

     Oct 4, 2015 à 8:13 am

     Okay I tried it.. both ways.
     Once I created the database user before installing wordpress on the staging site and it worked. The other time around, I didn’t and got the issue « We were able to connect to the database server (which means your username and password is okay) but not able to select the a*******_ata_d2db database. »

     That to me means that one has to create a user manually, only copying database won’t do. Right?

     Répondre

     • Sanny says

       Fév 2, 2016 à 1:47 am

       Raj, I see the same error (« Can’t select database »). How did you fix it ?

       Répondre

     • Scott says

       Jan 16, 2017 à 2:00 am

       Hopefully you guys figured this out, but just to leave this here for others to find, you do indeed need to create a database user (which is not clear in this article). While using Bluehost, I had to do about three steps. First step is to use the MySQL Database cPanel to get access to the list of MySQL databases. Once there, I could see that the new staging database that I had copied using phpMyAdmin per the article, did not have a privileged user assigned to it. So, I created a user, but then discovered that the user I created had too many characters (16 is the max). Once I got that straightened out, I then had to Add this user to a database using the same MySQL page. As part of this assignment step, I was able to select « ALL PRIVILEGES » to make this user a privileged user for this new staging database. Once that was all setup, I was able to configure WordPress to connect up to the staging database.

       Répondre

9. Gayle says

   Août 19, 2015 à 1:05 pm

   Terrific resource! Reached a WP staging breaking point and then found this. Lifesaver! Thank you! Only things I’d add would be some meta information for newbies like me. : )

   Répondre

10. LizP says

    Août 18, 2015 à 8:03 am

    Yikes, too hard for me!

    Répondre

11. Deborah says

    Août 10, 2015 à 1:48 pm

    Thanks for the tutorial. I seem to be stuck on one of the very first steps. When clicking go after changing the URL’s in SQL, I get a message of ‘# MySQL returned an empty result set (i.e. zero rows)’
    This is how I’ve entered the data:

    UPDATE wp_options SET option_value = REPLACE(option_value, ‘http://www.example.co.za/wp’, ‘http://staging.example.co.za’);
    UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, ‘http://www.example.co.za/wp’, ‘http://staging.example.co.za’);
    UPDATE wp_posts SET guid = REPLACE(guid, ‘http://www.example.co.za/wp’, ‘http://staging.example.co.za’);
    UPDATE wp_posts SET post_content = REPLACE(post_content, ‘http://www.example.co.za/wp’, ‘http://staging.example.co.za’);

    Can anyone please help me with this?

    Thanks

    Répondre

12. Andreas Kofoed says

    Juil 9, 2015 à 5:35 am

    Hi,

    First of all thanks for an amazing tut on this.

    I’ve encountered one problem so far and that is when I try to enter my subdomain through www.staging.example.com. I get this message: err_connection_timed_out ???

    Répondre

    • Andreas Kofoed says

      Juil 9, 2015 à 8:46 am

      Hi,

      I figured this out as I was due to some table prefix.

      Now my staging.mysite.com is up and running, but the styling and layout is totally different.
      How do I do, so my files in my child theme applies to the current theme???

      It seems like it is missing a lot of pictures, css and some basic settings?…

      Répondre

13. Patrick says

    Juil 3, 2015 à 8:50 pm

    Thanks for this great tutorial!

    I’m finding that after setting everything up, comments on the live blog are now going to the sub-domain staging blog. I can’t find anything in the settings that explains this behavior. Do subdomains perhaps take precedence for some reason?

    Any ideas?

    Répondre

    • Jennifer Filgate says

      Fév 16, 2017 à 1:14 pm

      Perhaps when you ran the operation to update the URLs in your database you performed it on your live site’s database instead of the new staging site’s database? You have to select the staging site’s database after you create it before you run the operation. Maybe you missed that selecting step.

      Répondre

14. Arjun Singhal says

    Mai 11, 2015 à 4:48 am

    I got errors regarding SSL certificates. I am a newbie when it comes to using Git and the command prompt on my Mac. So I couldn’t get to syncing everything like I wanted.

    Also, how it appears is that the steps are good to sync the local disks files to the server – changes in the theme folder etc.

    However, there is no syncing mechanism highlighted for the MySQL server changes in the case of WordPress.

    Répondre

15. Evan says

    Mai 8, 2015 à 4:56 pm

    I don’t know. This just seems really confusing.

    So, a Git Bucket is like an intermediary between your local computer and the hosted dev server? For example, if I have website.com then I create dev.website.com then I create an account and empty repository in Git Bucket then I create an empty folder on my local computer, and I edit files locally and sync them to the Git Bucket repository and then how do I commit to the live site? Is there any connection and control to the live site? It seems like from here, you sync your Git Bucket repository to the dev.website.com

    Then what? I wish this article had a diagram to understand how this all works. It might make sense to you guys because you do it all day, but for the first time, this is a dizzying experience. Especially since multiple points in this setup failed and I had to go about custom fixing each one. At this point, I have created dev.website.com, copied all files from the live site to it, copied the database, connected it in, logged into the dev.website.com wordpress site, made sure all is cool, but now … I am lost as to what I do next.

    In your article, you ask us to INIT a local directory on our computer. Well, I’m trying out Git Bucket’s SOURCE TREE, which by the way looks great. But now what? Any help on what is the procedure from here? What’s the logic to all this?

    I create a folder on my local drive, it syncs to a Git Bucket Repository so that people can develop collaboratively. But who uploads the changes to the dev.website.com server? Don’t users need to be able to do that to see live changes on the server? So how does that all connect?

    And how do you update the final changes to the live website once you’re ready? Man I’m confused. I spent 3 days getting this setup and I can’t figure out this next step, because I don’t understand how that all works.

    Any help?

    Répondre

    • Oscar says

      Nov 17, 2015 à 11:00 pm

      Hi Evan, although I am sure you figured it out by now as its months later, I figured it may help others with the same question. After you have committed your code to version control, you would move your changes over to the server of your choice (dev/staging/production) using the deploy feature. This is described in the section above titled, « Deploying Changes From BitBucket to Staging Site ». Hope this helps clarify!

      Répondre

16. vjohnson says

    Avr 25, 2015 à 12:40 pm

    I am truly a beginner at this, and I have read the article a couple of times. I think my environment is almost set up, the piece that appears to be missing is in the install step. The directions say copy the files but do not install « yet », when in this process do I run an install of wp? I am unsure if some of the issues that i ran into are due to my host which is hostgator or something that I’ve done wrong. Any input would be great.

    What is happening at this point is no errors but nothing is rendered on at the url for my staging area.

    Répondre

17. Martin says

    Avr 21, 2015 à 6:50 pm

    Nice article. Although, the whole way, you’re talking about setting up a development site on the server as a subdomain. But at the end your using a local Xammp server.

    How would you setup a test environment on the server where the doomain is hosted? Do you use bitbucket for it as well?

    Thanks, cheers.

    Répondre

18. Alberto Serrano says

    Avr 20, 2015 à 2:46 pm

    Hello , I made a staging site successfully but my live site already had a little problem with a plug in , I contacted the developer and he asked for my admin credentials , following your advice on other article I gave him log in credentials to my staging site and he fixed the issue , to make the changes on the live site he told me to import the database from the staging site to the live site , my concern is the sql changes I made to the staging database , if I copy the database isn’t my live site going to redirect to the staging site now ? I can’t find the SQL queries to delete them
    Thanks

    Répondre

    • WPBeginner Support says

      Avr 21, 2015 à 9:00 pm

      See our tutorial on how to update URLS when moving WordPress site.

      Répondre

      Administrateur

19. isagani says

    Avr 16, 2015 à 11:53 pm

    hey,

    nice article, i followed all instructions and gave me a clean view process on using git and staging environment. hope all experienced people do what you did so many can step forward from beginner to advance.

    Thanks a lot.

    Isagani

    Répondre

20. Kristof Bernaert says

    Mar 30, 2015 à 4:01 pm

    Just a perfect article that helped me to setup the whole thing.

    My staging environment is on the same shared linux hosting, just in another directory.
    I used this also as the repo for git.

    With Coda, I’m working online in that staging. As I save changed files (mainly css), I see instantly the updates.
    So I don’t need the local files on my laptop.

    But how to checkout those remote files under the staging folder, without fetching a local copy?

    Thx!
    Kristof

    Répondre

21. bcall says

    Fév 9, 2015 à 3:40 pm

    Thanks for the article!

    I have one problem, though: I have two databases and am not sure which one (or maybe both) is connected to my live site. I checked the wp-config.php file and it’s linking to a database with a different name, one that does not appear in my database list (in phpMyAdmin). Is it possible that the database was renamed?

    Répondre

    • Nick Jubrey says

      Avr 6, 2015 à 7:48 pm

      Look in your wp-config.php file that’s where wp is directed to that particular database, the db your using will be listed there.

      Répondre

22. Tiffany Johnson says

    Jan 5, 2015 à 10:06 pm

    I’m having some issues with the dev site recognizing my theme and content. I copied over the following files prior to running my installation of wordpress, however the pages and content are still not being recognized. I checked the files and my media is in the uploads file, my themes are present, as are my plugins, but none of them are recognized in the actual wordpress site.

    /wp-content/uploads
    /wp-content/themes
    /wp-content/plugins

    Any suggestions on what else I can try? Thanks!

    Répondre

    • Nicole says

      Fév 24, 2016 à 11:35 am

      I’m having this same problem. Any suggestions of what to try? I followed the instructions to copy those files from one folder to the other, and it is in the right place.

      Répondre

23. Brad Scott says

    Déc 25, 2014 à 4:17 am

    @WPBeginner,

    For my case.

    Create subdomain: staging.example.com
    Create Document Root: public_html/staging

    Need to run the following SQL queries:
    The NEW_URL should be http://example.com/staging not http://staging.example.com

    Login: http://example.com/staging/wp-login.php

    Cheers & Thanks

    Répondre

    • byberkan says

      Jan 13, 2016 à 5:26 pm

      Brad, so that means you are not using the subdomain. You are just using it as a subdirectory which you didn’t have to create a subdomain to use that..

      Répondre

24. Paula Lay says

    Nov 23, 2014 à 12:01 am

    Thank you so much for this tutorial! The step-by-step instructions are perfect for someone who hasn’t done this before. I encountered a snag where I was getting an error message after creating a subdomain (something like a problem configuring the DNS). For anyone that encounters this problem – clear your browser cache and cookies, and then you will see the correct screen. Took me days to figure this out (I gave it a few days because I thought it would take 24hrs or so for the domain to propogate).

    Répondre

25. Random Dev says

    Nov 11, 2014 à 8:03 pm

    Whoa. Wouldn’t it be simpler, cutting down on quite a few steps and reducing the technical nature of this process, to just use a backup plugin with a migrator (search/replace the database) function… instead of copying the databases manually, *and* instead of using Git/Bitbucket? Or am I not understanding something?

    Répondre

    • Cannonpult says

      Mar 13, 2015 à 3:24 pm

      For smaller sites, maybe. But plugins like Duplicator start to fail or have significant diminishing returns on larger sites. For example, if you were working on a site with a lot of media, Duplicator will never be able to transfer everything. You will get warning messages and have to leave media behind in the transfer.

      Yes, this tutorial would be overkill for a small blog. But it’s absolutely the way you should go for say, a woocommerce site with 3,000 products (including images and custom data).

      The other big consideration is frequency of changes. Some sites are fairly hands-off after they go live. Maybe you just update core + plugins and perform a few minor changes per year. Other sites might require weekly or even more frequent changes. If this were the case, it would become a pain to wait for backups and then drop a backup on the new site (crossing your fingers that it works each time). By using the method described in the tutorial, you can commit smaller changes at a time right after testing them.

      Répondre

26. mgiulio says

    Oct 9, 2014 à 6:03 am

    Excellent article.I was looking for info about best practices for wordpress staging sites. The additional section on the git-bitbucket workflow is very much appreciated.

    Répondre

27. nwesource says

    Août 12, 2014 à 5:13 pm

    Fantastic tutorial, thank you! I know WPEngine.com has a staging site built into their hosting options which seems fantastic although I haven’t tried it just yet. Are there any other easier options you know of to setup and operate a staging site, with more of a plugin functionality like WPEngine? They literally have a clone to staging button and a clone to live button that makes this seem like a process from the 80’s LOL…

    Amazing tutorial, thank you for enterprise level content!

    Répondre

28. WPBeginner Staff says

    Juil 10, 2014 à 8:54 pm

    No you first need to extract the zip folder and then upload the contents of wordpress directory to your staging site.

    Répondre

29. Tony Leary says

    Juil 10, 2014 à 6:54 am

    Can someone elaborate on this one step:

    « First download a fresh copy of WordPress from WordPress.org. Upload the contents of WordPress to your staging site. Note, do not run the WordPress install yet. »

    I read that as « 1) download WordPress zip file from WordPress.org and 2) upload .zip file to /staging folder via File Manager. » However, I don’t think that’s correct.

    Répondre

    • bcall says

      Fév 9, 2015 à 4:49 pm

      You can upload the .zip file and then extract the contents within file manager.

      Répondre

30. WPBeginner Staff says

    Juin 21, 2014 à 2:41 am

    Most probably your subdomain is not configured correctly.

    Répondre

    • Julius says

      Juin 26, 2014 à 12:23 pm

      I actually found out the problem..and it’s been resolved…however, I am unable to add images to my library….anyone else experienced this challenge.

      Répondre

      • Hans Lindgren says

        Août 4, 2014 à 9:47 am

        Is the wordpress install running on Windows?
        (If so, you need to grant Modify NTFS permissions to IUSR on C:WindowsTemp)

        Répondre

31. Julius says

    Juin 18, 2014 à 3:32 pm

    Awesome tutorial…however, after I attempt to log into the staging site I am taking to the « Opps! Google Chrome could not find http ». What am I doing wrong?

    Répondre

32. Julius says

    Juin 18, 2014 à 1:43 pm

    This is really a great tutorial and something I been wanting to do for quite sometime. My problem is that when I visit the WP login screen it appears that the styling from my theme isn’t applied. Is this normal? Also, when I enter my credentials from the live site into the fields for the staging site, it doesn’t log me in. It’s taking me to the « Oops! Google Chrome could not find http ». Am I doing something wrong?

    Répondre

33. Sloan Stewart says

    Juin 13, 2014 à 3:29 pm

    Very helpful article. Only issue I have is that when it begins discussing version control, it switches from focusing on the alternate wordpress installation on the server to a local installation on one’s machine.

    I am assuming one would build your site locally (I am using WAMP) and then use Git/Bitbucket & Ftploy to update your dev/staging wordpress install? That would mean one would have three versions of the wordpress site at all times [Production, Dev/Staging, Local].

    How does one ensure your local wordpress install remains compatible with the database and other configuration on the server? Or is there a way to utilize Git/Bitbucket/Ftploy on the server without having to involve a local copy of your wordpress site.

    Répondre

34. Karlis says

    Juin 2, 2014 à 4:27 am

    Do you need to create user for your freshly created phpmyadmin database?

    Répondre

35. WPBeginner Staff says

    Juin 1, 2014 à 9:59 pm

    No this tutorial is not written for WordPress multisite.

    Répondre

36. Aathi says

    Juin 1, 2014 à 1:40 am

    Hi,
    Will the above process works for wordpress multisite ?

    Répondre

37. Cheryl S. says

    Mai 26, 2014 à 11:19 pm

    Because I typically develop in a staging area on my server and then move it to the clients server to go live, rolling back to previous versions is nearly impossible. This article has made me seriously consider implementing version control with Git and Bitbucket. Thank you so much for this tutorial.

    Répondre

38. WPBeginner Staff says

    Mai 25, 2014 à 3:32 pm

    Yes this would be a better approach.

    Répondre

    • Mimi Bondi says

      Mai 25, 2014 à 5:28 pm

      Thank you. Is it safe to simply copy all the files from the  »test » site and paste them over the current  »live » files via FTP? Or is there more to it?

      Répondre

39. Mimi Bondi says

    Mai 24, 2014 à 8:56 pm

    Would this be the best way to duplicate a website, set it up with a new theme/content then copy it over to the current live website?
    I want to change theme but it’s quite a big job so instead of activating it then frantically trying to fix things for days, I’m looking for a way to copy my current site, change it all  »in the background » then make the new one live. Please let me know if it’s even possible?

    Répondre

40. Mimi Bondi says

    Mai 24, 2014 à 8:26 am

    Once i have my site exacty how i want it in the staging environment,
    is there a safeway to copy those files to the real live site?

    My goal is to change themes but because this would involve quite a bit of
    setting up, i am looking for a way to do this safely and only replace my
    current content with the new content when it’s ready (without changing
    permalinks and SEO hopefully). Is that possible?

    Répondre

41. Larry says

    Mai 12, 2014 à 8:38 pm

    Excellent article….I was able to follow the instructions step-by-step and complete the creation of development site on my hosting server. Kudos to the writter.

    Répondre

42. Mike says

    Avr 2, 2014 à 7:05 pm

    I’m having some issues when I try to run the SQL queries to change the references to the staging site. I am receiving the following error:

     »
    #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘1
    UPDATE wp_options SET option_value = REPLACE(option_value, ‘http://example’ at line 1
     »

    My SQL query is as follows:

     »
    1
    UPDATE wp_options SET option_value = REPLACE(option_value, ‘http://example.com’, ‘http://dev.example.com’);
    2
    UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, ‘http://example.com’, ‘http://dev.example.com’);
    3
    UPDATE wp_posts SET guid = REPLACE(guid, ‘http://example.com’, ‘http://dev.example.com’);
    4
    UPDATE wp_posts SET post_content = REPLACE(post_content, ‘http://example.com’, ‘http://dev.example.com’);
     »

    As I missing a step or do I have something incorrect in query? Thanks for your help.

    Répondre

    • Mike says

      Avr 2, 2014 à 7:22 pm

      Never mind, I figured out my issue. Feel free to delete this comment.

      Répondre

      • djramc says

        Mar 6, 2016 à 4:35 am

        i have the same problem. could i ask how did you solve this issue?
        thanks by advance

        #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘)’ at line 1

        Répondre

    • WPBeginner Support says

      Avr 3, 2014 à 2:49 pm

      You need to remove numbers from lines, replace example.com with your live site url and dev.example.com with your development or staging site URL.

      Répondre

      Administrateur

43. Bevis Larsen says

    Avr 1, 2014 à 6:53 am

    This article is most useful for the user who want to make advance wordpress application

    Répondre

44. Brad E says

    Mar 27, 2014 à 8:56 pm

    I followed the directions and am able to get the staging site to work. However, every link, page and even login revert to the live site not the staging site. How do I fix this?

    Répondre

    • WPBeginner Support says

      Mar 28, 2014 à 6:58 pm

      you need to change site address and wordpress address. To do that you need to run this SQL query in phpmyadmin for the database of your staging site:

      UPDATE wp_options SET option_value = REPLACE(option_value, ‘ORIGINAL_URL’, ‘NEW_URL’);
      UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, ‘ORIGINAL_URL’, ‘NEW_URL’);
      UPDATE wp_posts SET guid = REPLACE(guid, ‘ORIGINAL_URL’, ‘NEW_URL’);
      UPDATE wp_posts SET post_content = REPLACE(post_content, ‘ORIGINAL_URL’, ‘NEW_URL’);

      Don’t forget to replace the original url with the url of your live site and new url with the URL of your staging site.

      Répondre

      Administrateur

      • Brad E says

        Mar 28, 2014 à 7:08 pm

        OK – it works now. I had to run the query several times, but got it to work. The problem I am having now, is that all of the theme settings are missing. The header, widgets, background, etc. are set to the theme’s defaults. I am not sure how to update the settings to what the live site has. I copied the 3 files from the wp-content directory. Thanks for the outstanding article and support.

        Répondre

45. ROHIT says

    Mar 1, 2014 à 5:05 am

    Hi,

    As usual, just read you well written article on staging. I’ve got only question in mind right now and is that if there is any changes made in database while working on any project then do I need to upload it seperately on server from local environment whereas files would automatically get deployed via ftploy.

    Cheers and Thanks.
    Keep your good work up.

    Répondre

46. Clive says

    Fév 23, 2014 à 1:07 pm

    If I make changes on my local WP project, I understand files in my theme are changed, and those are uploaded to staging via BitBucket/Ftploy. What about the database/tables from my local project? I don’t understand why those aren’t also included? Or would the database/tables in staging be updated based on theme changes that are uploaded? Thanks!!

    Répondre

    • WPBeginner Support says

      Fév 23, 2014 à 5:30 pm

      Clive, in your BitBucket repository you can only store your WordPress files. FTPloy simply syncs those files to your staging site.

      Répondre

      Administrateur

      • Paul Sweany says

        Juil 16, 2015 à 3:10 pm

        What do you recommend for when database changes are made? Let’s say I create a new page; should I just re-import the database on the dev server after I make changes to it on my local copy? Also, moving it from dev to live, any recommendations other than manually importing it and running a search and replace to fix the URL?

        Répondre

47. Glen Clay says

    Fév 23, 2014 à 1:04 pm

    As usual, great article and right when I need it. Keep up the great work! On another note, I am on my iPhone and that annoying floating black ‘Trending’ bar keeps getting in the way of me commenting. This article benefited me so much that I went through the several tries it took for me to comment.

    Répondre

    • WPBeginner Support says

      Fév 23, 2014 à 5:36 pm

      Glen, thanks for your feedback. We will look into it.

      Répondre

      Administrateur

48. Eben says

    Fév 22, 2014 à 8:45 am

    I wasn’t really mentioned on what to do with the staging database and how to transfer the changes to the live database, especially if your client has been making changes to the live site while you’ve been making changes to the staging site and there are changes in both databases.

    This is one area of staging environments with wordpress that I haven’t been able to get my head around.

    Répondre

    • WPBeginner Support says

      Fév 25, 2014 à 4:47 pm

      Staging is basically for development, when working on themes or plugins. We imported the database only so that we have actual data to test with. It is not supposed to be a synchronized mirror of your live site.

      Répondre

      Administrateur

      • Juliana Maggioli says

        Août 5, 2014 à 5:23 pm

        I don’t know if is the same as Eben’s question, but everything is going fine till…: upload/transfer the staging content to the live site. supposing everything is perfect in the staging, how do i make all this perfect structure/content be the live site, without risks?

        Répondre

49. Damien Carbery says

    Fév 21, 2014 à 12:44 pm

    I have started using WP Migrate DB (http://wordpress.org/plugins/wp-migrate-db/) to convert urls and paths in the DB. It will also convert urls and paths that are in serialised data.

    So I copy the files to the staging server and create a database and then export the live db via WP Migrate DB and import it to the new database via phpMyAdmin.

    The biggest issue is when the live site is updated before I bring the staging server db back.

    Répondre

50. Zimbrul says

    Fév 21, 2014 à 9:32 am

    If you have Softaculous is even easier to deploy a staging site to the live site: you can clone the site to a location within the same server.
    It’s what I’m doing: I create the staging environment and when done I just go the the list of my WordPress installs in Softaculous control panel and « clone » the site to the live location. The live location must be empty by other files for this to work.

    Répondre

    • WPBeginner Support says

      Fév 21, 2014 à 3:33 pm

      Thats another way to do it.

      Répondre

      Administrateur

    • Giacomo Ardesi says

      Jan 24, 2016 à 10:55 am

      Hey Zimbrul, can you give some more details about Softaculous and how you used it please?

      Répondre

    • Giacomo Ardesi says

      Jan 24, 2016 à 5:00 pm

      Hey Zimbrul, could you please give some more details on how you use Softaculous to clone your WP staging site? Thank you!

      Répondre

51. M Asif Rahman says

    Fév 21, 2014 à 7:48 am

    Thanks Syed & The Team, that’s one of the most complete and understandable for normal readers Staging Guide for WP. Nicely done.

    Répondre