guht

I was refering more to the WP aspect of how to implement this, and how .htaccess relates to users created in WP, and how you get posts marked as private to go to a seperate blog. Would another instance of WP need to be installed point to that directory? Or does WP need to be configured somehow to have private posts be held in a seperate directory?

Im just not understanding the concept here… Oibiviously its ignorance on my part.

How does that work exactly? Is there some step by step instructions on doing something like this somewhere? It seems the above suggestions assume some other general knowledge that is not elaborated on in these posts.

I would like to do this also, but not sure how/where you would set this up. I noticed that when posting a message you can make the post private, but I dont see where or how you would make those blogs go to a special directory created just for personal files.

More detailed info would be greatly appreciated!

I encountered this problem just recently and I tried every solution I could find, and nothing worked.

I added a little code to help me debug what was actually going on and upon comparing the admin & referer urls. Upon comparing them I noticed that they were different – and then the light bulb went on upstairs.

I am using a dynamic dns forwarding service, because my ISP blocks port 80. The actual url is different, and yours may be also. I was trying to use https://www.foo.com as the siteurl in the config file, and I actually needed to be using www2.foo.com:6000 – the 6000 is the port Im forwarding http requests to.

Hope that helps some people.

Actually… I just continued through the warnings and filled in the information – it seems to work now except im getting permissions 403 error when trying to view login page…

I think that has to do with how directory is setup in IIS..

what wp_ tables? The install script never created any…

It looks like the file upgrade-schema.php is the one that has the commands that ‘SHOULD’ create the tables and populate the table wp_options, but I dont know if that file is even being execute or called by the install.php script.

Was this problem ever resolved? I am having the same problem.

function get_alloptions() {
global $wpdb, $wp_queries;
$wpdb->hide_errors();
if (!$options = $wpdb->get_results(“SELECT option_name, option_value FROM $wpdb->options WHERE autoload = ‘yes'”)) {
$options = $wpdb->get_results(“SELECT option_name, option_value FROM $wpdb->options”);
}
$wpdb->show_errors();

foreach ($options as $option) {
// “When trying to design a foolproof system,
// never underestimate the ingenuity of the fools :)” — Dougal
if (‘siteurl’ == $option->option_name) $option->option_value = preg_replace(‘|/+$|’, ”, $option->option_value);
if (‘home’ == $option->option_name) $option->option_value = preg_replace(‘|/+$|’, ”, $option->option_value);
if (‘category_base’ == $option->option_name) $option->option_value = preg_replace(‘|/+$|’, ”, $option->option_value);
@ $value = unserialize($option->option_value);
if ($value === FALSE)
$value = $option->option_value;
$all_options->{$option->option_name} = apply_filters(‘pre_option_’ . $option->option_name, $value);
}
return apply_filters(‘all_options’, $all_options);
}

The line it complains about is the foreach statement..