I have a strange feeling that I tried earlier to setup the public page inside of /wp/ at one stage, and couldn’t get it to work either. Which is why I ended up setting it up the way I did… kept fiddling until it worked.

As far as my previous suggestion goes… that does NOT work LOL

Now that I am wide awake once again, I had the chance to try it out – putting the files as described in a /public/ directory – and no go with that at al!

I got a 404 error when accessing /public/ and while the page displayed properly when looking at /public/index.php in my browser, it showed no posts… so back to the drawing board on that one!

But that is where “trial and error ” makes all of this fun – frustrating at times, but still good fun.

So I think I’ll stick with what works as described in the main post.

Let’s just say that in the root directory I have another website set up.

Basically I have installed the blog to a subdirectory and set it up as you describe except the ‘public’ index.php and associated .htaccess file is in the original subdirectory I installed the blog in rather than the root directory.

So to use your original example, to see that page you would go to /wp/ and it will display, but in my case I don’t see any text for what should be the front page of the blog, although everything else looks ok and all the links in the header and sidebar etc. point to the private area as you would expect.

Tim

Hey Tim

I’ve only set this up with one WP install, and those instructions apply to that case, and don’t quite understand where you put that “unprotected” index.php file mentioned above…

However, I would imagine, if you needed to do TWO WP installations, then you would need to modify slightly…

But I don’t know why you need the 2nd install at all… unless you want to include a lot more “public” pages there, which is probably an OK idea.

In which case… to tie the two installations together (sort of) I want you to try to set up TWO new EMPTY “PAGES” (not posts) in the 2nd blog – this is the blog at the root level.

I’m assuming you have custom permalinks set up to be /%postname%/ – so call these new EMPTY PAGES Members and Public. You’ll notice that when the permalinks come into play, that the URLs to these “pages” are now…
yourdomain.com/public/ and yourdomain.com/members/

Surprise surprise… these are ALSO the paths to your “public” members page and the sealed members section… click on them from the links in the top level blog navigation, and you should go straight to the other blog. Clever little integration trick (I hope LOL)

Please let me know how that goes.

(edit – this second concept of using “empty” pages in your blog navigation to point to existing directories on your server does work – I’m actually doing it on another older site which I am upgrading to WordPress – and still keeping a LOT of the existing HTML sections in play – more on that when it’s finished)

I have implemented it already pretty much as you have laid out except that I have 2 complete blogs – one in the root of the domain and the members one in a subdirectory, but my ‘unprotected’ index.php for the members blog (which I’ve placed in the subdirectory as my main blog is in the root directory) does not display any detail, just the header and sidebars.

The front page is a static page I’ve set up, but it doesn’t show, only my custom 404 page I have set up.
It works perfectly well when you view the index.php in the protected directory.

Any ideas on that?