Stewart C Baker

Just going to bump this to the top.

Nobody has any idea? Or am I in the wrong forum?

I figured this out after browsing around and noticing one support post which said you have to first declare $withcomments as a global variable before this works. So I changed to that and it works.

So, if anyone else is having trouble with this:

<?php global $withcomments; $withcomments = 1; comments_template) '', true); ?>

should fix it. The global variable is important and not mentioned in all threads on this topic, so I thought I’d post about it. ??

The easiest way to do this is probably to go ahead and set the presentation page to be your home page, and then create a new page (not post!) and set it to use the template titled “Blog Template (posts page)”.

You don’t need to add any content to this page, just set that in the template and label it whatever you want your blog page to appear as in the menu.

The guy who runs my friend’s web hosting is just going to start us off with a fresh WP install, so I’m going to mark this as “resolved” even though I never did get it to work with what we already had.

Starting over is often the best solution!

Thanks all for your help. ??

Thanks, Jesin.

I think that suggestion is probably the best. Unfortunately, I’m not sure I can get access to the SQL tables since my friend’s site is hosted elsewhere. I’ll have him ask his host to give that a shot.

Thanks, Mika.

I’ve tried that and am still getting the same error when I try to access the network admin pages.

However, I also stumbled across this old support forum thread which pretty neatly summed up the problem I was having and which suggested putting the rewrite rules in the ROOT DIRECTORY’s .htaccess file. That and your suggested .htaccess above did the trick–at least for getting the site to recognize that I was trying to get into /wp/wp-admin/network/ instead of /wp-admin/network/. I still wasn’t able to use the multisite setup as a subdomain install, but that’s really not an issue as we’re fine with subdirectories.

With that, I was able to create two new sites: foo.com/test/ and foo.com/testtwo/

Now I have a different set of problems:

• Trying to access the newly installed subdirectory site at foo.com/test/ loads the content, but none of the CSS
• Trying to access the dashboards for everything except the /network/ and main site gives me a redirect loop

The home page is accessed through foo.com; however, when I try to access wp-admin, it redirects me to foo.com/wp/wp-login.php

Were you using the trick to give WordPress its own directory?

I didn’t install the initial WordPress, but it does appear that this is the case. The WP files are not in the root directory (which is actually a subdirectory on a shared webspace, I think, and also not the real root directory).

I’ll set the subdomain option to false and see if that fixes things. Thanks for your suggestions!

Thanks. I’ll have to take another look then, because it was just saying the fields were empty.

(I appear to be doing something wrong anyway, because the plugin isn’t pulling automatically at all even though I have it set to pull once an hour and it’s set to “yes.”)

I had a lot of problems with setting up mine when it came to the X-Path.

What error message do you get when you click “pull feed” manually? Logged successes and errors show up waaaay at the bottom of the “edit source feed” page, below the “field mapping” section.