Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'buddypress'

Viewing 25 results - 62,526 through 62,550 (of 69,044 total)
  • Author
    Search Results
  • #52601
    Jeff Sayre
    Participant

    The answer is yes and no.

    The privacy component is designed to offer users a mechanism to assign access rights (viewing rights) to their various core BP object groupings. It is not designed to let users assign per-item access control to any and all objects. So, for instance as you suggest, at this stage a user will not be able to assign an individual image discrete access rights. Why? Because photos (album objects) are not part of BP’s current core.

    Please be advised that this component only provides the assignment of privacy levels to BP’s core object groupings. All 3rd-party components will need to code their own privacy control features–using this component as a model and tying into its access-control table.

    Remember that this is a first version Privacy Component, so new features will be added later.

    A little more about access control

    Typically, Access Control Lists and protocols focus on flexibly setting access rights to resources based on predefined roles (for example: site admin, group admin, moderator, editor, contributor, member, user). This type of access control is more often called, and more appropriately referred to as, role-based access control (RBAC). Role-based AC is necessary when two or more people are involved in the management, oversight, and even ownership of specific subsets of data. This group of people then need to be jointly authorized to perform certain functions.

    But BuddyPress is a user-centric platform where there are currently no-jointly owned or controlled subsets of data. Ignoring the overall Site Administrator, in BuddyPress, there is a one-to-one relationship between a given piece of data and a single owner of that data. Even groups (at this time) are owned and controlled by one user. Group Moderators are limited in their power and do not own anything.

    The core BP privacy component is what I am calling a light-weight ACL implementation. At some point it may make sense to offer a separate, full-fledged RBAC system but I’m guessing that only a few devs who truly understood such a system would take advantage of it.

    Offering privacy control on BuddyPress’ core component objects is more than sufficient.

    #52598
    Ezd
    Participant

    Jeff: Yeah i made a ticket as well here: https://trac.buddypress.org/ticket/1023#comment:6

    Looks like Andy already fixed them in the trunk. :)

    #52597

    In reply to: Upload avatar failed

    Jeff Sayre
    Participant

    This is a very old thread that has not seen any activity for 5 months until your post. BuddyPress has changed significantly during that time, so whatever was the OP’s issue it is more than likely not the same as your current issue. Also, this thread is marked as resolved so it will more than likely get passed over by most people.

    Please read this thread and then start a new post.

    #52596
    abcde666
    Participant

    good that the TRAC-ticket has been re-opened again:

    this issue is not about which browser you are using or hardware !

    https://trac.buddypress.org/ticket/1021#comment:3

    There is clearly something wrong with the mouse-over at the homepage of testbp.org !

    the mouse-over is behaving perfect and very fast at an individual user-blog at testbp.org

    #52594
    Anointed
    Participant

    Coming from an ‘elgg’ point of view, I’m curious if your privacy plugin is going to be similar.

    When I create any new item in elgg, be it an image/video/audio/post/etc.. I have the ability to assign the object to a given group at the time of creation.

    Meaning, if I upload a new picture, or a new blog post, I have a dropdown permission box where I can set the groups allowed to see the item. (I can select multiple groups if needed).

    One thing I absolutely love is I can assign the privacy settings to groups of users.

    For instance, I have multiple ‘friends’ groups, ‘coworkers/family/friends/etc’ so when I make a post, I can say that only ‘friends’ are allowed to see it. Or, if I am a member of different ‘groups’, I can assign the permission to members of the given group (that part is really cool)

    Basically the permission system is so extensive, that my profile page looks completely different depending upon the permissions of the user visiting my page. (I’ve even managed to take it to the level of custom styles/css on a ‘per permission’ basis)

    Of course I can edit permissions on any object after creation should I choose to edit it later.

    Is this type of system basically the same as what you are talking about?

    #52592
    Jeff Sayre
    Participant
    #52591
    Jeff Sayre
    Participant

    Here’s a one-page PDF that shows the 6 access control levels of BPAz:

    http://www.sayremedia.com/buddypress/BPAz_Access_Levels.pdf

    #52586
    Jeff Sayre
    Participant

    @jjj

    I had considered adding the ability to block a certain user or groups of users but then realized that the selections that are offered do in fact block groups of users by virtue of them not being able to view a given object. For example, if a particular user is bothering you, and they are not in your friends listing, you can make an object only viewable to friends. This, in essence, will block them.

    Possibly future versions of the component could enable the grouping of several filter options or even include the ability to filter out certain users. But suffice it to say that the first version offers plenty of options and flexibility.

    @Erich73

    Since forums are not a core-created object but in fact are objects pulled into BuddyPress from an outside plugin, BPAz will not offer a filtering option for forums. There are simply too many distinct objects that bbPress creates. It truly needs its own privacy filtering system. Therefore, it is up to bbPress to offer such privacy options or a 3rd-party bbPress developer.

    #52584
    abcde666
    Participant

    Hi Jeff,

    what about a Forum-privacy ?

    Not sure if this makes sense ?

    #52582

    Since you have an option to allow certain users, do you have an option to block certain users also? Or, can I allow/block specific users while also allowing logged in users/friends?

    Maybe I should just wait for the alpha. :D

    #52581
    Ezd
    Participant

    Jeff:

    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 (domain.com/designs/wpmu)

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

    No I made a clean install

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

    Yes. Login was working fine. When I installed buddypress I couldnt login from the buddybar login. It looks for wp-admin.php in the root instead of in the directory “designs/wpmu/” where wp-admin.php is located.

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

    1.1 beta

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

    No clean install

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

    Only Buddypress

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

    Standard that comes with buddypress

    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?

    bbpress 1.0.2

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

    When logging in from the buddybar it cant find wp-admin.php as its looking for the file in domain.com and not in the correct location which is domain.com/designs/wpmu where wp-admin.php is located.

    When clicking login I get the message “No input file specified.”

    I even tried making a clean install once again. Same problem with buddybar!

    #52579

    In reply to: forums in 1.1

    Mike
    Participant

    perfecto! had one *slight* mistake in that setup … i dumped everything into /plugins/buddypress/bp-forums/ … without the bbpress folder =P and yes, it was via zip, lol.

    #52575

    In reply to: forums in 1.1

    Paul Wong-Gibbs
    Keymaster

    I’m betting you installed via the zip file. You need to download bbpress and put it in /plugins/buddypress/bp-forums/bbpress/

    (not /plugins/buddypress/bp-forums/bbpress/bbpress/ !)

    #52574

    In reply to: forums in 1.1

    Paul Wong-Gibbs
    Keymaster

    And do you have a /plugins/buddypress/bp-forums/bbpress/bb-includes/class.bb-query.php?

    #52573
    Paul Wong-Gibbs
    Keymaster

    *If* you’ve even enabled BuddyPess, you need to copy or merge the functions.php from the standard BuddyPress theme into your custom theme.

    #52572
    abcde666
    Participant

    absolutely cool Jeff ! You are my Privacy-Hero !

    Thanks a lot for all your effort ! Looking forward to this.

    Erich

    #52571

    In reply to: forums in 1.1

    Mike
    Participant

    here ya go…

    [Wed Sep 16 13:05:18 2009] [error] [client xx.xxx.xxx.xx] PHP Warning: require_once(/var/www/vhosts/michaelkuhlmann.com/httpdocs/wp-content/plugins/buddypress/bp-forums/bbpress/bb-includes/class.bb-query.php) [function.require-once]: failed to open stream: No such file or directory in /var/www/vhosts/michaelkuhlmann.com/httpdocs/wp-content/plugins/buddypress/bp-forums/bp-forums-bbpress.php on line 20, referer: http://michaelkuhlmann.com/groups/holy-cow

    #52569
    Anointed
    Participant

    I believe that the first huge step towards each buddypress install having it’s ‘own’ members is now complete. In order to accomplish this, we needed to start out where each blog can have it’s own members.

    I just uploaded a new plugin to wpmudev.org that may be useful to you. I know many have complained about this.

    It allows people to register for an individual blog using the normal registration process. In WPMU all registrations are forwarded to wp-signup.php, so it is impossible for a visitor to register for only a sub-blog. This plugin overrides WPMU and restores the default WordPress registration page for sub-blogs (sub-blog.domain.com/wp-login.php?action=register).

    Features:

    * Compatible with plugins like Register Plus to control registrations.

    * You can edit the default user role sitewide (subscriber, author, etc.).

    * You can also control whether users can adjust their own blog registration settings.

    * If users can control their own registration settings, a menu with that option appears under Users->User Registrations.

    * Does not affect main blog. Registrations there are maintained at wp-signup.php.

    Check it out: http://wpmudev.org/project/wpmu-blog-registrations

    I would be curious to hear from the bp devs if this is the right plan of attack for laying the groundwork for individual blogs to have their own buddypress.

    My idea being that once we have ‘separated’ the wpmu members so each member actually registers and belongs to an individual blog, we can then start filtering the bp widgets to only show activity/members/groups/etc.. that belong to the blog which is displayed.

    #52567
    bpisimone
    Participant

    Great and important work for a framework like BuddyPress. Privacy is probably the most important thing for online things in general – people just have not realized that yet.

    I’ll be happy to test.

    #52564
    Jeff Sayre
    Participant

    You do not have the proper syntax for locate_template().

    Look here: https://trac.buddypress.org/changeset/1742/trunk

    #52563
    grosbouff
    Participant

    1.0.3…

    I would like to upgrade to 1.1 but it doesn’t work for me.

    Anyway; what’s wrong with this code ?

    Can’t find the solution.

    Hi guess it’s a problem with $classified_parent_slug/$classified_link…

    #52562
    Jeff Sayre
    Participant

    just remember not all our themes are that wide… =(

    Haha!

    Since the goal is to eventually have this component merged into BuddyPress core, its CSS is designed to work with BuddyPress’ default theme. It is up to each user to style their site the way they see fit. Anyone with CSS experience will have no problem doing that.

    #52560

    In reply to: Renamed the folder.

    Jeff Sayre
    Participant

    You changed the site’s URL.

    Read this thread.

    #52559

    In reply to: Private Profiles

    Greg
    Participant

    This is a little risky for a non-programmer, but here is some code that would replace the profile-loop.php file in the skeleton member theme. Note that this theme is deprecated in the new parent-child theme setup. It is also not a sophisticated privacy component like the one Jeff is working on. It simply omits everything except the base profile fieldset when a non-member views the profile.

    This is from my own installation, but I have removed some pieces (mostly formatting) to simplify things a bit. I haven’t tested it in the simplified form.

    It assumes that “Base” is the base profile group name you specified in the BP dashboard settings.

    <?php
    /*
    * /profile/profile-loop.php
    * This file loops through the profile field groups, and then each profile field to
    * display the profile information that a user has entered.
    *
    * Loaded by: 'profile/index.php' (via the xprofile_get_profile() template tag)
    */
    ?>
    <?php if ( bp_has_profile() ) : ?>

    <?php while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

    <?php if ( (bp_get_the_profile_group_name() == "Base") || ( is_user_logged_in() ) ) : ?>
    <div class="info-group">

    <?php if ( bp_group_has_fields() ) : ?>

    <h4><?php bp_the_profile_group_name() ?></h4>

    <table class="profile-fields">
    <?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>

    <?php if ( bp_field_has_data() ) : ?>

    <tr<?php bp_field_css_class() ?>>
    <td class="label">
    <?php bp_the_profile_field_name() ?>
    </td>
    <td class="data">
    <?php bp_the_profile_field_value() ?>
    </td>
    </tr>

    <?php endif; ?>

    <?php endwhile; ?>
    </table>

    <?php else : ?>

    <h4><?php bp_the_profile_group_name() ?></h4>

    No info yet.

    <?php endif; ?>

    </div>

    <?php endif; ?>

    <?php endwhile; ?>

    <?php if ( !is_user_logged_in() ) : ?>
    <p class="not-a-member">You need to log in to see full member profiles.</p>
    <?php endif; ?>

    <?php else: ?>

    <div id="message" class="info">
    <p><?php _e( 'Sorry, this person does not have a public profile.', 'buddypress' ) ?></p>
    </div>

    <?php endif;?>

    #52558
    gerikg
    Participant

    Jeff Sayre, great work, just remember not all our themes are that wide… =(

Viewing 25 results - 62,526 through 62,550 (of 69,044 total)
Skip to toolbar