so that url is normally indicative of an incorrect install…   not the data, but the files…

typically, simple press is either uploaded to wrong location, ie not in wp-content/plugins or the filename of our plugin got changed…  it must be wp-content/plugins/simple-press

or it can happen if you have another version of simple press in the plugins folder (though usually get a multiple definition issue first)

SP is installed in /www/wp-content/plugins/simple-press

This is the only version of SP I have ever installed.

This is a multisite WP install with several subsites using the same SP plugin, each with its own resource directory.

e.g. the Publications and Communications committee uses /www/wp-content/sp-resources/pubcom

SP wanted to use locations in the the blogs.dir format that is now obsolete, so I manually edited the locations for the resources in Integration/Storage Locations. There should be a place to make the base location permanent, so SP doesn’t keep choosing wrong locations every time I install a plugin that needs a directory made. Is there somewhere I can make that edit? Would that have anything to to with the incorrect URLs? Funny that they are correct on two out of the three menus. That seems to indicate a programming issue, rather than an install issue, otherwise all three menus would be wrong?

blogs.dir is only obsolete on new installs… existing installs still use it…

in the next version we hope to handle the optional blogs.dir better (not use for new installs)…

Funny that they are correct on two out of the three menus. That seems to indicate a programming issue, rather than an install issue, otherwise all three menus would be wrong?

not trying to be a smart ass, but even more telling is that we have many tens of thousands of installs and many multisite installs that dont have that problem…  so its not a general, systemic problem… but we just need to understand what is going on in your unique situation…  still could be something we need to handle in code, but without understanding better, dont know…

so is this problem on the main site or a network site?  does it happen on all network sites?

which panels appear wrong?  if you look through the code, you find that the url to our admin pages are generated thorugh constants using the wp api:

if (!defined(‘SFADMINFORUM’))          define(‘SFADMINFORUM’,               admin_url(‘admin.php?page=simple-press/admin/panel-forums/spa-forums.php’));
if (!defined(‘SFADMINOPTION’))         define(‘SFADMINOPTION’,               admin_url(‘admin.php?page=simple-press/admin/panel-options/spa-options.php’));
if (!defined(‘SFADMINCOMPONENTS’))  define(‘SFADMINCOMPONENTS’,     admin_url(‘admin.php?page=simple-press/admin/panel-components/spa-components.php’));
if (!defined(‘SFADMINUSERGROUP’))      define(‘SFADMINUSERGROUP’,      admin_url(‘admin.php?page=simple-press/admin/panel-usergroups/spa-usergroups.php’));
if (!defined(‘SFADMINPERMISSION’))     define(‘SFADMINPERMISSION’,     admin_url(‘admin.php?page=simple-press/admin/panel-permissions/spa-permissions.php’));
if (!defined(‘SFADMINUSER’))           define(‘SFADMINUSER’,               admin_url(‘admin.php?page=simple-press/admin/panel-users/spa-users.php’));
if (!defined(‘SFADMINPROFILE’))        define(‘SFADMINPROFILE’,           admin_url(‘admin.php?page=simple-press/admin/panel-profiles/spa-profiles.php’));
if (!defined(‘SFADMINADMIN’))          define(‘SFADMINADMIN’,               admin_url(‘admin.php?page=simple-press/admin/panel-admins/spa-admins.php’));
if (!defined(‘SFADMINTAGS’))           define(‘SFADMINTAGS’,               admin_url(‘admin.php?page=simple-press/admin/panel-tags/spa-tags.php’));
if (!defined(‘SFADMINTOOLBOX’))        define(‘SFADMINTOOLBOX’,           admin_url(‘admin.php?page=simple-press/admin/panel-toolbox/spa-toolbox.php’));
if (!defined(‘SFADMINPLUGINS’))        define(‘SFADMINPLUGINS’,           admin_url(‘admin.php?page=simple-press/admin/panel-plugins/spa-plugins.php’));
if (!defined(‘SFADMINTHEMES’))         define(‘SFADMINTHEMES’,               admin_url(‘admin.php?page=simple-press/admin/panel-themes/spa-themes.php’));
if (!defined(‘SFADMININTEGRATION’))    define(‘SFADMININTEGRATION’,    admin_url(‘admin.php?page=simple-press/admin/panel-integration/spa-integration.php’));

which is why, as I mentioned, thus far, any issue like this has come to down to incorrect installation…

so just gathering more data..

OK. Just to back up a bit, I added the plugin in the superadmin dashboard, but did not network activate or install there as only a few of the 30 subsites will be using it and I didn’t want to confuse subsite managers.

I then activated and installed it on three subsites. Should I have done a network activate and install before installing it on subsites??? Everything seems to be working OK except for the one menu that appears below “Forum” once that is opened. The pop-out menu to the right, and the detailed menu in the central area both are correct.

you do not need to do a network install…  it can be activated only on the sites needed…

to be honest, I am not sure if I have ever tested a network site without it also activated on the main site…    that actually might be required since there are some options not available at the network site – ie storage locations…

anyway you can run a quick test by activating it on the main site and seeing if that helps?  I will try to do that same, but today is pretty tied up with getting our mobile responsive theme beta going…

I added it on the main site (not the network admin site) but no difference.

Is there somewhere in the settings to override the menu defaults?

if you want to override the menu urls, just change the constants I posted earlier…

There is even an action you can hook into after they are defined:  sph_global_site_constants

just tested this today on some multisite test sites and could not duplicate… works fine…

just to check, no domain mapping plugin, right?

OK. Thanks! That should work. No, there is not a domain mapping plugin.

Cheers,

Bruce

cool.. please let me know how that goes… still very interested in what is going on here…