shortandsharp
asked on
Why I could not run wordpress on my fedora 5 server?
Hi, I just upload every thing to my fedora 5 desktop server, but still I could not access the categories and post although I have the the siteurl and home value change respectively
update wp_options set option_value='http://192.168.xxx.xxx/wordpress' where option_name = 'home';
update wp_options set option_value='http://192.168.xxx.xxx/wordpress' where option_name = 'home';
update wp_options set option_value='http://192.168.xxx.xxx/wordpress' where option_name = 'home';
update wp_options set option_value='http://192.168.xxx.xxx/wordpress' where option_name = 'home';
I suggest you read the documentation and install Wordpress again, or at least learn how to move an existing installation from a server to another one. What you have done isn't how it's supposed to work.
Also running a server in your home, even if your ISP allows it (many don't) is not a good idea. There are many hosting companies offering space, including http://wordpress.com/
ASKER
the purpose of me getting every thing posted on my local machine is to cut hosting latency and test the layout. when there's a reasonable amount of content, then I upload it. I've read every thing from http://codex.wordpress.org/Moving_WordPress, that's why I ask why is it not possible to run on a local linux blackbox.
thanks.
thanks.
Ok then,
Can you access the default page after moving to new server? What is the error when you try accessing the categories and posts link? What is the format of its URL? Have you moved the database to local or still connect to it remotely?
Personally I don't see how the update you use above would help in anyway.
Can you access the default page after moving to new server? What is the error when you try accessing the categories and posts link? What is the format of its URL? Have you moved the database to local or still connect to it remotely?
Personally I don't see how the update you use above would help in anyway.
ASKER
http://192.168.123.xx/wordpress/qualityavalanche/category/insurance/health-insurance, move the database to local already.
/%id/%/%post_name%
thanks
/%id/%/%post_name%
thanks
Have you tried disable the pretty URL option (go to the Administration > Options > Permalinks), switch to default and see if it works? I'm sure it's an issue with your .htaccess file.
ASKER
Yes it works but any one. but then there should be a reason why production server can achieve using customize Permalinks, and why my can't work, even though I have make .htaccess file 666 in the wordpress install directory. thanks
If you are trying to run this on a local server, just to test you are asking for problems. Most ISPs provide a dynamic IP which changes frequently, which forces you to use one of several workarounds, like dynamic dns, and any permalinks from that are not going to work when you finally upload anyway.
ASKER
Any wordpress blog can be run anyware without any connection to the Internet. My purpose is to reduce hosting latency, as in if I were to post to do the live server one by one it's going to cost me time. thanks
you are right, but wp on a local server is just going to have one reader - you
wp on a lan is just going to have people on the lan
but in either case, permalinks are going to be focused on where it is, and later moving it to a public server is going to present problems
wp on a lan is just going to have people on the lan
but in either case, permalinks are going to be focused on where it is, and later moving it to a public server is going to present problems
ASKER
What do you mean by moving it to a public server is going to present problems? You mean I cannot develop reasonable amount of content before I upload both the files and mysql database?
thanks
thanks
It might work if you use relative addressing on all links, and set it up with the same directory structure on your host, but if you ever have a post which points to one of your permalinks it will be like http://192.168.xxx.xxx/wordpress ..... and when you go public it will be more like http://mydomain.com/wordpress ..... and you are probably going to decide it looks better as http://mydomain.com/ ..... or http://mydomain.com/blog/ ..... in which case even those are going to need to be fixed
And with some servers you may have an additional "/html" mixed in just to make life even more fun.
And with some servers you may have an additional "/html" mixed in just to make life even more fun.
Permalinks are intended for use on an Apache server with mod_rewrite enabled. Are you running Apache, and if so, is mod_rewrite enabled?
If you do have Apache, this article will explain how to enable mod_rewrite:
http://cocoon.apache.org/2.1/faq/faq-configure-environment.html
If you do have Apache, this article will explain how to enable mod_rewrite:
http://cocoon.apache.org/2.1/faq/faq-configure-environment.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.