briansage

Thanks, @ravanh. I like that.

Left a 5-star review for the support.

We had a similar problem with Nginx. We had to configure it to explicitly pass the the sitemap.xml request to index.php, like so:

server {
  ...
  rewrite ^/sitemap\.xml$ /index.php?feed=sitemap last;

Above makes a good tip for newer WP versions.

function my_function_admin_bar(){ return false; }
  add_filter( 'show_admin_bar' , 'my_function_admin_bar');

Found this here: https://www.ads-software.com/support/topic/31-update-causing-28px-top-spacing-in-html-body?replies=28

Finally got a single site install to work (brilliantly, I might add). The trick we had to overcome was our path vs. directory discrepancy, and we sort of did it by lying to the server… We added a ServerAlias that matched the production site’s and pointed our hosts files to it during setup ??

Thanks again for all the help. I’ll be giving multisite another shot after we prove a few things with this setup.

Yeah, nothing is working well at this point. Even / is a WP 404, while we have posts. We’ve given up on the multisite, all together, until we can get this working correctly.

I think the big issue is that we have sitedomain.com/blog/ (Ruby on Rails project on Apache) using mod_proxy to grab content from blogserverIP/sitename/ (WP single install on Apache). Somewhere in all that, it’s going awry.

Thanks for the advice. This seemed to work at first blush, but pretty permalinks aren’t working, now that we’re testing content.

My suspicion is that permalinks need to be setup in the master network, then settings need to be cloned and remain unchanged. Does that sound right?

@lovefishing
It depends on which theme you are using, but likely it will be in one of sidebar.php, header.php, or footer.php

Also, this thread is for the Alpha version of 3.0, which you should upgrade from, if you haven’t already. This may not even be your problem. Good luck with it.

Thanks Andrea! I’m getting one…

Well lookie there: https://core.trac.www.ads-software.com/changeset/15193 it appears that in RC3

add_theme_support( 'nav-menus' );

…has changed to…

add_theme_support( 'menus' );

I feel rather silly now, but I hope this helps someone else. Enjoy!

Adding another report to this thread, I have a custom built theme (modded from TwentyTen, of course) on 3.0 RC2 that has working custom menus. When migrating the project to a new server with 3.0 RC3 the menus just stopped working.

oldserver.com/wp-admin/nav-menus.php works great (3.0 RC2)

newserver.com/wp-admin/nav-menus.php now reports, “Your theme does not support navigation menus or widgets.” (3.0 RC3)

Could this have anything to do with PHP include paths, permissions, or anything else a different server environment might introduce?