Hi Samboll…
It helped…I’ve been able to successfully display the home page…
The parmalinks to the posts aren’t working though…(I get a 404)
I tried changing the permalinks structure in the permalinks panel, and it showed a success message…the links to the posts are updated to the new structure as well, but I get a 404 on those links…
The mod_rewrite module seems on in the httpd.conf…
What else do I need to check?
Also, when I go to ‘Post New’ in admin panel, the page redirects to itself (/wp-admin/post-new.php) after a few seconds, and then hangs… 🙁
Not sure what the problem is…
Ya, the key is updating the meta option for url in the database to fix the log in problem.
I’d have to say that the “moving WordPress” page doesn’t quite cleanly solve the dev to production problem yet…
A few things need to be built:
1. Something that translates serialized data from dev to production.
2. Something that let’s WordPress know if it’s on dev or production. Maybe a yaml file gets read, since that’s what the cool kids do. 😛
3. Something that let’s you make sure you don’t accidentally erase blog posts on production and just let’s you transfer the data you need. Right now, it’s pretty easy to blow data in production. :-\
Hi…
Could you please elaborate on this? 😐
“Ya, the key is updating the meta option for url in the database to fix the log in problem.”
@ barce – all of that is total nonsense
@ sumedh – try this
delete your .htaccess file
upload an empty one and chmod 666
update permalinks
chmod .htaccess back to 644 for security
links should work now
Hurrraaayyy !!!
Finally it worked… 🙂
I had “AllowOverride None” in my Apache httpd.conf file… 🙁
One more related change…
If possible, I want to use http://www.example.com/category1 for category pages instead of http://www.example.com/category/category1 …I don’t think current admin panel UI allows that…any suggestions?
Samboll, thanks a lot for all the help you are offering… 🙂
