Jenn — Unlike some hosted blog services, such as Blogger, you can’t just change the location of a wordpress blog. Because WordPress lives on a server, the url specifies the exact location of where the blog’s files are.
For example, an address of http://www.wimnonline.org/wimnsvoices means that the site lives on the server where wimnonline is housed, in a FOLDER called wimnsvoices. In order to change that to anything else, you not only have the change the url but you also have to actually MOVE ALL THE FILES.
Everything should go back to normal if you log in as admin, go to the Options page and under blog address, input the old url, http://www.wimnonline.org/WIMNsVoicesBlog/.
Next, if you do want to change the url, I recommend the following tutorial to help you move everything: Moving Domain name. You’re actually moving subdomains, not domains, but the process is the same. There is also a similar article on The Codex.
And as always, BACKUP YOUR BLOG FIRST, including your database and especially the beautiful theme someone else designed for you. Let me know if you need additional help.
you went a little crazy on your tags for this post. that doesn’t help you.
But what you need to do is to access the database to edit the data. If you are unfamiliar with accessing the database through a commandline interface, you’ll probably want to use phpmyadmin.
Your webhost might give you an address through which to access phpmyadmin, or will allow access through their web panel admin under databases.
You want to get to a table named wp_options. In that table are many records that define vital and not-so-vital options for wordpress. You updated the site url through the interface and now you need to get into the backend to fix it because changing this buggered up the front end.
The first record should be for site URL [siteurl]. If you get that far and are using phpmyadmin, click the edit icon–it’s the pencil in the second column.
There is a visual tutorial for fixing this common problem with phpmyadmin here
While Brittanie’s advice for you to backup your database is wise, you can safely ignore the tips about moving your blog. That’s not your problem.
Incidentally, in a vast majority of these cases, if you’re fortunate enough to have the same browser window open in which the error first occurred, if you go back (yes, the Back button) in your browser, the admin Manage Options should still be cached. Once back at the admin Manage Options page, if you then retype the original info and hit the Save button, the changes are reverted. It also helps to jump straight back to the cached admin page, not go back one page at a time.
Discovered that one by accident one day.
Other than that, it’s off to database, as geoff pointed out. Great tutorial, by the way, geoff. Passing on the link, thanks.
Thanks for the advice, all.
I’m going to try to find someone who knows what a phpmyadmin is and how to use it tomorrow; I really don’t feel qualified to go into the backend to make any more changes. I’m worried that I’ll do something worse.
I did try to hit the “back” button to get back to the page where the error first occurred, but it didn’t work. The manage options were not only not cached, but everything went wiggy after I made the error.
Sorry I used incorrect or unhelpful tags _ i really am a newbie. (This is odd for me, as I’m used to knowing a great deal about whatever I’m working on… this, however, is totally new terrority.)
Any other advice I can pass on to our web volunteers, I will appreciate. Thanks for your help,
Jenn
