Support Forum

@ Mr Papa, I tested the latest installation changes on a new site under 1 of my networks, and it works perfectly.

However, it creates 3 folders under sp-resources, which is fine, but this isn't consistent with the description for the SVN setup, so I'd just modify that description. 

After installing a new site, I went back and edited the locations of my existing site, and it works fine.

I have to think more about your comments on "global options" before I can comment intelligently.  There aren't a lot of WP plugins that have global options (I can think of just 1 off the top of my head, NextGen Gallery).  As for feature control of things like file uploading, if that is in a plugin, and a network admin doesn't want to allow that, he can not install or delete that plugin.  I see your point about network admins wanting to control how site admins configure SPF, but I think those are features that only impact networks where users can create their own sites.  Most of the multisite installs I see are where the network admin is controlling the site setups, where that concern is a non-issue.  I think you'd be best served to devote resources to have SPF first work with multisite the way most plugins do, and then tackle the global settings issue.

@ Lee H, you wrote:

"What I meant about write access to admins. Currently it appears that any networked blogs would need write access to add new or any additional themes/plugins to their selection."

Sites cannot add themes or plugins in a standard multisite install, and I'd recommend that they not be allowed to add SPF themes or plugins as that is not consistent with the way multisite works.  Network admins can only perform these functions.  Adding a new plugin is separate from activating, so a site admin could activate any 1 of the installed plugins.

"As it is now, a admin from another blog on the network can edit the paths to the main blogs forum install and use or modify whatever is there."

I'm not sure that's the case.  An admin from Blog A is only editing the SPF settings for Blog A.  Unless that person is also an admin on the main blog and logs into the main blog, the settings are completely independent.  I haven't tested every element of that, but I have made changes to the settings on 2 forums on 2 sites of the same multisite installation, and the settings are independent.  That is just the way multisite works with just about every plugin out there. 

@ Mr Papa, new install.  I updated the code, created a new site, activated the plugin on that site, and then continued on.  I figured I'd mention the SVN documentation thing because keeping that updated provides a strong foundation for doing the documentation for the ultimate release.

@ Lee H,

"I'm saying that blog.2's forum can set the storage locations path to blog.1's forum storage locations. Then in the backend of blog.2's forum, the admin can delete any or all smilies, badges, avatars, icon etc, that are in blog.1's storage location. And the SP backend will happily do it without complaint. Of course these files can be uploaded as well. Imagine your surprise if your wholesome forum icons where replaced with something XXX?"

Ok, light dawns on my marble head, and I see your point, which might be valid.  I tested and I could change Blog 2's custom badges folder to that of Blog 3, and then proceed to do what you suggested but I was logged in as a network admin.  Then I tried creating a site admin for Blog 2 and could still change locations to Blog 3.

SPF reported that I had write access to Blog 3 folders while on the backend of Blog 2.  Is SPF's write access test faulty?  Or is this a multisite issue where multisite isn't controlling write access in blogs.dir?  I'll do some more investigating on the WP side and see what I can find. 

One workaround could be for SPF to check if the install is multisite, and if so, only let a blogs.dir folder location be saved if it contains the current blog ID.

Interestingly, when I went to add a new site admin, I got this error:

Warning: Cannot modify header information – headers already sent by (output started at /problem-with-post-edit-buttonome/qbg/qbgarage.com/wp-content/plugins/simple-press/sp-api/sp-api-primitives.php:763) in /problem-with-post-edit-buttonome/qbg/qbgarage.com/wp-includes/pluggable.php on line 934

The user was created, however.  Hopefully, the SPF team catches that.

I may not have communicated effectively on the issue of access to themes and plugins.  Network admins do exactly what you do because that is the way multisite works.  I was referring to the creation of new blogs rather than new themes or plugins.  There are web services offering the ability to create for a new user to create a site, much like wordpress.com.  I don't see these services as a big target initially, because I think most multisite installs are where the network admins create the sites themselves.