Can't load site after transfer to root dir

Sounds like an .htaccess issue.

codex.www.ads-software.com/Moving_WordPress#Moving_WordPress_Within_Your_Site

It looks like you’ve stopped at step nine. It seems you can still log in:

https://www.mudshop.com.au/wp-login.php

Try logging in and resetting your permalinks.

Hi – Thanks so much for your quick response!
I tried to login but it I get “Not Found The requested URL /wp-login.php was not found on this server.
Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny13 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g Server at mudshop.com.au Port 80
I am freaking out a bit now! I know this is the correct username and password. I don;t understand about permalinks, is there anything I can do from my FTP?
Thanking you again!

Could this be one of those things where a trailing / on the URL (to make clear it’s a directory) can make all the difference?

Resetting permalinks is easy. Go to Settings / Permalinks, set back to default and save, then restore to your preferred option and save again.

Thanks dgilmour but I can’t get into my admin so I am stuck! When I try to login in I receive an Error 404 message.I am completely lost. Maybe it is because I moved my files to the root dir and not copied them??

Open your .htaccess and paste your WordPress rules here. Make sure to follow the rules for posting code. Your RewriteBase is probably set to your old directory; you can try changing it to just /.

With regards to step 9 and beyond for
codex.www.ads-software.com/Moving_WordPress#Moving_WordPress_Within_Your_Site

it says to: Change the following and save the file. Change the line that says:
require(‘./wp-blog-header.php’);
to the following, using your directory name for the WordPress core files:
require(‘./wordpress/wp-blog-header.php’);
I am not sure I would be changing mine too?
Again, any help would be greatly appreciated.

I don’t see that step anywhere on that page.

Sorry I have got so many “how to” sites open at the moment, frantically trying to find a solution. It got that info from https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory
Could you tell me what word press rules I need to paste into the .htaccess file? I am very new to WordPress and it is all quite foreign to me.

These are the rules added to the .htaccess text file in your WP root directory. (This is a file used by the Apache web server. It contains instructions (Directives, in Apache-speak) which are able to override the default web server settings for that specific directory.)

You can see examples here:
https://codex.www.ads-software.com/Create_A_Network#.htaccess_and_Mod_Rewrite

That codex page is similar, but primarily for doing the exact opposite of what you’re doing right now.

I meant posting the contents of your .htaccess file here, so I can check if there’s an obvious problem. I think it’s a problem with your RewriteBase. It’s probably still set to your old directory rather than the root directory: /. This would cause all your requests to be sent to the old directory, which doesn’t exist anymore.

ok here it is Big Bagel

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Cancel that last post:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /home/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /home/index.php [L]
</IfModule>

# END WordPress

Yup, change it to your first example:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Ok BB will try and let you know…

Bugger, no good: I get this on the page:
The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept
cookies.