import existing site

There is no “automatic” way to import html files into WP. But if there aren’t hundreds of html files… you can always put them manually in WP Pages.

As for the address issue: if you are really converting the whole site to be WP powered, then why not move your WP install to the root, so the Pages will look like:
example.com/about-our-church
example.com/youth-program … etc.
Actually, you can re-do the whole website while it sits in that subfolder and when it’s done, just move it up.

The ISP’s install required it to be under a directory.

However, you are correct, I could simply move them, but that kinda kills the idea of having others update the site when I’m not around.

I was wrong, I am able to install to docroot. Let me play some more once I re-install to docroot. Thanks!

but that kinda kills the idea of having others update the site when I’m not around.

I am not sure I understand this concern… Updating the content has nothing to do with where WP is installed.

I was able to install to docroot at https://www.sitename.com, so after install, my main page had the WP splash page.

That’s good…sorta ?? Problem is, I need to create new site apart of current site. No interruptions. So I can do second installation of WP to https://www.sitename.org/wptgc and make new site.

What is best way to take new site from wptgc and apply it to the docroot install of WP at site https://www.sitename.org ?

1. WP doesn’t have a “splash page” – never seen it.
2. Do you have an existing site at sitename.org? Then why did you install WP there if you still have to work on it?
3. The more convenient way would have been:
leave it as it is in a subfolder (wptgc or whatever is called) and work on it – make the Pages, transfer the content, design your own theme etc.
4. When all is done – it’s a few minutes manouvre to move it to the root.

Splash page meaning the default page you get when you hit a site where WP was just installed.

Yes, existing site. The goal is to begin to use a CMS type application ( WP ) to manage the site and allow other people to manage the site content without always having to funnel changes through me.

I initially did install to a seperate directory. This is fine for the initial migration. However, once I’m done, I really need to be able to use WP to manage the actual site and not just a seperate instance that has to be copied everytime changes are made.

I was saying exactly the same thing – see #4: when you are done move it to the root.
I just finished recently a very similar project (about 100 html files in the old site):
– the old site was up till the last moment
– I had WP in a directory (new) and worked on the new structure and theme
– when the new site was OK, I moved it to the root in less than 10 minutes and from there on they can update the site via the WP admin interface

Can you explaing what you mean by move? Did you just copy files to the root? Or install / reinstall WP to root?

I can see working on new site in new directory, but how will WP know the files are not in new anymore and they are now in root?

You just move the WP install files (=all the WP files) from the subdir to the root.
And before doing that you go into admin > Options > General: and change the two URIs to point to the root – not the subdir.
Then (THIS IS A KEY MOMENT!) without trying to open your blog you move over the files and then acces your beautiful new site. No insall, no nothing ??
It can’t be easier…

Once you’ve moved them, can they be administered as they are in the root? I suppose so since you’ve update their URI’s, correct?

Thanks so much for the help.

Hi

I have a similar problem, sort of.

I created a blog, all was well. Then organization I made it for decided they wanted the homepage to be a static “about us” page, and not a cycling blog page.

A simple redirect to the About page using CPanel didnt work, and I was too imptient to wait and all the host tomorrow ?? so I decided to get “fancy” and instead created a new directory for WP and copied files into it.

End result — I don’t know how I did this — the original main site lost all its graphic theme even thought the theme files are still present, and I couldn’t edit anything in the admin, which redirects to the non-formatted homepage.

New directory worked fine but of course didn’t have any of the content we had already built. I did not know what files should be moved over.

And for some reason not all the admin features are available to me (it too redirects.)

Can I either salvage the original site in the root directory, or else fix the new version so that it doesnt redirect? (example, from https://bristolgem.org/NEWS/wp-admin/post.php, when I click on “options” the link goes to https://bristolgem.org/wp-admin/options-general.php (no dubdirectory).

Gosh i hope this made some sense. I’vd been digging a deeper hole hour after hour!

Thanks

You need to reset two key url’s in the database:
https://www.tamba2.org.uk/wordpress/site-url/
to get it all working, then if you need to change things post back and we can help?

Wow! Thanks so much! Whew!

So here is where I was: https://bristolgem.org/

Now, I dont *have* to have a new subdirectory. What I do need to is to make the first page a visitor comes to this About Us page: https://bristolgem.org/?page_id=2

When I made that page the homepage in Options it did work when one clicked on “return home.” But it was not the first page one comes to.

Have I missed a really easy obvious way to do this in WP? Or should i just call the host in the morning and do a regular ol’ redirect from https://bristolgem.org?

Suggestions?

Thanks again!

The way I do it is take the index.php page and make a copy of it, saving it as home.php. Then you can go into home.php using an editor and change the information to read whatever you want, and it’s a static page, and calls in all the sidebar/header/footer info just like the other parts of the site do.

Keep the index.php file in there, but the home.php will override it.

Just make sure that when you’re replacing the content in home.php that you leave all the php tags that call in the “sections” – and you can use regular HTML to code the main content.