rowanwolf

Sorry,no bites or kicks from the horse.

The problem I ran into stopped me from completing the install – much less moving on to the multisite. Otherwise I would not have mentioned it.

I want wordpress in its own directory off the root, and I want my blogs to be in their own subdirectories

example.com.blog1 rather than example,com/wordpress/blog1.

So, all of the files with wordpress are the “core” files?

For number 5, I was in the admin panel and selected settings —> “general” as directed to set up my first site.

Go to Settings -> General and make the site address https://www.example.com while the wordpress address is example.com/wordpress

Part 2
I have two domains – uncommonthought.com and uncommonthought.net

I am trying to move my sites from uncommonthought.com where they are in MovebleType to uncommonthought.net where they are in going to be in WordPress hopefully.

When I entered the first blog name – Uncommon Thought, a yahoo search screen came up informing me that Uncommon Thought was a name that was already taken.

The problem is not that I don’t feel comfortable with moving and modifying files. I do feel relatively comfortable doing that. The problem is the assumption that everyone knows what the assumption that every knows what the “core” WordPress files are (Instruction 6).

Or even where one is installing to start with.

What I did was to
1. I created a database on my server account for WP, and assigned a user.
2. Expanded the latest WP on my PC
3. I accessed my server account via filezilla and uploaded the files to /wordpress.
3. I went into the 5 minute setup.
4. I created an .htaccess file as instructed above.
5. everything fell apart because it would not accept my blog name.

I never got to copying anything or moving “core files”.

Well, I started the install and ran into a problem.

I own the domains exampl.com and example.net. I have been using Movabletype for years, and I have decided to switch to WordPress. I was planning on setting up my blogs (currently in mt and currently at .com) in WP in my .net domain.

When I entered the first blog name, it would not let me save because it is “already owned” – by me, but not sure how to get that to work.

I had planned on getting the setup to work in the .net account and then deciding on whether to move it to the .com domain or relaunch in .net.

Sorry,
I am confused at the top of your instructions where you say:

https://www.example.com/
– /wordpress/
– index.php
– wp-config.php
– wp-blog-header.php
– and all the rest.

I think you are saying put wordpress in its own directory off the root. And then it looks like you are saying to put index.php, wp-config.php, and wp-blog-header.php and all the rest of what ??? in the root directory???

Thanks so much chrismichaels84 as that is not the way I interpreted the directions, and thanks Mika for the reminder on multisite.

Thank you!

So I assume that I upload wordpress to the root directory after expanding the files on my computer.

Then I go through the install.

Then I move all the files except index.php and .htaccess which I COPY to the /wordpress directory.

Then, I do the multisite changes to the wp-config.php file.

At that point I have wordpress installed as multisite in its own directory?

I’m totally lost after that, but first things first.

Thank you for that information. I will uninstall the wp-dpmanager.

I assume this means starting over with setting up the blogs?

That being the case, WP was not putting them where I wanted them to be anyway. Namely, I want

domain.com/blog1

and it produces

domain.com/wordpress directory/blog1

Should I post that question in a separate forum post?

Thanks Ipstenu for your help.

I guess one of the features of wp-dbmanager. It shows up as “Database” on the left side of the dashboard. It says “repair.” I ran it.

As luck would have it, I didn’t have a backup as I was still doing setup on each of the blogs.

I tried “repairing” the database and now it won’t access wordpress at all. I get an error message:
“The site you have requested is not installed properly. Please contact the system administrator.”

I had hoped to not go back to ground zero on this install as I have about 60 hours work into it.

Is there a way to fix it and get back in, or should I just start from scratch again?

Those directories just got created out of thin air. I don’t know why and I really don’t understand them being pushed all the way out to the physical root directory.

I set it up as a multi-site and it is showing Network Admin and all of my blogs. SO it is running as a multi-site …. kind of. All of my posts were there, and now they are only accessible for “Blog 1”

I was planning to switch from MT to WP running in multisite mode. This .net setup is a trial run to get everything working. My hope was to somehow shift the whole shebang to my .com domain and replace the MT blogs, or else redirect and relaunch on my .net domain.

Now I have some mysterious error that is driving me nuts.

Help. Please. I don’t even know where to start.

Here is a print screen. As you can see, it shows 46,136 posts and yet shows “No posts found”

They weren’t there for weeks, and then on 10/20 they appeared. Not only that, wp is installed in the root of domain.net and the folders were created in the physical root of domain.com. I have two domains hosted at the same host. Hence the first domain (.com) is the physical root.

The indents did not show up

domain.wordpress directory
..blog1
… wp-content
……. wp-resources-back
………. file1.4.3

domainwordpressdirectory
..blog 2
… wp-content
……. wp-resources-back
………. file1.4.3
..blog 3
… wp-content
……. wp-resources-back
………. file1.4.3
domawordpressdirectory
..blog 4
… wp-content
……. wp-resources-back
………. file1.4.3

When I drill down
domain.wordpress directory
blog1
wp-content
wp-resources-back
file1.4.3

domainwordpressdirectory
blog 2
wp-content
wp-resources-back
file1.4.3
blog 3
wp-content
wp-resources-back
file1.4.3
domawordpressdirectory
blog 4
wp-content
wp-resources-back
file1.4.3