loader.php cannot accurately guess the location of wp-load.php

[simonwheatley]

The CSS for member themes is loaded by adding the following into style.css:

@import url(css/loader.php);

The file loader.php then requires wp-load.php as follows:

require_once( preg_replace('%(.*)[/\\\\]wp-content[/\\\\].*%', '\1', $_SERVER['SCRIPT_FILENAME'] ) . '/wp-load.php' );

Unfortunately this doesn't cover the situation where the WordPress Mu files are not on the site root, as covered here: ​http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

I propose the following: Add a filter to functions.php in the member theme to change the main CSS file directly to css/loader.php, also pass the directory path for WP as a GET param. Currently the entire directory path is passed, which could be perceived to be a security hazard, so maybe just the path relative to docroot should be passed?

[simonwheatley]

Patch to allow members theme to accurately determine the location of wp-load.php, even if it's not in the docroot

[simonwheatley]

Since opening this ticket I've realised that WPMu doesnt like living in a separate folder, ala WP. However I still think this patch simplifies the loading of the CSS by removing an HTTP call.

I guess things could be simplified still further by refactoring the provided function (see patch) to perform the tasks which loader.php does.

[apeatling]

Moving this to 1.1.

[(none)]

Milestone Default Member Theme 1.1 deleted

[DJPaul]

Does this still apply with the BP 1.1 theme changes?

[apeatling]

invalid now.