Developing a WordPress site in a (sort of) live environment

  • Hi, new to word press and have a simple question.

    I built a basic site locally using MAMP, and after enough MAMP issues decided I wanted to start working on an actual hosted environment to. I am building a personal travel/photo blog for an international trip of about three months over the summer. I have a couple months to get the kinks worked out but want to do so on my actual hosts servers (Bluehost)

    My question is, what is the most simple/elegant way to keep the site “under construction” as far as the root domain and still allow me to test/develop in a live environment. The last site I worked on was html (and with Frames, at that =), so my reference would be like renaming the “index.html” to like “index2.html” and then putting in an index.html with an “under construction” banner or some such.

    Two things I tried, which seem suboptimal are password protecting the root directory (this created “http error” when uploading photos) and renaming the wp-config.php file (which upon visiting the site prompts to create a config file and allows you to do so) I’m sure there is a simple way to do this. Ideally, I’d have a visit to the root “.com” generate an under construction type screeen, and I could test the real site with like a “.com/testing” URL or something like that

Viewing 4 replies - 1 through 4 (of 4 total)

  • Develop in a sub-folder, then use the technique outlined in this Codex page to allow WordPress to take over the root domain.

    Thread Starter mseneca

    (@mseneca)

    Any chance of something a little simpler (a la changing a filename and then just entering that in the address bar to get to it)?

    I just followed the instructions on that link and ended up with lots of errors. I changed everything back to the way it was. The temporary option would be to remove the password on the root directory while actively uploading and changing things and then reapply the password after.

    No – that’s about as simple as it gets.

    Thread Starter mseneca

    (@mseneca)

    Turns out password protecting the public root wasn’t what was creating my upload error. So all is well with that approach.

    So just a password on the root folder, remove the password to go “live.”

    That’s as simple as it gets.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Developing a WordPress site in a (sort of) live environment’ is closed to new replies.