Forum Replies Created

Viewing 15 replies - 136 through 150 (of 196 total)
  • Thread Starter agreda

    (@agreda)

    @david Thank you for checking in on this! Your new snippet adds new users without any error, but now only if they do NOT create a blog. Those who create a blog do not get added via this.

    Still hacking away and testing to see if I can get both working in one plugin. All suggestions appreciated.

    Thread Starter agreda

    (@agreda)

    [sigh] I thought since wp rolled in mu, “Blogs are now called Sites; Site is now called Network.”

    Thanks again for the help! Hoping someone else might be able to shed some light on the answer…

    Thread Starter agreda

    (@agreda)

    @andrea thanks for the clarification. Makes sense for all blogs, I just feel the should be “real” users of site 1, perhaps via a superadmin option… or maybe I’m just being selfish since that’s what I’m trying to get working again with this script that stopped working after upgrading to 3.1.

    Thread Starter agreda

    (@agreda)

    @ipstenu Thanks, but that’s the code that threw the error in my last post.

    And forgive me, but it must not be my week for deciphering obvious acronyms… WAG?

    @squidgemonstr Thanks, I’ll check that out.

    I too am at a loss about the whole “pseudo” thing – why not just make them subscribers, or don’t.

    Any ideas how we might get dsader (the ds in ds_new_user_meta, i believe) to take a look at this?

    Thread Starter agreda

    (@agreda)

    As usual, y’all rock. And now for the proverbial, however…

    Changing wpmu_new_blog to wpmu_new_user results in the following error on the activation page:

    Warning: Missing argument 2 for ds_new_user_meta() in /home/triblogs/public_html/wp-content/mu-plugins/new_user.php on line 3

    Here is line 3:
    function ds_new_user_meta($blog_id, $user_id) {

    Interesting aside: Just confirmed using wpmu_new_blog does not throw the error.

    Using user_register results in the same error. What am I missing here? Should there be a $thing that indicates user level after that $user_id thing? Or am I obviously just clueless?

    Thanks again!

    Make sure you search with the asterisk.

    Thank Dog for these forums, otherwise many of us would just keep grumbling to ourselves about how certain things don’t work like they used to! 🙂

    @sw Glad you got it working! We are not using BPS. Did modify WP Stats in any way to get that plugin working? If so, care to share what?

    Does anyone else have any feedback regarding why the WP Stats admin config page might be inaccessible under WP 3.1 MS?

    Thank you!

    The examples in those threads may need some tweaks, but most likely will work straight away.

    Hi Andrea. You’ve mentioned before that all new registered users under WP 3.1 are automatically assigned Subscriber status to blog ID 1, but this clearly does not seem to be the case (at least at tripawds.com) as they are not listed under Site Admin as a user of the main site. The exception, however, is that new users who also create a blog/site are being assigned subscriber status to blog id 1. Those who create no site, are not.

    Now, we have been using the following in mu-plugins to automatically assign all new users main blog Subscriber status:

    function ds_new_user_meta($blog_id, $user_id) {
    add_user_to_blog('1', $user_id, 'subscriber' );
    }
    add_action( 'wpmu_new_blog', 'ds_new_user_meta', 10, 2 );

    It’s been working like a charm, until our 3.1 upgrade. Since then, only users who create a site are being added to the main site.

    So… My questions include:

    • Should all new users (with or without a bblog) appear as subscribers under the primary site admin / users?
    • Could this “new-user” plugin be keeping WP from doing its job?
    • Any suggested “tweaks” for getting this plugin working “straight away” under WP 3.1?

    Many thanks to all for any input.

    PS: Thanks for the multisite user management plugin lead, however, it appears to assign users to all sites, and we only want to add new users to site id 1.

    EDIT: I just now noticed how old this topic is. :-/ But it seemed the most relevant after searching these forums.

    Does anyone have any feedback about using the WP Stats plugin with WP 3.1 Multisite?

    Stats display properly via the Site Stats link (/wp-admin/index.php?page=stats), but the config link (/wp-admin/plugins.php?page=wpstats) redirects to the dashboard (/wp-admin/?c=1).

    New members wishing to activate the plugin cannot do so because the admin page cannot be accessed to enter a key.

    We are running the most current version, which indicates 3.1 compatibility. Thanks in advance for any suggestions.

    Perhaps the issue is unrelated to the hack. After upgrading our multisite install to 3.1, we too lost Stats functionality.

    Too clarify, on sites where WP.com Stats had already been activated, the stats do display, and the new Shortlink menu works in the Admin Bar. The Stats configuration panel, however, is inaccessible. Clicking the WordPress.com Stats configuration link in the dashboard redirects to mainsite.com/wp-admin/?c=1 — regardless of which site is being administered.

    An attempt to activate Stats on another member site results in the same redirection for the configuration link. That site’s dashboard shows the message “WordPress.com Stats needs attention: please enter an API key or disable the plugin.” with the same bad link.

    So, now we have sub-site bloggers unable to activate Stats, and asking why they don’t have the new Shortlink menu. I figured it was just because the needed to activate stats. <sigh>

    We have Akismet network activated with a hardoded API, and it is functioning but also has a configuration link that now redirects to the main dashboard.

    Any feedback is greatly appreciated. Thanks.

    Thread Starter agreda

    (@agreda)

    Thanks for the quick reply, Andrea! That’s what I figured, just looking for confirmation before I deleted my Admin account.

    users sign up to the main site. they are pseudo-subscribers by default

    Hi Andrea, mind explaining “pseudo” subscribers? It’s been a while, and I don’t expect you to remember, but you helped me a couple times during our original WPMU migration.

    At that time we used a custom dsader “New User” plugin, which automatically added all new registered users as subscribers to the main blog/site. I’m wondering if this is no longer needed in mu-plugins. (We’re now running WP 3.0.4.)

    With nearly 2000 users now, and more joining every day I fear the main site may be getting bloated with users affecting performance (if that’s even possible) but we do need them to be users of the main site so they automatically become members of the SimplePress forums running there.

    Thanks again for your time!

    FYI: Here’s how we set up a blog ring using the random blog redirect.

    Thread Starter agreda

    (@agreda)

    On two separate installs? Granted, they are “practically” mirrors, but not exactly identical. If there is a way I can tell about the reporting, just let me know.

    Thread Starter agreda

    (@agreda)

    Sorry for the delay. I have not yet had the chance to test this on a clean install, and doubt i’ll be able to do that anytime soon. I did, however, try on another test multi-site we have, with the following results…

    Uploaded akismet.php only (with no key hardcoded) and activated it successfully on main blog. Attempt to activate on sub-site with no other plugins activated resulted in the same error as above…

    The plugin generated 618 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    Deactivated plugin from subsite, hardcoded the key, then reactivated it and got the same error again.

    Server logs during this time indicate the following:

    [error] PHP Warning: include_once() [function.include]: Failed opening ‘/home/maindir/public_html/wp-content/plugins/legacy.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/maindir/public_html/wp-content/plugins/akismet.php on line 45, referer: http://url.hasbeen.changed/wp-admin/plugins.php?deactivate=true&plugin_status=all&paged=1

    Deactivated plugin from substite and main blog, uploaded Akismet folder including legacy.php and then successfully activated plugin on main blog and subsite without any errors.

    Both sites are running WP 3.0.1 MultiSite, with Aksimet 2.4.0. Hope this helps.

Viewing 15 replies - 136 through 150 (of 196 total)