Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'buddypress'

Viewing 25 results - 63,451 through 63,475 (of 69,044 total)
  • Author
    Search Results
  • #49999
    teros0805
    Participant

    Sorry to see nobodies felt the need to comment on this thread for a week friend. I’m having the same problem trying to figure this out. Without a fairly straightforward way to customize the default site page I’m going to be forced to look at alternatives to WPMU/Buddypress.

    I’m sure theres got to be a way – i’ve seen examples of some cool buddypress sites – but my dream of MU and Buddypress being even close to as easy and straightforward as WP is are fading fast. It seems, still, like this set up is very much a patched together affair.

    I don’t mind putting in some time…..Every script or combination of scripts has some learning curve. Maybe wordpress (just the blog) has spoiled me with its most excellent documentation and straightforward usage, styling, etc.. but I’ve been having drupal flashbacks for the last 24 hrs since trying to set up a WPMU/BP test site.

    #49998
    Roy McKenzie
    Participant

    Figured it out. Well, it kind of figured itself out. Thanks anyway!

    #49988
    Andy Peatling
    Keymaster

    There is a bug in WPMU 2.8.2 that will not allow site wide plugins to be deactivated:

    https://trac.mu.wordpress.org/ticket/1071

    #49987
    miketempleton
    Participant

    Any updates on this situation? I am in the same situation as Dansalmon, where I would like to have all member blogs under a subdirectory of their own.

    Today we are running a standard WP.org blog at http://www.domain.com and running WPMU to power http://blogs.domain.com in order to achieve this effect, but it means people can potentially have two logins. I would much rather prefer to move to BuddyPress and take advantage of all the other features, but the addresses for user blogs is the only thing that bothers me. I would prefer that they be indicated as such in the URL string.

    r-a-y
    Keymaster

    I experienced a similar problem as well.

    Did you edit a BuddyPress core file using a bpGroups function?

    You should let Burt Adsit know of your fix, so maybe he can provide a cleaner solution using his plugin instead of editing the core:

    https://buddypress.org/developers/burtadsit

    Try adding this to line 161 of /wp-content/mu-plugins/oci_bp_group_forums.php

    add_action( 'groups_create_group_step2_save', 'oci_bb_group_updated', 10, 1 );

    See if that does the same thing.

    #49985
    localwpmu
    Member

    This topic mentioned the same issue of not being able to deactivate buddypress 1.0.3 plugin after upgrade. https://buddypress.org/forums/topic/fatal-error-after-upgrading-to-wordpress-mu-282-and-buddypress-103

    Korhan Ekinci
    Participant

    ok, I had one member with user name “Korhan”, I guess I did this by mistake in the forum profile edit area and could not somehow change it back to “korhan”. So I went inside the database and changed it manually. Posting works now.

    I also changed all profile links in forums to buddypress /member/username way, so that there are no 2 places where users play with their profiles but just one and that should be buddypress profile pages.

    I know this is going off topic, but here is what I did so that others can use it. I use the looks-like-buddypress theme for my forums:

    I changed the logged-in.php file:

    <div id="logout-link">
    <?php bp_loggedinuser_avatar_thumbnail( 20, 20 ) ?> &nbsp;
    <?php bp_loggedinuser_link() ?>
    <?php bb_admin_link( 'before= / ' );?>
    / <?php bb_logout_link(); ?>
    </div>

    Also added the css

    #logout-link {
    float: right;
    }

    #logout-link img {
    vertical-align: middle;
    }

    This way the looks are the same as bp

    I also changed the sign-up page link to bp’s. I replaced the sign-up button in login-form.php with this:

    <input type="button" name="signup-submit" id="signup-submit" value="<?php _e( 'Sign Up', 'buddypress' ) ?>" onclick="location.href='<?php echo bp_signup_page() ?>'" />

    #49979
    José M. Villar
    Participant

    Nope, Im afraid there´s not a newer version.

    1.1 was coded by Andy himself, and there are no signs that it is going to be updated. He has made clear many times that its up to Buddypress community to continue with the update of Facebook connect plugin.

    If I had coding skills, I would have updated it a long time ago, but I am still busy understanding how BP works ! ;-(

    #49977
    José M. Villar
    Participant

    Very nice, congratulations !

    What about integrating bbPress stats ? For those who have bbP setups might come handy.

    #49975
    Michael Berra
    Participant

    I ALready created a ticket (although my english is bad and I not enough of a programmer to narrow down the problem…):

    https://trac.buddypress.org/ticket/865

    #49974
    Windhamdavid
    Participant

    Make sure you have the themes in the proper locationI haven’t been following these forums too closely recently and I haven’t seen this error, but I went straight up 2.7.1 to 2.8.1 then 2.8.2. try this.. make sure you’re not refreshing a ?action=”*&^^” page.. just the plugins.php, delete out of the mu-plugins folder. refresh.. you should see NO Buddypress. drop it in the regular plugins folder.. refresh and then ‘activate site wide’.

    #49972
    localwpmu
    Member

    I tried as per your suggestion but it doesn’t work. BuddyPress ver 1.0.3 still cannot be deactivated.

    After deleting the entire BuddyPress directory and refreshing the plugins panel, the plugin didn’t shows up (display blank) but the word “Deactivate” is still shown and upon putting the cursor over it, it is “www.mydomain.com/wp-admin/wpmu-sitewide-plugins.php?action=deactivate&plugin=buddypress/bp-loader.php&_wpnonce=1a9adedb1e”

    I tried on another domain with an upgrade of wpmu 2.7.1 to 2.8.2 followed by a fresh install of BuddyPress 1.0.3 and the same fatal error happened when I tried to deactivate BuddyPress in plugins panel. I did the same suggested recovery/resolution but the error persists.

    Any other approaches I can try? Thanks.

    #49971
    Windhamdavid
    Participant

    the fbc_get_avatar() error is from the facebook connect… it’s been addressed somewhere else in the forums. ..it’s been fixed. The spam.. the user “LnddMiles” is not just on buddypress sites, so it’s a spambot that looks for open registrations.

    You should add a captcha or math problem to your registration page to divert these.

    #49970
    Windhamdavid
    Participant

    I think that’s very nicely done! simple, effective, 300 lines…. publicly +1, forum +1, the api..maybe just some jquery flot

    #49969
    plrk
    Participant

    More specifically, I’m wondering:

    • Is it a good idea to add fancy graphs using the Google Maps API (each user would have to use their own API key, naturally)?
    • Should there be an option to display all or some of these graphs publicly, that is, not in the administration panel? If so, where and which?
    • What more graphs would you like? I’m thinking about adding Wire and Forum stats, good/bad?

    #49966
    Windhamdavid
    Participant

    delete the entire Buddypress directory, refresh you plugins panel… upload it again, get your BP 1.0.3 themes in place.. refresh plugins.. activate it. i too.. always forget to deactivate plugins for upgrades ;o

    lokers
    Participant

    ok, I’ve got temporary solution.

    File: wp-content/plugins/buddypress/bp-groups.php

    Line 1481: yous should have (inside function groups_create_group() / case 2:)

    after:

    do_action( ‘groups_create_group_step2_save’ );

    I’ve added this line:

    oci_bb_group_updated($group_obj->id);

    So it works, but i had to modify this file which I am not happy with. I guess there is another way of doing this properly. If anyone will find better solution, could you please let me know too?

    plrk
    Participant

    bbPress does not have any native ways to hide forums that should be hidden. You can do as I have done – installing a “blank” theme that redirects users to your main site, limiting users to use the built-in group forums functionality only – or you could install a bbPress plugin that hides forums from those that are not allowed to view them. There is such a plugin, intended specifically for buddypress users, but I can’t remember what it is called.

    lokers
    Participant

    Just to clarify. I am talking about plugin for buddypress to communicate with bbpress. And by saying forum is visible I mean forum created with this plugin on bbpress side is visible (but should inherit settings from group).

    #49946

    In reply to: bp-custom-php help

    r-a-y
    Keymaster

    You need to remove the “- ‘.BPLANG.'” suffix from the .po/.mo files in your bp-custom.php

    Use this:

    <?php
    define( 'BPLANG', 'mysite' );
    if ( file_exists( BP_PLUGIN_DIR . '/bp-languages/buddypress.mo' ) ) {
    load_textdomain( 'buddypress', BP_PLUGIN_DIR . '/bp-languages/buddypress.mo' );
    }
    ?>

    #49945

    In reply to: bp-custom-php help

    3612275
    Inactive

    I’m trying to do this as well, however, it’s not working. I have my buddypress.po and buddypress.mo in my bp-languages folder and I uploaded a new bp-custom.php to the /plugins/ folder however, from there how do I enable the new translation?

    I’m using:

    <?php
    define( 'BPLANG', 'mysite' );
    if ( file_exists( BP_PLUGIN_DIR . '/bp-languages/buddypress-' . BPLANG . '.mo' ) ) {
    load_textdomain( 'buddypress', BP_PLUGIN_DIR . '/bp-languages/buddypress-' . BPLANG . '.mo' );
    }
    ?>

    #49943

    In reply to: change default blog

    Lynn Owens
    Participant

    You guys are the best. Thanks for the time in answering the question. For the time being I have chosen a non-technical solution for the problem. I used domain mapping to set up the corporate blog on mysite.com and am using mysite.org as blogid_1 and my buddypress set up.

    It’s important to note that BuddyPress is an opensource project, just like all of the other WordPress related ones. That being said, if you find something isn’t working up to your expectations you are free to develop or contribute to the project to make it work how you wish. As it stands today, BuddyPress does a good job of keeping tidy and cleaning up after itself; better than most plugins in my opinion. The signups table is specific to MU and is a new addition, so you can expect it’s functionality to be misunderstood. When a user is deleted, the idea is that their signup remain in the signups table as proof of their previous registration. One could even argue that removing all user data is a bad idea in the event someone ever needs it later, say for law enforcement purposes.

    Regarding blocking spam registrations, read some articles about Twitter. Some analysts have said that nearly 50% of all registrations on Twitter are spammers. Crazy eh? There just isn’t a fool proof way to prevent it from happening unfortunately.

    Also, while none of the moderators are directly employed by Automattic, it’s about the best internship I think anyone in our respective businesses can hope for. We all do our best to represent Automattic and are here to help to the best of our abilities.

    If you can find a specific bug or flaw in how users are currently managed between BuddyPress and WordPress, you’re welcome to respond here or file ticket in the trac. If you feel your opinion warrants more attention you can message me privately if you’d like also, and I’d be happy to help further.

    #49941
    chibuzo_o
    Participant

    Hi,

    I have got the same problem. I tried upgrading Buddypress to 1.0.3 and got the same fatal error.

    I’ve tried replacing all the files in the plugin folder but that didn’t work.

    Someone help please!!!!

    #49940
    Rohan Kapoor
    Participant

    Sitewide is working now. I am running on the buddypress trunk (last updated yesterday) and it works for now, :P

    Should this get submitted to trac?

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