WordPress.org

Ready to get started?Download WordPress

Forums

WordPress Paths and XAMPP (5 posts)

  1. aianta03
    Member
    Posted 5 years ago #

    Hi,
    I was using XAMPP to create a wordpress website. Every thing went well until I tried to access it from another computer... The themes CSS was removed! I dug around in the code to see what the matter was, and I found out that this was going on.

    When the theme was importing CSS it was looking at bloginfo style sheet URL = localhost/website/wp-content/,etc The problem was that it was looking on the client computers loclhost, not on the server. How can I modify my theme to look at my servers internal IP rather than at "localhost" I have already tried replacing the stylesheet URL with the path to the style sheet but it still doesn't work.

  2. jcotter
    Member
    Posted 4 years ago #

    I'm having the same issue. Did you ever get it resolved?

  3. aianta03
    Member
    Posted 4 years ago #

    nah, I dropped it after a while since it was a hobby type project. Still if anyone has a solution then that would be great.

  4. n1lore
    Member
    Posted 4 years ago #

    use the web url in the general tab, url and blog. fixed my missing external css scripting , but now i have the issue that i cant get to my own site internally using localhost or the IP, of course web url wont work.

  5. ClaytonJames
    Member
    Posted 4 years ago #

    @n1lore

    http://wordpress.org/support/topic/376654?replies=3#post-1439305

    I think localhost and 172.x.x.x addresses are reserved for private blocks. They are never meant to be directly reachable from the WAN. You must (which you have already successfully done) use your domain name in the URL's to make it accessible to the public (Which it is) by resolving your ip to your domain name. I assume on a home network this is provided by a dynamic ip update service of some sort. If you don't want to tackle the hardware I already mentioned or isp issue that is giving you problems connecting, you can probably circumvent it by adding an exception to your hosts file on the server to resolve 127.0.0.1 (localhost) to //www.yourdomainname.com.

    That way you can use the browser on the server to view your site locally. Seems to me it would be easier to just troubleshoot why you cant resolve back inside your own network through your own router.

Topic Closed

This topic has been closed to new replies.

About this Topic