first please define what you mean by ran an update?  looks like you ran the wp update which is not what was meant… we meant if SP asks you to upgrade, do the upgrade…

Have posted this several times, but its important to get the word out… if you are running from SVN, DO NOT use the wp updater for any sp core, plugin or theme update (its fine for other wp and plugin updates) as it will not work because of svn interference…

moderation? really?  doesnt need moderation here…  but definitely let us know if that continues…  you shouldn’t have posts in moderation at this point…

I fear you may be delving deep into multisite intergration and we dont fully support wp multisite yet…  though we have lots of reports of folks using it together…  Andy and I just dont know multisite and havent been able to fully test it yet…  big plans for the two in 5.1…

the new user list on the forum is cached… so updates can be delayed…  that said, deletes should occur instantly and did in a quick test I just ran…  Can you please explain how you deleted the users so I can make sure to test in that method?

should add we are hoping to add a team member who knows and uses wp multisite since Andy and I are mostly unfamiliar…

So if anyone with some wp multisite and wp chops is interested in helping out with SP, we could use ya!

Bill Murray,
Could you please reply to this topic and then start a new topic to see if either related to your moderation issue?

Quick reply for moderation test…

good. no moderation. will await a new topic. thanks!

On moderation: my reply wasn’t labeled in moderation.  Maybe it is just 1st posts in a thread…

To clarify, I did an SVN Update (what it’s called in Toirtoise SVN) on my folders on my local hard disk.  I didn’t run the WP updater.  I did get a WP update message, but I ignored it.

On multisite, I have a fair amount of multisite experience and can code PHP.  I am happy to provide pointers and test things, but don’t have the time right now for a lot of coding.  That said, unless SPF is doing something strange, none of what I am describing should be tied to multisite.  Table access and settings should be site specific and should just work. 

On the user list, I added a user on Site 3, got the error (discussed in separate thread), then immediately deleted the user.  That was done a couple of users per day from last week (whenever I reported the error).  I probably haven’t added a user to Site 3 since Friday, and all were deleted the same way: by a site or network admin on the admin backend, Users->All Users->highlight user name and click Remove.  I doubt it is purely a cache issue, since the users do NOT appear as newest members on Site 3, only on the MAIN site.

so you deleted the user on the network admin or in the admin for the network site?  doesnt that still leave the user on the main site though?? which would explain why they are still in the main site new user list. 

can you check the sfmembers table for the main site… are those users you deleted still listed? and are they still in the wp users table?

sorry, if ask a bunch of ‘silly’ questions about multisite – just dont know how it functions…  yet!

as to the updater – weird… not sure how the updater code is activated unless via the wp updater…

For user lists in multisite, you have to use the wp_users AND the wp_usermeta tables.  For example, the number of users that the Users admin menu displays for the main site in a multisite network is NOT NECESSARILY the same # as the # in wp_users.  I think the code on how the user list is built for the network is a good example, because it shows the sites that each user is registered on. 

You are right that even though I removed the users from a site, they were still in the wp_users table, because everyone is in the wp_users table.  That does not explain why they are appearing on the main site and not one of my test sites because if SPF used wp_users to grab the newest members, the list would be the same for all sites. 

Yes, the users are still in wp_users (because everyone is always there), and in wp_sfmembers (the members for the main site), but for wp_sfmembers on multisite that COULD be wrong, unless the user registered on the main site.

One suggestion: recommend to people that they either a) only use SPF 5.0 on the main site of a multisite install and only use 1 activation of SPF on the entire network until you sort out the user issue OR b) activate SPF on 1 site in a network that is not the main site, and add users to that site from the main wp_users table (that site could just be the forum and nothing else).

The updater error on the main site went away on its own.

Did you have any thoughts on the profile display before the forum displays?  or the redirection issue?  I am thinking I might uninstall SPF from all sites and then do a re-install on the main site and see if that helps.  One other thing I noticed: manually changing the forum permalink did not change the permalinks on Components->Login and Registration.  Fair enough.  But shouldn’t you put a prompt in both places that if you change 1, you probably need to change the other?

thats what I suspected was going on with the users. thanks for the data.

no thoughts on the profile, as I have not seen something like this…

we have thought about the login and registration urls but the problem is that some folks may have changed it to something else already…  whether to support other plugin or their own thing… either way, we can’t go around changing options that or risk over writing user changes…  kind of a catch-22 for us… so we have gone the safest route which does require an additional user action…

New info on the profile issue: when you do a new install, the first time you load the forum page, the profile page displays – and stays there.  Subsequently, the profile page displays and then is quickly cleared.  That is what is going on, as far as I can tell.  If you do a brand new install, you should see it.

As for my redirection issue, uninstalling SPF on all my test sites plus a complete uninstall/fresh install on the main site solved that problem.  So I think my recommendation on multisite is basically sound: SPF works, but with a limit of 1 SPF install per network.  (Multiple installs probably work too, if you are comfortable with the mashup of users on the main site.)

On the login/register URL’s, I wasn’t suggesting you change your course completely, which is to require an additional action.  That is fine.  But you can add a small note on changing the forum permalink that the login/register URL’s should be checked, and vice versa.  It would probably save you from responding to several questions if something breaks.

oh and I know what I want to do with users…  when a user is created, they should just get sfmembers entry the network sites they are a member of… and if added to another later, get the sfmembers then…  among other things…

but not that simple since some users have already complained that a user on any of the network site should be a user on the main site and maybe even all other network sites…  not what I would expect, but it points out that not everyone thinks the same…

other users want to aggregate anything that happens on network sites onto the main site…

only point out that is a major integration effort that we need to do…

profile…  are you forcing a profile view on first login?  forum – admin – profile options…

No such place as far as I can see. 

Forum->Profiles has a First Forum Visit section, and the Display profile form on login was checked.  However, unchecking it made no change.  I still see the blink. I even tried logging out, and opening the forum in a new browser tab after I changed the setting.  Still, the profile blinks.

On Forum->Admins, these are the only 2 choices, Your Admin Options and Global Admin Options.  Neither has a setting that seems to relate.

argh… typo, sorry…  forum – profile – profile options…

will keep trying to duplicate it, but cant get the blinking here or on any of my test sites…