Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'buddypress'

Viewing 25 results - 63,001 through 63,025 (of 69,044 total)
  • Author
    Search Results
  • #51334
    r-a-y
    Keymaster

    (I believe what I’m about to write is relatable to the topic at hand; if not, feel free to close the thread!)

    I’m just starting to grasp the whole concept of multi-sites.

    From what I’ve read, it’s exactly what I want to do.

    But I need some clarification.

    Here’s my setup, I have WPMU+BuddyPress installed in the root:

    hxxp://www.example.com (blog_id #1 should be shown here, including all its posts, categories and pages)

    I want all subsequent blogs to be created from

    hxxp://blogs.example.com

    So that new blogs will have a subdirectory under that subdomain.

    eg. hxxp://blogs.example.com/newuserblog/

    Single sign-on should work across the root and subdomain.

    From those that have responded to me on the WPMU forums, this should be possible with the multi-site plugin.

    Now for the BuddyPress questions!

    Okay, so let’s say I login to BuddyPress (which is installed in the root instance of MU) and I want to create a new blog from “My Account > Create a blog”, would BuddyPress be creating this new blog under the new Site instance (eg. the subdomain Site – blogs.example.com? This is what I would want to do. I’m guessing this would require some core hacking.

    Also, if I go to hxxp://www.example.com/blogs, would this show blogs from the blogs.example.com subdomain?

    Thanks for reading! Hope to hear some feedback!

    Jeff Sayre
    Participant

    The fact that, as you say, “everything works lovely” when you switch to the bp-default theme, indicates that BuddyPress is functioning properly. So, you have an issue with your custom theme.

    Any WP theme will work as a BP home theme as long as some additional files are included. With v1.1 of BP, basically the version you downloaded from trunk, BP switches to a parent/child theme architecture. So, you need to make sure the custom theme you are using can function as a parent theme.

    Look at the various files in the BP parent theme — bp-sn-framework. My guess is that your custom theme is missing many of those files.

    More information of the new parent/child theme architecture: https://buddypress.org/forums/topic/details-about-the-new-theme-architecture

    #51326
    Paul Wong-Gibbs
    Keymaster

    If you can wait maybe a couple of weeks to a month for BuddyPress 1.1, you’ll be glad to learn that BuddyPress 1.1. won’t use XMLRPC anymore.

    #51317
    augustovilarim
    Participant

    Hi,

    I have the same problem

    1. Which version of WPMU are you running?

    2.8.4a

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

    directory

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

    subdirectory

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

    NO

    5. Was WPMU functioning properly before installing/upgrading BuddyPress?

    Yes

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

    1.0.3

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

    NO

    8. Do you have any plugins other than BuddyPress installed and activated?

    NO

    9. Are you using the standard BuddyPress themes or customized themes?

    Standard

    10. Have you modified the core files in any way?

    NO

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

    NO

    12. If running bbPress, which version?

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

    I don’t know how to get that.

    Only the first page and admin area works… all others pages, like blogs, users, profile, etc shows:

    Not Found

    The requested URL /comunidade/blog was not found on this server.

    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

    #51306
    David Lewis
    Participant

    Yes, a media library / manager makes more sense… with wire integration and bulk uploading hopefully. Now… if a user has not just a BP Profile but also a Blog… they would then have two media libraries… their WordPress Media Library and their BuddyPress Media Library. But I guess that makes sense. The Blog is almost like another world. Right?

    #51305
    Jeff Sayre
    Participant

    @boinker

    That is fine. I’ll set this topic to “not a support question” and we’ll see if anyone else has some ideas that may help.

    #51303
    4041799
    Inactive

    Hi Jeff.

    I’ve already contacted with WP Remix theme.

    Nevertheless, I post here because maybe someone that has WP Remix too can help me with my issue, it’s not possible?

    Thanks in advance.

    #51301
    Jeff Sayre
    Participant

    WP Remix is a premium theme. You will need to go ask the 3rd-party developers of that theme if and when they plan on offering BuddyPress support to their themes. You’ve paid money to them, they should help you.

    I’m setting this to resolved as it is an issue with a 3rd-party theme and not BuddyPress.

    #51300
    Jomark
    Participant

    Here’s my first running Buddypress site, http://piyesta.com/

    It is a social networking and web tv in one kind of site.

    #51298
    Jeff Sayre
    Participant

    If you look at the roadmap, there is no mention of an photo album (or gallery) plugin. That does not mean it will not happen, it just means that it is not a priority up through v1.4. It also does not mean it will not happen before v1.4.

    As with all open source projects, community contribution can significantly drive a project’s evolution. If Manoj, or someone else, comes up with what Andy (and the community) believes is an acceptable photo album component, it could get merged into BP core. Will that happen before v1.4? Will that happen at all?

    Right now, Manoj’s plugin is a strong candidate. But, it does have a ways to go. In speaking with Manoj, he has said that he is waiting for v1.1 to come out before he upgrades and improves his plugin. That makes sense.

    I have also discussed with Manoj the desirability to evolve his plugin into an overall media plugin–not just for photos. I personally believe that having a photo album plugin as a core component is of limited use in this day and age. Any core BP component, in my opinion, should offer as wide of a range of services as is practical. Here is what I said in another thread:

    It would be nice to see an option to upload other media types as well. People not only have photos, but video, audio, text, pdf, and other document formats that could all be organized around the concept of media.

    An album, then, would be a user’s place to add all the media types that they wished to share and organize. There could be sub-albums with an option to group by date, by media type, or by category or tag.

    #51288

    In reply to: Forum Integration…

    Peter Jeshua
    Participant

    Okay… I re-uploaded the BuddyPress plugin. Maybe I was out of sequence where I did bbPress last instead of the BuddyPress plugin last on my install? Who knows, but now the elusive “Forums Setup” is showing up where it should in my Dashboard.

    #51287

    In reply to: Forum Integration…

    Peter Jeshua
    Participant

    I have bbPress installed here: http://students.expression.edu/forums. I’m trying to integrate into BuddyPress. Where is “Forums Setup”? It’s absolutely not under my Site Admin sidebar in the dashboard for BuddyPress.

    #51285
    arghagain
    Participant

    OK, I have tested all methods. I even deactivated buddypress plugin, remove all plugins, and then sign up a test user with just wpmu, when did this, wpmu set privacy option for blog correctly, but right after I activate buddypress again, I saw the same user I just had created with wpmu earlier – the privacy went private again and not set as public.

    This makes me think that wpmu 2.8.4a is conflicting with buddypress 1.0.3. Maybe buddypress 1.0.3 is trying to change the privacy from wpmu 2.8.4a. Since none of the plugins I installed is conflicting with either buddypress 1.0.3 or wpmu 2.8.4a at all. So this must be the problem of buddypress 1.0.3.

    Can anyone help me confirm this problem? Or it’s me that the only one who has this problem? Thanks…

    #51284

    In reply to: Blog-Bug?

    Jeff Sayre
    Participant

    Up until an hour ago, this thread had not seen any activity for over 7 months. There have been many significant changes to the BP codebase since then. So, whatever issues the OP may have had will surely not apply to the current BP version.

    Arghagain, please read this thread for your information.

    I’m closing this thread as it is too old to be of use for additional discussion.

    #51277

    In reply to: Blog-Bug?

    arghagain
    Participant

    Upon looking to see if anyone has the same issue as me, I found this thread. Here is my thread https://buddypress.org/forums/topic/sitewide-activity-and-sitewide-post-problems

    Have anyone finally fixes this yet?

    My issue? New users sign up, their blog’s privacy is set to private even though in sign up page they set it to public. After first time log in, users can set the blog to public privacy again. It’s bothering me when blog is not public even though users want it to be when first sign up, this means when they write a blog post, it will not appear in sitewide posts widget! Also when other users visit a member that has private blog, there will be an error says that “[membername] has not created any public blog.”

    I’m using buddypress 1.0.3 and wpmu 2.8.4a

    #51276
    peterverkooijen
    Participant

    To autogenerate a temporary username put this function in bp-custom.php:

    function randomusername() {
    $length = 10; //length of string
    $start = 65; //Where to start from on ascii table
    $end = 90; //where to end on the table

    for ($k = 0; $k < $length; $k++){
    $randomname .= strtolower(chr(round(rand($start, $end))));
    }

    return $randomname;

    }

    Make this edit to the username input field on the form (hacking core file, should become easier in version 1.1):

    <input name="user_name" type="text" id="user_name" value="'.$user_name = randomusername().'" maxlength="50" />

    Test it if you want; you’ll see a random string in the username field that will be replace by the autogenerated username based on fullname on activation.

    You can hide the username field on the signup form, without getting error messages for not giving it proper TLC, by using this CSS trick.

    That requires another core file hack, since you need to add a id like username-form-field. Again, should become easier in version 1.1.

    My registration form is now:

    Name:

    Email address:

    And that’s it! Everything works. Full name is available as first and/or last name. The URL is the full name lower case without spaces. :-)

    Only thing left to do is clean up the email messages etc. that still mention the username…

    #51274
    r-a-y
    Keymaster

    I’ve already done this and the custom language file works wonders!

    Although you’ll have to learn the lingo all you mo-po’s out there! (bad joke, but anyway!)

    #51273

    In the current stable version of BuddyPress (1.0.3) changing the root blog from 1 to anything else still works in a few funky ways. There is a proposed fix for this (from me) in the trac but it is pending more bug fixes for 1.0.4 (which may get trumped by 1.1 at this rate.)

    Basically what I imagine is happening, is that when users sign up, they are given access to the dashboard blog like you specify, but they are given the contributor rights to blog_id = 1 because BuddyPress assumes “1” instead of BP_ROOT_BLOG.

    Basically, you’re stuck for the time being. You can apply my proposed fix but it’s pending testing and review so I’d suggest not using it live if you can help it.

    #51272

    In reply to: User points

    Paul Wong-Gibbs
    Keymaster

    Just to give a heads-up, after some thought, the next version of Achievements released will be for BuddyPress v1.1, so I have to wait for 1.1 to come out first.

    Not sure how much time that gives me so don’t want to make any promises about new features :)

    #51270
    peterverkooijen
    Participant

    Temporary solution how to customize registration form until 1.1 arrives, FYI and my own reference:

    Changed this line in function bp_show_register_page() in functions.php in my template:

    require ( BP_PLUGIN_DIR . '/bp-core/bp-core-signup.php' );

    to

    require ( 'custom-signup.php' );

    Copied bp-core-signup.php to the template folder, renamed to custom-signup.php.

    Go customize! :-)

    Unfortunately the custom fields are generated by yet another core function:

    do_action( 'signup_extra_fields', $errors );

    This action is associated with the function xprofile_add_signup_fields in bp-xprofile/bp-xprofile-signup.php.

    Copied the function to bp-custom.php, renamed action and function to custom_signup_extra_fields and custom_xprofile_add_signup_fields.

    Used this CSS trick to hide the avatar upload. Will use the same trick to hide the username field.

    #51268
    arghagain
    Participant

    OK, I figured the problem out but have no answer. After upgrade to wpmu 2.8.4a from 2.8.2 using buddypress 1.0.3, I noticed that when new users sign up, even though they apply for public privacy at the sign up page, when logged in, their blogs aren’t public, and as a test member, I have to go to settings >> privacy >> and choose a radio button for public privacy again, and afterward it works.

    Seem to me the sign up page did not allow public privacy even though members wanted that option!

    Any idea how to fix this?

    #51266
    r-a-y
    Keymaster

    I’ve noticed that you have an add_action only when WPMU activates a user… you should also do a check when someone tries to change the full name via BuddyPress – “My Account > Profile > Edit Profile”.

    Not sure what the action would be for that.

    peterverkooijen
    Participant

    This is the function that the regular wpmu registration process uses to add the user to wp_usermeta:

    function update_usermeta( $user_id, $meta_key, $meta_value ) {
    global $wpdb;
    if ( !is_numeric( $user_id ) )
    return false;
    $meta_key = preg_replace('|[^a-z0-9_]|i', '', $meta_key);

    /** @todo Might need fix because usermeta data is assumed to be already escaped */
    if ( is_string($meta_value) )
    $meta_value = stripslashes($meta_value);
    $meta_value = maybe_serialize($meta_value);

    if (empty($meta_value)) {
    return delete_usermeta($user_id, $meta_key);
    }

    $cur = $wpdb->get_row( $wpdb->prepare("SELECT * FROM $wpdb->usermeta WHERE user_id = %d AND meta_key = %s", $user_id, $meta_key) );
    if ( !$cur )
    $wpdb->insert($wpdb->usermeta, compact('user_id', 'meta_key', 'meta_value') );
    else if ( $cur->meta_value != $meta_value )
    $wpdb->update($wpdb->usermeta, compact('meta_value'), compact('user_id', 'meta_key') );
    else
    return false;

    wp_cache_delete($user_id, 'users');

    return true;
    }

    Is this function also used by Buddypress or does Buddypress replace it with something else?

    Where do meta_key and meta_value come from? Data from Buddypress xprofile field_1 is not included at this point…

    What would happen if I just added $bp as global? Trying that now… EDIT: Does nothing.

    I see xprofile_sync_wp_profile() uses this same function….

    #51254
    Jeff Sayre
    Participant
    #51252
    Jeff Sayre
    Participant

    @morgenvrij

    We need more detailed information about your setup. Please start a new thread by posting your issue and including answers to these questions.

Viewing 25 results - 63,001 through 63,025 (of 69,044 total)
Skip to toolbar