• I’m using a custom menu set to primary, in order to link to other non wordpress pages on the same server. It works, but I am forced to use a full url with http, I erase it, and it inserts it again (so the link doesn’t work of course).

    any way to prevent it from doing this?
    thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Not that I know, Generally speaking, WordPress simply doesn’t generate relative urls – only full ones. What’s the problem with using full urls?

    Thread Starter TimTee

    (@timtee)

    thanks, though these aren’t generated, ones I enter as a custom link. It adds it.

    It isn’t that it doesn’t work, but generally when I build a site with menu items to pages within the site, I don’t use fully qualified urls for all menu items so it seemed odd this isn’t an option.
    thanks!

    When using WordPress, you really have to get used to using full urls. Because it uses generated content dynamically from a database via a templating system, using relative urls will produce very unpredictable results.

    I’m working locally and it would be great to have relative links for some of my “custom links”.

    Currently I have to manually change all my custom links to ensure they don’t point to the local drive when I go live.

    ie. change the link from locall888/mylocalsite/page to http://www.mysite.com/page.

    It’s a small pain but a pain that could easily be avoided with a relative link. : (

    It’s possible to provide a relative url on custom menus
    Enter your url as “/relative_url” and it’ll go to http://www.domain.com/relative_url

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘custom links – remove the http?’ is closed to new replies.