WordPress 3.0 does not support relative path

  • I created a new wordpress site for version 3.0. It works fine until I went to the General Settings and changed the WordPress address tp “/wp” and Site address to “/wp”. In the past this worked and I was able to move the whole site and database from dev to test to prod environments and domain to domain easily.

    Trying to save this relative path now gives me these errors:

    The WordPress address you entered did not appear to be a valid URL. Please enter a valid URL.

    The Site address you entered did not appear to be a valid URL. Please enter a valid URL.

Viewing 5 replies - 1 through 5 (of 5 total)

  • WordPress has never supported relative paths. It’s just that it’s now trying to stop you entering them.

    Thread Starter ctang

    (@ctang)

    Well, that new validation should be removed. Relative paths obviously worked as I have moved v2.9.2 from domain to domain easily.

    WordPress 3.0 is broken to me, unless I remove the validation myself and force it to save the relative paths.

    They may have worked if you knew what you were doing and understood how to create the correct relative paths but, in the hands of a less technical user, the results were highly unpredictable, to say the least. The “official line” for some time now has to been to use only absolute urls.

    Sorry…

    use <?php bloginfo(‘template_directory’); ?>

    In the wordpress/wp-includes/formatting.php
    find the

    case 'siteurl':
case 'home':

    blocks, comment out their current content, and add

    $value = esc_url_raw($value);
			break;

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WordPress 3.0 does not support relative path’ is closed to new replies.