Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'wp user activate'

Viewing 25 results - 776 through 800 (of 903 total)
  • Author
    Search Results
  • #58943
    kiwipearls
    Participant

    I have the exact same problem. Is there an easier way to fix this?

    Can I just overwrite WPMU and Buddypress via FTP? Or do I really need to delete them all first? I just want a step by step, layman terms, of how to go about this. And I suppose I will need to remember my sql db access passwords..lol shame on me I know, but I might just create a new user for that SQL table and use that for access.

    I tried just reinstalling Buddypress…deactivated, deleted the files, re-uploaded Buddypress via FTP – then reactived it…so doing that alone did not fix the problem. It still won’t let me select default theme. So I guess I need to do the same for WPMU.

    I just don’t want to go through the trouble of deleting WPMU and then re-uploading it – plus all my plugins (which I have backuped).

    But from now I I will just ignore the auto-update linky thingy.

    #58894
    Jeff Sayre
    Participant

    … it isn’t feasible since the queries it would take to pull that off would be astronomical.

    If the data can be written to a table to begin with, and the structure of the written data makes sense, then in theory a query can be designed to accomplish the same outcome without having to write it to a table.

    But in practice, since WP uses a sharded DB and not a normalized DB schema, this could be an issue.

    … but I think the talking back and forth between the components isn’t really the job of the core to do

    Okay, I think I just saw a ghost. That was a scary comment, jjj!

    Whereas I agree that it may not be the responsibility of the core to ensure that non-core components successfully talk back and forth with each other or with other core components, it is absolutely the responsibility of the core to ensure that each core component effectively and properly communicates with one another when activated. Every component we have discussed here is a core component.

    What you basically just said is the right hand does not need to know what the left hand is doing. In actuality, your right hand may not always need to know what your left hand is doing, but sometimes it is an absolute necessity. The brain takes care of this for us, of course.

    BuddyPress’ core needs to take care of monitoring, negotiating, and policing the actions of its core components. As users and developers, we are entirely dependent on the core development team to make sure that happens.

    #58814
    Anton
    Participant

    1. Which version of WPMU are you running? 2.86

    2. Did you install WPMU as a directory or subdomain install? Sub directory

    3. If a directory install, is it in root or in a subdirectory? root

    4. Did you upgraded from a previous version of WPMU? If so, from which version? Nope. Fresh install.

    5. Was WPMU functioning properly before installing/upgrading BuddyPress? Didn’t test WPMU on it’s own. Installed it to use BB

    6. Which version of BuddyPress (BP) are you running? 1.13

    7. Did you upgraded from a previous version of BP? If so, from which version? nope

    8. Do you have any plugins other than BuddyPress installed and activated? Yes. deactivated them all and the problem(s) still occurs.

    9. Are you using the standard BuddyPress themes or customized themes? Standard. Only edited the default css and added a couple of links.

    10. Have you modified the core files in any way? Yes. The delete button next to the code is not working and If I add any chars to the delete string eg: http://socialpress.co.za/friends/activity/delete/123?_wpnonce=30864bbwe2 it does delete but not always. Some members can’t delete. The default delete string does not work. I have also added those same chars to the RSS site wide activity feed as the default one: http://socialpress.co.za/activity/feed doesn’t work.

    11. Do you have any custom functions in bp-custom.php? nope

    12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in? 1.13

    13. Please provide a list of any errors in your server’s log files

    there’s quite allot of these

    [12-Dec-2009 19:18:07] WordPress database error Table ‘socialpr_socialpress.wp_bp_activity_sitewide’ doesn’t exist for query SELECT COUNT(id) FROM wp_bp_activity_sitewide WHERE hide_sitewide = 0 ORDER BY date_recorded DESC made by require, require_once, include, bp_has_activities, BP_Activity_Template->bp_activity_template, bp_activity_get_sitewide_activity, BP_Activity_Activity->get_sitewide_activity

    [12-Dec-2009 19:18:21] WordPress database error Table ‘socialpr_socialpress.wp_bp_activity_sitewide’ doesn’t exist for query SELECT * FROM wp_bp_activity_sitewide WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 0, 10 made by require, require_once, include, dynamic_sidebar, call_user_func_array, WP_Widget->display_callback, BP_Activity_Widget->widget, bp_has_activities, BP_Activity_Template->bp_activity_template, bp_activity_get_sitewide_activity, BP_Activity_Activity->get_sitewide_activity

    [12-Dec-2009 19:18:21] WordPress database error Table ‘socialpr_socialpress.wp_bp_activity_sitewide’ doesn’t exist for query SELECT COUNT(id) FROM wp_bp_activity_sitewide WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 200 made by require, require_once, include, dynamic_sidebar, call_user_func_array, WP_Widget->display_callback, BP_Activity_Widget->widget, bp_has_activities, BP_Activity_Template->bp_activity_template, bp_activity_get_sitewide_activity, BP_Activity_Activity->get_sitewide_activity

    [12-Dec-2009 19:18:21] WordPress database error Table ‘socialpr_socialpress.wp_bp_activity_sitewide’ doesn’t exist for query SELECT * FROM wp_bp_activity_sitewide WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 0, 10 made by require, require_once, include, bp_has_activities, BP_Activity_Template->bp_activity_template, bp_activity_get_sitewide_activity, BP_Activity_Activity->get_sitewide_activity

    [12-Dec-2009 19:18:21] WordPress database error Table ‘socialpr_socialpress.wp_bp_activity_sitewide’ doesn’t exist for query SELECT COUNT(id) FROM wp_bp_activity_sitewide WHERE hide_sitewide = 0 ORDER BY date_recorded DESC made by require, require_once, include, bp_has_activities, BP_Activity_Template->bp_activity_template, bp_activity_get_sitewide_activity, BP_Activity_Activity->get_sitewide_activity

    SHouldn’t there be a table wp_bp_activity_sitewide on the installation? I’ve looked in the db but it’s not there. I did the default installation.

    .

    14. Which company provides your hosting? Hostgator

    #57891
    Andrea Rennick
    Participant

    :D I’m just finishing up a post on how to do backups.

    “I thought about the index.html as well, but that would still make people loose their posts they are editing when upgrade is taken place (or is failing), wouldn’t it?”

    Hopefully you’ll have booted them out & warned them. :D Don’t upgrade on the middle of a Thursday, for instance. First thing Monday morning, early on a Saturday – those are times I pick, though I also have the advantage of being in an earlier timezone than my users.

    “So you also do not (even) deactivate the BP-plugins?”

    I mostly do MU sites, but yeah. I’d just keep on going… (Do the instructions say to deactivate it? I can’t say I ever looked…)

    I tyr the auto-upgrades first, and then if needed (or if it’s a big upgrade) I do it manually. Much safer.

    “By the way, myself and some others had a white screen of death last upgrade. Not just just main blog, but all blogs, the moment I clicked the de-activate BuddyPress button. Apparently this could have been prevented by switching theme first”

    Yep. the theme is looking for BP and you turned it off. :) Kind of predictable, really.

    I did a post here about backups, mostly via ssh, if someone wants to give it a read-over.

    http://wpmututorials.com/basics/how-to-backup-wpmu/

    #57657
    Kim Gjerstad
    Participant

    Hello all,

    My setup:

    1. I’ve upgraded last week my MU from 2.8.5 to 2.8.6.

    2. Buddypress is version 1.1.2.

    I have a similar issue with user slugs that have a blank space converted to a dash in them.

    For example, this does not work:

    http://centres-sociaux.fr/members/dominique-garet/

    When I activate the compability mode, the new slug doesn’t work either:

    http://centres-sociaux.fr/members/dominique garet/

    Yet, with or without compability mode, alpha character slugs work just fine, like this:

    http://centres-sociaux.fr/members/kgjerstad/

    I also changed the user_nicename in wp_users to see if that had any effect, but it also failed to fix the issue:

    http://centres-sociaux.fr/members/dgaret/

    Any tips, or hints, would be greatly appreciated.

    PS. This is my first posting in the forums, so I take the opportunity to show my appreciation to this lively community and to the great features BP offers. Longlive the Open source communities!

    #57613
    David Lewis
    Participant

    Okay. I just started fresh. I completely deleted the entire website. All the files. I also completely deleted the database. I made a fresh database. I uploaded WPMU. Installed it. Then uploaded BuddyPress and activated it. And I followed the installation instructions to a “T”. So a complete virgin fresh install of WPMU 2.8.6 and BP 1.1.2. I made two users. And still… I cannot add friends. The busy icon on the button just spins forever and nothing happens. Completely at a loss here. Any ideas?!

    #57585
    grandin
    Member

    I have the same, or similar, issue.

    I’m started with WPMU 2.8.4, FR version, then did the automatic upgrade. I installed Buddypress, the default theme and the parent. When a user tries to activate his account, the go to this sort of URL http://ux-paris.com/wp-activate.php?key=7c9a743c9ff98355 which throws the following error: Fatal error: Call to undefined function bp_page_title() in /home1/thelayen/public_html/uxparis/wp-content/themes/bp-sn-parent/header.php on line 9.

    FWIW, in the Buddypress admin panel, it shows that “My current theme is not BP compatible”…but my current them is BP Default?

    Any ideas?

    #57161
    profitsbuzz
    Participant

    I have the same issue here, when I test by signing up for an account. However when I tried to activated it, I was not able to do so. Can anyone advice what I need to do in order for my new users to activate their account?

    Thanks.

    I am using BP1.1.1 and WPMU 2.8.5

    #56918
    @mercime
    Participant

    Hi Andrea_r, waiting for videos to your session/s at http://wordpress.tv/event/wordcamp-new-york/ :-)

    I tested your theme in a site under development.

    WPMU 2.8.5.2 + BP 1.1.2 + bbpress installed via BP one click

    Main site with MU Sitewide Tags Pages

    BuddyPress main site in blog-ID-2 at http://members.example.org/

    Thank you for the clean theme. Without looking at code, i.e., checking it out like a newbie who activated the theme, following are some quick notes:

    1. wp-admin-bar – Text (e.g. Org Members) of link to BuddyPress site ( http://members.example.com) shows up in backend (dashboard etc) but does not show up in front end. The link block is there and clickable to main BP site, but the text does not show up. Still, the wp-admin-bar shows correct links to main BP site, etc. throughout the site including sub-blogs.

    2. Footer widgets only showing up in only in blog areas – is this the intention?

    3. h1 – cannot find it anywhere in the theme. Need at least one h1 per Post or Page

    4. Main Nav – link to Forums was not generated to show BP main site nor other subblogs nor main site, while link to a newly activated “Events” plugin page was generated to show in the main nav across all sites. (the link to Forum shows up in this install when I use child theme)

    5. Main Nav – like the official bp-child theme, activating the theme in sub-blog for groups or individual members does not show correct links to main BP site features like member/group/blog directory. In order for one theme to be used throughout the site, conditional statement will be needed to show correct links to main BP site conjoined with respective blog’s navigation links.

    Quick scan in main BP site (blog_id_2) to see how theme works in different sections

    6. Members Section

    – directory page – 2 columns – ok

    – My own admin individual profile page – skeleton set up with 2 columns where in left column is avatar, options bar and user bar boxes. But there is a large space on the right side as if missing a 3rd column. Checked links in options bar resulted in two columns with links except the ff which has a missing left column – Edit Profile page, Change Avatar page

    – If I click on another member’s individual profile page – left column as two user bar boxes unlike the link to my profile which has the options bar and user bar. In addition, when I also am missing the left column with options/users boxes in Blogs link page, Friends link page, Groups link pages plus the Events link page is incorrect and goes to front page of site

    7. Groups Section

    – directory page – 2 columns – ok

    – Group individual page – skeleton set up with 2 columns – but there is a large space on the right side as if missing a 3rd column plus the page is missing all sub-navigations for Creating a Group, Creating forums etc

    That’s it for now. As mentioned above, didn’t look at codes “behind the scenes” at this point, only the functionality if newbie user activated it.

    Good luck :-)

    #56780
    Jeff Sayre
    Participant

    Since you have taken a WP install and turned it into a WPMU install, there would be no BP data to import from your original install. Thus, you will have no BP data when install and activate BP–other than your Admin account.

    Did you search the WPMU forums for instructions?

    https://mu.wordpress.org/search/upgrading+WP+to+WPMU?forums=1

    If so, as DJPaul says, each member will have to log in before their initial BP data set is created.

    #56573

    User and avatar information is stored in wp_signups before the account is activated, and it is moved into the user, usermeta, and xprofile tables upon activation.

    It would seem you’re experiencing a different issue than what you describe.

    For now I’m closing this and linking it to…

    https://buddypress.org/forums/topic/avatar-upload-issues?replies=1#post-28737

    @titeufpld, if you’d like me to reopen this topic for some reason, send me a PM.

    #56054
    ousep
    Participant

    Here’s what I’m trying to do…

    I’d like to hook into bp_after_registration_submit_buttons to run a query that will update wp_signups in the database.

    If that function does what i think it does, I would set ‘activated’ to the same as ‘registered’ and set ‘active’ to 1. I’m guessing there’s more involved, like copying the ‘meta’ to wp_usermeta, and also adding their details to wp_users.

    Now here’s the tricky bit: how do I hook into bp_after_registration_submit_buttons?

    And, how do I get _any_ identifying value for the user who’s just registered?

    #55665
    peterverkooijen
    Participant

    @Chouf1, the code is not for uppercasing; it’s making sure firstname and lastname are stored consistently in the different places where WP/WPMU/BP stores names.

    Why is it too much to ask for consistently, reliably stored firstname + lastname in the WordPress world? Uppercasing should be part that imho. It’s utterly ridiculous to have to do that in CSS. Is that even official CSS? Do all browsers support it?

    In most software for grownups firstname and lastname fields are at the top of the members/users table, part of the core of the application, the heart of member registration and management. In the WP/WPMU/BP world it’s a messy afterthought, stored halfheartedly in three or four different locations, in different ways, without any synchronization between them. Aaarrrggghhh.

    Before a WordPress user account is activated, it is stored in the wp_signups table; there’s a meta field storing various things. Have you checked if its that one?

    That’s one of the two places where the lowercase version of the name is stored. My code above updates names with uppercase in the usermeta fields.

    My question is which code stores them in xprofile or wp_signups. Where should I apply my nameize() function to get clean names in xprofile?

    Cleaning them up before they’re stored in wp_signups would do the trick as well, because I think the xprofile data is taken from there. I don’t think the wp_signup data is used for anything else later, so it has a lower priority to me.

    Edit: Of course I’m not trying to uppercase all chars of the name, just the first ones, as used to be custom in western culture. FYI, here’s the nameize function I use:

    function nameize($str,$a_char = array("'","-"," ")){
    //$str contains the complete raw name string
    //$a_char is an array containing the characters we use as separators for capitalization. If you don't pass anything, there are three in there as default.
    $string = strtolower($str);
    foreach ($a_char as $temp){
    $pos = strpos($string,$temp);
    if ($pos){
    //we are in the loop because we found one of the special characters in the array, so lets split it up into chunks and capitalize each one.
    $mend = '';
    $a_split = explode($temp,$string);
    foreach ($a_split as $temp2){
    //capitalize each portion of the string which was separated at a special character
    $mend .= ucfirst($temp2).$temp;
    }
    $string = substr($mend,0,-1);
    }
    }
    return ucfirst($string);
    }

    Edit2: The CSS solution only works on the first name. The last name still starts with lowercase. Any easy CSS trick for that? I don’t think so.

    Apparently the same CSS trick is used in this forum, which would explain why my “username” – cough, spit – is displayed as ‘Peterverkooijen’ instead of ‘peterverkooijen’ as I had entered it. Why is that kind of mess considered acceptable?

    #55653
    Paul Wong-Gibbs
    Keymaster

    Before a WordPress user account is activated, it is stored in the wp_signups table; there’s a meta field storing various things. Have you checked if its that one?

    BuddyPress doesn’t modify any WordPress tables or data. It does add a few entries to your _options though. The easiest way to “uninstall” BuddyPress is to drop the tables it creates when it installs. They usually start with “wp_bp_”.

    Very few WordPress plugins have a real “uninstall.” Most of them pollute the WordPress tables with their data and when you deactivate and delete that plugins files, their settings and data still remain in the database. It took me a while to get used to that too, coming from a world where if you don’t need something, you get rid of it; But it doesn’t hurt anything keeping it there, and it even helps sometimes if you decide to revisit a plugin that you deleted 6 months ago.

    In the coming weeks I may write a plugin to import existing blogs into the wp_bp_* tables, but the risk with that kind of thing is just like any other aggregator, it will be a very heavy routine that goes through all users, all blogs, all posts, and all comments, and feeds them into the BuddyPress tables for future use.

    #55370
    Brajesh Singh
    Participant

    hi korban

    I had worked on the same concept and came out with my own plugin.

    You can download it using the following link

    http://www.thinkinginwordpress.com/download/bp-auto-activate-user-and-blog2.zip

    Upload it to wp-content/plugins activate and it will remove the confirmation email.

    It works with buddypress 1.1.x .Please note it will not work with buddypress 1.0.3

    Hope it helps.

    thanks

    Brajesh

    #55237
    Jeff Sayre
    Participant

    You need to deactivate all BuddyPress-dependent plugins before you deactivate BuddyPress itself.

    Did you deactivate the bpPicture Album plugin before you deactivated BuddyPress? If not, then that is more than likely what caused your problem.

    Figured it out. To manually do this you need to go into your database and put this in your wp_sitemeta table under the field active_sitewide_plugins:

    a:2:{s:24:”buddypress/bp-loader.php”;i:1254779318;s:12:”bp-album.php”;i:1254851888;}

    What a given user would need to place in that particular sitemeta table record depends on what plugins they had activated. This is what you needed to do. It will not necessarily be what others would need to do.

    The best way to handle this issue is to temporarily move all your plugins out of /wp-content/plugins/ and then log back into WPMU’s backend as Site Admin. Refresh the page, logout, and then move the plugins back. Log back in and you should be good to go. Your plugins will be deactivated and ready to be reactivated.

    #55204
    outolumo
    Participant

    I just went through the default bp-sn-parent theme and harvested all the action hooks beginning with bp_ to a list. Could someone put it to the codex? This list could be useful for people developing their own BuddyPress themes. I hope I didn’t miss anything.

    Because these hooks appear in the default BuddyPress theme, some plugin developers might assume their existance in bp-themes. Therefore they should probably exist somewhere in the custom template files. Most of these are are fairly generic and could be filtered into existing themes (e.g. bp_head() could be filtered using wp_head() hook), assuming that the theme you are building on is properly saturated with hooks.

    Note that the optionsbar.php, userbar.php and plugin-template.php need to be added to your theme. I don’t know if they could be filtered.

    The notable exception being the search-login-bar and nav-items. IMO they shouldn’t be in the BuddyPress template at all. Better solution would be to have functions for search-box & login widget, and insert them to the template using tags for those. This would make them both more reusable – e.g. search-box could be re-used on search and 404 templates – and flexible, allowing to login box to appear separate from the search box. Likewise the nav-menu should be widgetized, i.e. made a function that can be called somewhere from the page.

    While not exactly a template tag issue, theme developers should be aware that the buddypress admin bar is by default activated at the wp_footer() as follows:

    add_action( ‘wp_footer’, ‘bp_core_admin_bar’, 8 );

    I’m gonna try placing the following to the functions.php:

    remove_action(‘wp_footer’, ‘bp_core_admin_bar’, 8);

    add_action( ‘i_want_it_here_tag’, ‘bp_core_admin_bar’, 8 );

    ====================================================

    header.php

    <?php do_action( ‘bp_head’ ) ?> (In the head section.)

    <?php do_action( ‘bp_before_search_login_bar’ ) ?>

    <?php do_action( ‘bp_login_bar_logged_out’ ) ?>

    <?php do_action( ‘bp_login_bar_logged_in’ ) ?>

    <?php do_action( ‘bp_search_login_bar’ ) ?>

    <?php do_action( ‘bp_after_search_login_bar’ ) ?>

    <?php do_action( ‘bp_before_header’ ) ?>

    <?php do_action( ‘bp_nav_items’ ); ?>

    <?php do_action( ‘bp_header’ ) ?>

    <?php do_action( ‘bp_after_header’ ) ?>

    <?php do_action( ‘bp_before_container’ ) ?>

    ====================================================

    footer.php

    <?php do_action( ‘bp_after_container’ ) ?>

    <?php do_action( ‘bp_before_footer’ ) ?>

    <?php do_action( ‘bp_footer’ ) ?>

    <?php do_action( ‘bp_after_footer’ ) ?>

    ====================================================

    Content wrappers: inside #container, but containing #content.

    index.php

    <?php do_action( ‘bp_before_blog_home’ ) ?>

    <?php do_action( ‘bp_after_blog_home’ ) ?>

    single.php

    <?php do_action( ‘bp_before_blog_single_post’ ) ?>

    <?php do_action( ‘bp_after_blog_single_post’ ) ?>

    404.php

    <?php do_action( ‘bp_before_404’ ) ?>

    <?php do_action( ‘bp_after_404’ ) ?>

    archive.php

    <?php do_action( ‘bp_before_archive’ ) ?>

    <?php do_action( ‘bp_after_archive’ ) ?>

    page.php

    <?php do_action( ‘bp_before_blog_page’ ) ?>

    <?php do_action( ‘bp_after_blog_page’ ) ?>

    attachment.php

    <?php do_action( ‘bp_before_attachment’ ) ?><

    <?php do_action( ‘bp_after_attachment’ ) ?>

    links.php

    <?php do_action( ‘bp_before_blog_links’ ) ?>

    <?php do_action( ‘bp_after_blog_links’ ) ?>

    search.php

    <?php do_action( ‘bp_before_blog_search’ ) ?>

    <?php do_action( ‘bp_after_blog_search’ ) ?>

    ====================================================

    Post wrappers – everything within the Loop. N.B. not every loop is listed here.

    index.php, single.php, archive.php, attachment.pgp, search.php

    <?php do_action( ‘bp_before_blog_post’ ) ?>

    <?php do_action( ‘bp_after_blog_post’ ) ?>

    ====================================================

    Some specific tags allowing to replace the entire loop:

    404.php

    <?php do_action( ‘bp_404’ ) ?>

    search.php

    <?php do_action( ‘bp_blog_post’ ) ?>

    ====================================================

    The mandatory Buddypress templates:

    optionsbar.php

    <?php do_action( ‘bp_before_options_bar’ ) ?>

    <?php do_action( ‘bp_inside_before_options_bar’ ) ?>

    <?php do_action( ‘bp_inside_after_options_bar’ ) ?>

    <?php do_action( ‘bp_after_options_bar’ ) ?>

    userbar.php

    <?php do_action( ‘bp_before_user_bar’ ) ?>

    <?php do_action( ‘bp_inside_before_user_bar’ ) ?>

    <?php do_action( ‘bp_inside_after_user_bar’ ) ?>

    <?php do_action( ‘bp_after_user_bar’ ) ?>

    plugin-template.php

    <?php do_action(‘bp_template_content_header’) ?>

    <?php do_action(‘bp_template_title’) ?>

    <?php do_action(‘bp_template_content’) ?>

    =================================

    Special templates:

    comments.php

    <?php do_action( ‘bp_before_blog_comment_list’ ) ?>

    <?php do_action( ‘bp_after_blog_comment_list’ ) ?>

    <?php do_action( ‘bp_before_blog_comment_form’ ) ?>

    <?php do_action( ‘bp_blog_comment_form’ ) ?>

    <?php do_action( ‘bp_after_blog_comment_form’ ) ?>

    searchform.php

    <?php do_action( ‘bp_before_blog_search_form’ ) ?>

    <?php do_action( ‘bp_blog_search_form’ ) ?>

    <?php do_action( ‘bp_after_blog_search_form’ ) ?>

    sidebar.php

    <?php do_action( ‘bp_before_blog_sidebar’ ) ?>

    <?php do_action( ‘bp_inside_before_blog_sidebar’ ) ?>

    <?php do_action( ‘bp_inside_after_blog_sidebar’ ) ?>

    <?php do_action( ‘bp_after_blog_sidebar’ ) ?>

    More details about how these tags are applied can be found by looking at the files in the bp-sn-parent -theme.

    #55007
    D’Arcy Norman
    Participant

    I’m seeing this, too. I just tried a fresh install of WPMU (2.8.4a) and tested Dashboard > Users > Add User (worked fine, email arrived intact).

    After installing and enabling BuddyPress 1.1.1, doing the same thing to Add User results in a borked email:

    Hi,
    You've been invited to join 'WPMU Test Blogs' at
    http://myserver.ca/wpmu as a subscriber.
    If you do not want to join this blog please ignore
    this email. This invitation will expire in a few days.

    Please click the folowing link to activate your user account:
    %s

    The last %s isn’t being substituted by the activation link.

    #54917

    In reply to: 'empty' group members

    Paul Wong-Gibbs
    Keymaster

    If you make a new group and join user(s) into it, does this problem reoccur? If it does, try to deactivate all plugins other than BuddyPress and make a new group and try again. If it doesn’t reoccur, then it’s a conflict with a plugin.

    I have read recently of problems with feedwordpress + BuddyPress, so there’s an incompatibility somewhere (if indeed feedwordpress works with WPMU).

    I’m inclined to thing this is a problem from the Groupblogs plugin, but let me know what happens when you test the above.

    #54854
    jazgold
    Participant

    hmmm i’m a little late on this, but i wrote a basic plugin for myself to do this. basically anyone who comes to your buddypress site will be directed to the login page, if they’re not already logged in. if they log in successfully, they will be taken to whatever page they had been trying to access ( i.e. not simply the backend editing area, or the front page ). to use it just paste it into a .php file, put it in your plugin folder, and activate

    //  whenever a page is loaded, make sure the user is logged in
    function catch_anons(){
    	global $user_ID;
    	get_currentuserinfo();
    		$login_page = get_bloginfo('url') .'/wp-login.php';
    			if ( '' == $user_ID && strrpos( curPageURL(), $login_page)===false ) {
    					$redirect = "?redirect_to=" . urlencode(curPageURL());
    				header( 'Location:' . $login_page . $redirect  );
    		die();
    			}
    }
    add_action('init','catch_anons'); 
    
    //once they log in,send them to their original destination
    function login(  ) {
    $first_stop = '/';       
    	//if there's no 'redirect_to' send them to "Home.php"
    	if ( $_REQUEST['redirect_to'] )
    		$first_stop =  $_REQUEST['redirect_to'];
    		header( 'Location:' . $first_stop );
    	die();
    }
    add_action('wp_login','login');
    
    //build the current URL  wish i could say where i grabbed this, a long time ago...
    
    function curPageURL() {
    	$pageURL = 'http';
    	if ($_SERVER["HTTPS"] == "on") {	$pageURL .= "s";	}
    		$pageURL .= "<img src="smileys/irritated.gif" width="" height="" alt=":/" title=":/" class="bbcode_smiley" />/";
    	if ($_SERVER["SERVER_PORT"] != "80") {
    		$pageURL .= $_SERVER["SERVER_NAME"]. "<img src="smileys/irritated.gif" width="" height="" alt=":" title=":" class="bbcode_smiley" />" . $_SERVER["SERVER_PORT"] . $_SERVER["REQUEST_URI"];
    	} else {
    		$pageURL .= $_SERVER["SERVER_NAME"].$_SERVER["REQUEST_URI"];
    		}
    return $pageURL;
    }
    #54612
    copgarden
    Participant

    Update:

    There are 2 places in the WPMU Dashboard an admin can add a new user. Further up in the Site Admin>Users menu, and further down in Users>Add New. Welcome Pack is only activated if a user is added from the Users>Add New menu. And as mentioned above, that is where the glitch occurs.

    In testing more thoroughly found the WPMU notifications work fine from both places in the Dashboard when BuddyPress is disabled. When BuddyPress is active the “Add New User” in WPMU develops the glitch as described above.

    #54495
    Gianfranco
    Participant

    @proceon

    A lot about what you’re trying to achive is said here: https://buddypress.org/forums/topic/new-theme-framework-and-exisiting-wp-themes

    Otherwise, I myself am trying to get a step by step procedure to integrate BuddyPress as a section of a “normal” website, that is not full BuddyPress based.

    So far, form my experiments with theaming and integrating I can say:

    1) Delete all the files from “bp-sn-parent” that are already in your WP Theme (header.php, footer.php, index.php, …). Leave just all sub-directories and “optionsbar.php”, “userbar.php”, “plugin-template.php”, “style.css.

    2) Copy this at the bottom of “header.php” (WP Theme):

    <?php if ( !bp_is_blog_page() && !bp_is_directory() && !bp_is_register_page() && !bp_is_activation_page() ) : ?>

    <?php locate_template( array( ‘userbar.php’ ), true ) /* Load the user navigation */ ?>

    <?php locate_template( array( ‘optionsbar.php’ ), true ) /* Load the currently displayed object navigation */ ?>

    <?php endif; ?>

    3) In the header (comments) of the “style.css” in “bp-sn-parent” theme write this:

    Template : your-wp-theme-name

    …so you make this theme a child of your WP Theme, right?

    4) Activate the “bp-sn-parent” theme in the backend, under “Site Admin/Themes”, then activate it under “Apperance/Themes”.

    This will be the theme ofor the whole site, but it’ll call all the WP theme templates when no BuddyPress functions are needed. It’s a reverse way of doing the integration. I think it’s better.

    This procedure makes a lot of what you need, I think. Like, it gets your WP Theme working as it should and it “calls” the BuddyPress into play only when needed.

    But, I need to warn you that I am still struggling with styling (or skinning) the BP theme.

    So, I am still on it. But maybe it was worthing sharing already what I got so far, so that other may take it from there.

    Hope it helps…

    #54446
    Gianfranco
    Participant

    I am trying to achieve the 3 layer approach suggested by outolumo, which looks ideal to me.

    I just got a serious inheritance problem…!

    Because I need to integrate BuddyPress in a section of a site and not having it run as a whole site, I am testing this set up:

    1) The original “WP Theme” as a parent (with just the code in post #2 from Andy, in “header.php”)

    2) The “bp-sn-parent” folder stripped out of reduntant files that are already in “WP theme”, keeping just BP folders and “optionsbar.php”, “plugin-template.php”, “userbar.php”, and “style.css”.

    Made this theme a child of WP Theme, declaring “Template: wp-theme” in the stylesheet, right?

    3) The “bb-default” theme for styling (skinning) and customization.

    I’ve declared “Template: bp-sn-parent” so that “bb-default” is a child of “bp-sn-parent”, which is a child of “wp-theme”.

    So:

    1)”wp-theme” is the parent.

    2) “bp-sn-parent” is the child of “wp-theme” (style.css declares: Template: wp-theme).

    3) “bb-default” is the child of “bp-sn-parent” (style.css declares: Template: bp-sn-parent).

    First problem:

    The “bb-default” theme is not showing up in the backend under “Site Admin/Themes”, so I cannot make it available in “Apperance/Themes” to activate it.

    If I put a blank “index.php” file in “bp-sn-parent”, than it does show up in the backend, so I can activate it. (Is that normal?)

    So, before activating the “bb-default” theme (which should refer to “bp-sn-parent” which should refer to “wp-theme”), I’ve edited the “style.css” in the “bb-default” theme to import the styles from “wp-theme” (because it styles the whole site) with this rule:


    @import
    url( ../wp-theme/style.css );

    The result is a that the homepage (normal site) is blank, and the BuddyPress section is there, but messed up and not skinned with “bb-default” styles, and only some styles from “wp-theme” are applied (the footer image is there, but not the header image).

    Now, if I go and I activate the “bp-sn-parent” theme, the homepage of the site shows up normally, and the BuddyPress section has some “bb-default” styles and got the header images from the “wp-theme” but not the footer image. And it’s preatty screwed up too.

    So, as you see I am trying to achieve this 3 layers set up, but as I said, something with inheritance is totally messed up.

    Does anybody have any insights on this. I am sure it could be useful for the whole community.

    Thanks.

    #54055
    pushi22le
    Participant

    I found this plugin https://wordpress.org/extend/plugins/remove-buddypress-adminbar/

    I also copied and edited the plugin to deactivate the bar just for guests. Here is the code:

    <?php

    /*

    Plugin Name: Remove BuddyPress AdminBar For Guests

    Plugin URI: http://blog.netweblogic.com/php/wordpress-php/remove-admin-bar-plugin/

    Description: This plugin removes the admin bar completely from the public area of the website just for guests. Can be used either as a normal or MU plugin.

    Author: NetWebLogic LLC

    Version: 1.2

    Author URI: http://blog.netweblogic.com

    */

    if ( !function_exists(‘remove_bp_adminbar_guests’) ) {

    function remove_bp_adminbar_guests() {

    if (!is_user_logged_in()) {

    remove_action( ‘wp_footer’, ‘bp_core_admin_bar’, 8 );

    remove_action( ‘wp_head’, ‘bp_core_admin_bar_css’, 1 );

    function bp_core_override_adminbar_css_perblog() {

    ?>

    <style type=”text/css”>body { padding-top: 0 !important; } #wp-admin-bar { display: none; }</style>

    <?php

    }

    add_action( ‘wp_footer’, ‘bp_core_override_adminbar_css’ );

    }

    }

    }

    // Start this plugin once all other plugins are fully loaded

    add_action( ‘plugins_loaded’, ‘remove_bp_adminbar_guests’ );

    ?>

    So the bloggers have two options, they can deactivate the bar only for guests or also for the registered users.

Viewing 25 results - 776 through 800 (of 903 total)
Skip to toolbar