Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'Hide Admin'

Viewing 25 results - 851 through 875 (of 908 total)
  • Author
    Search Results
  • #57379
    maburker
    Participant

    I am sorry the bp-core-adminbar.php

    #56682
    Brajesh Singh
    Participant

    hi

    This is a css problem.

    Put something like this in the theme css(which ever blog theme you are using)

    body {padding-top:28px !important;}

    and The top bar will no more hide the theme.

    Hope it helps.

    btw,you need to have adminbar css in all your themes in order to enable visibility of admin bar.The best way is use import url syntax of css and import adminbar.css from one theme to all the themes.

    #56548

    In reply to: what about bp-plugins?

    Xevo
    Participant

    You can hide the plugins panel in the administration area from your users and you can use plugincommander to choose which plugins should be activated for users and which shouldnt be.

    Personally I don’t see why you would make a plugin folder for a plugin. If every plugin started doing that, then we’d have a lot of plugin folders. :)

    #56312

    In reply to: Broken activity

    arghagain
    Participant

    OK, I saw this in bp-activity.php:

    /* Drop the old sitewide and user activity tables */

    $wpdb->query( “DROP TABLE IF EXISTS {$wpdb->base_prefix}bp_activity_user_activity” );

    $wpdb->query( “DROP TABLE IF EXISTS {$wpdb->base_prefix}bp_activity_sitewide” );

    And so I look in the db and saw there is no bp_activity_user_activity table, and there is no bp_activity_sitewide table. This means it’s a good thing since these got dropped.

    Though I saw this

    $sql[] = “CREATE TABLE {$bp->activity->table_name}

    but to my lack of knowledge of programming, I see this and think it’s bp_activity_something (but no idea)…

    Looked everywhere and I only saw this in db bp_activity_user_activity_cached. This table doesn’t look like it was created by

    $sql[] = “CREATE TABLE {$bp->activity->table_name}, but I could be wrong because I looked at the part under $sql[] = “CREATE TABLE {$bp->activity ->table_name} and saw similar rows get created and these rows are in my bp_activity_user_activity_cached table.

    For example, in bp-activity.php,

    function bp_activity_install() {

    global $wpdb, $bp;

    if ( !empty($wpdb->charset) )

    $charset_collate = “DEFAULT CHARACTER SET $wpdb->charset”;

    $sql[] = “CREATE TABLE {$bp->activity->table_name} (

    id bigint(20) NOT NULL AUTO_INCREMENT PRIMARY KEY,

    user_id bigint(20) NOT NULL,

    component_name varchar(75) NOT NULL,

    component_action varchar(75) NOT NULL,

    content longtext NOT NULL,

    primary_link varchar(150) NOT NULL,

    item_id varchar(75) NOT NULL,

    secondary_item_id varchar(75) NOT NULL,

    date_recorded datetime NOT NULL,

    hide_sitewide bool DEFAULT 0,

    KEY date_recorded (date_recorded),

    KEY user_id (user_id),

    KEY item_id (item_id),

    KEY component_name (component_name)

    ) {$charset_collate};”;

    require_once( ABSPATH . ‘wp-admin/upgrade-functions.php’ );

    dbDelta($sql);

    In my current db, table bp_activity_user_activity_cached has everything except hide_sitewide row. In my current db, table bp_activity_user_activity_cached has extra rows that function_bp_activity_install doesn’t have such as date_cached and is_private rows.

    Any suggestion? What rows should I add or remove? Am I looking at the right stuff?

    Looked like at the end of the function bp_activity_install(), it has require_once( ABSPATH . ‘wp-admin/upgrade-functions.php’ );

    dbDelta($sql);

    Maybe the upgrade-functions.php had not gone smoothly?

    #55615
    still giving
    Participant

    A dropdown admin bar, that hides itself, would be nice as a standard option.

    At the very least it dominates all theme design at present, at worst it interferes with the lay out of others themes.

    Added this to the trac for you as it’s a confirmed bug. I spent a few minutes wrestling with it and found that the posting mechanism is tied to the check_is_member function, even though is_site_admin is used to make the post-form visible.

    A quick fix would be to hide the post-form even for site admins, but I’d rather rebuild the access check to allow admins + group members to post on the group wire.

    stwc
    Participant

    WPMU 2.84, BP 1.1.2, subdir install upgraded with no issues from 1.1.1 to 1.1.2 using autoupdater.

    This seems like a bug and a fairly minor one, but just checking. If I’m logged in as admin, viewing a group that I don’t belong to, the Wire message box appears in that group for me, and I can type something in and hit submit, but nothing happens. No warning, and nothing appears on the Group’s wire.

    If I join the Group, the Wire message appears as expected.

    Preferred behaviour, I guess, would be to either hide the Wire message box and instead show a warning that I can’t post to the Wire unless I join the group (if that’s the intended functionality — I’m not 100% sure, which is why I’m asking here).

    #53310
    ryans149
    Participant

    Hey, thanks. You are great!!! I was looking for the same

    #53306
    Andy Peatling
    Keymaster

    In your wp-config.php add the line:

    define( ‘BP_DISABLE_ADMIN_BAR’, true );

    #53304
    Rahul Sonar
    Participant

    socialpreneur

    I didnt get a single one. can you give me any suggestion?

    Thanks

    #6769
    knight_
    Participant

    Hello,

    I’m hoping someone can help me with a major problems that I’m encountering with my BP installation.

    I’m running WordPress MU 2.8.4. and BuddyPress 1.0.3

    1) After registering, when a user gets the “Activate avatar” e-mail and clicks on the link they see their avatar. It’s uploaded just fine but the cropping tool is missing! So after proceeding you end up with the infamous bacl box. If you click on change avatar, this time it works fine and cropping tool functions properly.

    2) Another cropping tool problem. This time with groups. The group avatar is uploaded fine. The cropping tool functions fine. Once you click on “Crop Full Size and Save” a new page comes up with:

    Are you sure you want to do this?

    Please try again.

    You click on Please try again. and it takes you back. Same thing happens if you try again.

    If you skip this step and finish creating the group. Then go to admin->group avatar and upload and crop the avatar it works fine.

    3)Is the the abillity of users to delete their account disabled by default? If so how do I enable this? This is very important. I have seen it in another installation of BP.

    For example: http://bp-dev.org/members/MEMBERNAME/settings/delete-account

    However that page is missing in my installation but the code seems to be in the core files.

    4) How can I disable/remove the activity labels across the board that display “active X time ago”. Most users obviously want to hide their online status and don’t want others to see when they logged in and for how long. Ideally this would be a user defined setting but since it’s not, how can I disable this?

    Thanks.

    #53227
    takuya
    Participant

    There’re plenty ways! Search the plugins from Developer menu.

    #6751
    Rahul Sonar
    Participant

    Is there any way to hide this option for all users?

    http://i34.tinypic.com/2me7djn.jpg

    #53049

    In reply to: Hide Admin

    johnegg
    Participant

    Any update on this?

    #6600
    Chad Holden
    Participant

    I want to hide a specific member from everyone. It’s the member I used to create the admin for the forums. Name is forumadmin, so that doesn’t make much sense on a listing of hotels.

    #6591
    Jeff Sayre
    Participant

    Many people have been inquiring about privacy options in BuddyPress. Some of you are aware that I am currently coding a Privacy Component for BuddyPress. I decided that it is time to fill the community in on my component, providing more details and a timeline.

    My Privacy Component will be entering a private alpha early next week. After the alpha phase is complete, it will then be available as a public Beta. If it goes well, and Andy likes it, it may be included in the BP core for version 1.2. If you look at the BP roadmap, you will see that that is when privacy filtering is scheduled to be included in core.

    In this screen capture of one of the privacy setting screens, you can see that there are actually six user classification filters that can be chosen for each BP object. The sixth option, “Relationship Mapped”, is made available by a separate plugin which I’ll be releasing later. The default Privacy Component will offer five levels.

    My current estimated release date for the first public beta is the week of October 5. This date may change depending on the feedback from the alpha phase.

    More Details

    This is taken from the Privacy Component’s current readme.txt file:

    BPAz is a privacy control component for BuddyPress that provides a site’s users a mechanism with which to control who has access to which pieces of their personal data.

    == Description ==

    The BuddyPress Authorization component (also referred to as BPAz, BP-Authz, or BuddyPress Privacy Component) is a BuddyPress component that allows users fine, granular control over who has access to which pieces of their personal data. It provides this service by hooking into BuddyPress’ core functionality, thereby giving users the ability to control (grant or deny) access to each piece, or grouping of, their personal data.

    The term “auth” is often used interchangeably for authentication or authorization. There is significant difference in meaning between them. Authentication is not authorization. Authorization is not authentication. Authentication must come before authorization. Authentication is handled by WPMU, initially by the registration process and subsequently by the login script. Authorization deals with verifying and managing the access rights a given authenticated user has to certain objects.

    Because of this confusion, the process of authentication is now often referred to as A1, or AuthN, or simply Au. The process of authorization is now often referred to as A2, or AuthZ, or simply Az. Since authentication must come before authorization, the A1-A2 ordinality of the terms is evident. This also explains the alternate names BPAz and BP-Authz.

    BPAz deals with authorization by verifying and managing access rights an authenticated user has to other’s objects–although a user may choose to expose their data to non-logged in users as well.

    The core BuddyPress objects on which rights can be set:

    • xprofile fields
    • activity stream actions
    • friends list
    • groups list
    • messaging
    • blogs
    • wire
    • status updates

    The basic access levels configurable per object (some objects offer only a subset of these rights):

    • allow/deny anyone (globally public or globally private). This is accomplished by setting an object’s viewing rights to either “All Users” or “Only Me”
    • allow only “Logged in Users” to view a given object
    • allow only friends to view a given object
    • allow only a specific list of users to view a given object. This is also called per user access control. This is accomplished by setting an object’s viewing rights to “These Users Only” and then entering a comma-separated list of usernames (a member’s login name) in a textbox that becomes visible.

    NOTE: Per relationship-type access control is possible if you use my BuddyPress Relationship Mapping plugin. For instance, allow by friend, colleague, partner, client, customer, fan, etcetera.

    Site Administration of BuddyPress User Privacy Tools

    Site administrators have ultimate control and oversight over the configuration of BPAz’s features and functionality via an additional administration panel under the BuddyPress menu hierarchy. The BuddyPress Privacy Component is enabled by default for all object groupings. However, Site Administrators can disable user-configurable sitewide privacy, or even individual privacy control objects, by using the Privacy Settings administration panel. As the Site Administrator, you will always be able to see each user’s complete content. Users do not have any options to hide content from Site Administrators.

    #51822
    peterverkooijen
    Participant

    Yes, I already use wp-hide-dashboard. It’s a partial solution.

    Users still get the pushy wp-login every now and then, which is a problem because it also has a link to an ancient register/signup form that clashes with Buddypress.

    wp-admin/profile.php also is not whacked by wp-hide-dashboard.

    madloki
    Participant

    Hello folks!

    First: a really great plugin :)

    But i have some questions:

    1) Is it possible that user can register only ONE blog?

    2) Can i hide some widgets from guest? It´s not good when anyone can see what users are doing (side wide activy f.e.).

    3) I have read about the manjo gallery, an own user gallery would be great. Is there any news?

    4) How can i use the img tag in groups? I have installed the img-plugin for bbpress, but it doesn´t work in buddypress.

    5) The admin can limit the user mb-limit and upload limit. But the last doesn´t work. I can upload bigger files! Also it would be good if we could change the limit for different user (admin 25 MB f.e. is not so good :o)).

    Edit:

    1) I found this http://buddypress.org/forums/topic/only-one-blog-for-user and will try it, ok good. And the other questions? :p

    So long, many thanks from germany!

    Kind regards

    Markus

    #51782
    Jeff Sayre
    Participant

    @elemsee

    but it sounds as if your solution removes blogs from the bar altogether. We plan to make subscribers members of blogs that the Admins set up…

    You have BuddyPress installed, I assume. So why don’t you give it a try–disabled the blog tracking and see what happens. It does exactly what you’re looking for. It prevents your members (users) from being able to create their own blogs. It does not hide the existing Admin blogs from them.

    If you have more than one Admin-created blog, you can place additional buttons, or fancy menus, to those Admin-based blogs.

    Unless you change the default behavior, WPMU by default makes all new users subscribers to the primary site blog (Blog ID number 1), which is the Admin blog. If you try out my suggestion, you will see that the “Blog” button is still visible. It takes users to the Admin-created blog. Only the “Blogs” button disappears for sight as it is a link to all user-created blogs, not the Admin blog.

    #51562

    Easiest way would be to use the WPMU function is_site_admin() to determine if the currently logged in user is a site admin, and then hide the buttons accordingly in your template.

    Then, you can create a custom function in plugins/bp-custom.php to redirect a user if they try to access the group creation URL directly.

    r-a-y
    Keymaster

    I’m using a plugin called WP Hide Dashboard on the primary blog:

    https://wordpress.org/extend/plugins/wp-hide-dashboard/

    This hides mostly everything from a subscriber.

    Hope that helps!

    webatease
    Participant

    Gigya Socialize worked for my install… I’ve only tried myspace, facebook and twitter – but it authenticated me correctly and I was able to login to BuddyPress. Only issue I’m having is that each time you login with one of your social usernames, it creates a new username in WPMU/BuddyPress, as opposed to all tying to your one WPMU/BuddyPress account. This created havoc for me, since I want to use groups, and other permissions.

    At this point, I’m leaning towards limiting to just the Facebook login. Does anyone know if there is a way to hide/not allow login using the actual wordpress login, and ONLY use the login for Gigya Socialize? I/e allow users to go to wp-admin, but not give them the option to login using the user/pass – only letting them see the Gigya Socialize plugin.

    chrisk2020
    Participant

    Forgive me if this has been asked before I can’t find any relevant posts:

    Basically what I want to achieve is to move the functionality of elements from the secondary nav items of the buddybar, specifically Dashboard, New Post, Manage Posts, Manage Comments:

    And have them display for a Logged in User when they visit their own ‘My Blogs’ page in their profile page.

    So then I can remove/ hide the buddybar, direct new users to their profile page from where they can click the link to add a new post and access their blog admin.

    I want to remove the buddybar for integration/ design purposes and to me it seems most logical that a user would be able to maintain their blog from within buddypress having navigated to ‘My Blog’. (I will limit each user to one blog)

    #49782
    Mariusooms
    Participant

    There are other platforms and have tried a few myself. As new as the bp platform is, it is by far the quickest out of the box that enables much of what you need already (together with wpmu). However other platform might offer more fine grained control, but it comes with a hefty learning curve as the platform is simply more complex. The upside to bp’s less complex architecture makes it also easier to develop for.

    I’ll see if I can give some input on your requirements.

    The main feature is an easy and somewhat restrictive way to post content. The only thing girls can publish is pictures of outfits, and then tag the clothes (describe, tag, categorize…).

    It looks like you need a custom content type that omits the post message. Flutter allows you to create a specific post type. I haven’t tried it with wpmu. There is also a wpmu plugin called ‘toggle_meta_boxes’ which allows you to hide unneeded post boxes to make it super easy for your users to just upload content.

    We want to have some level of control here. BTW not all users can upload content.

    Since you only have one subject users post on I would recommend NOT giving every user a blog at sign up, but just let them post to the main blog. Keeps you in control over categories, tags, etc. Plus it lets you control the user level. I however you do want to give users a blog there are wpmu plugins which allow you to set blog defaults like categories, predefined pages and posts and such. Also you can make new blog users have an editor role rather than an admin role if you want to control what they can or can not do.

    The content published by everyone goes to the main page, same of today.

    This is done by buddypress through widgets or even custom loops if you are adventurous.

    No problem there.

    People con vote their fabs.

    I haven’t looked at this, but I imagine there would be a wp plugin which would let users vote on posts. If you can find a vote plugin that serves an RSS feed you could pull that into the bp user profile. EVen link it to the activity stream with a small custom plugin.

    When user is logged in, she sees the content of the girls she is following (not pictures of everyone, just pictures of the ones that inspire the user).

    In bp through making friends with other users you can follow the activity of your friends only. At the moment the activity stream is text only, afaik, but I think images in the activity stream is in the pipeline?

    User profile is built by the outfits she publishes

    The profile page shows the latest activity, blog posts, wire messages, etc. of the profiles user.

    and the outfits she favorites.

    This is the most dificult part, since I haven’t looked into it. Assuming you can find a good vote/favorite plugin it should be doable.

    You can search for/discover/subscribe to trends, types of clothes, styles, colors, people…

    This is where bp shines as the search is very well done. Combine it with bp_contents plugin which allows your users to tag themselve, groups, blog and add categories…your archiving possibilities are endless.

    Some pitfalls (already mentioned):

    Privacy controls, inappropriate content flagging (is coming in 1.1 though), it is still not an out of the box solution (however for you requirements there is none that I can think of).

    There are still even other approaches when I think about it, I would recommend wp and bp in a heartbeat. Especially since the backend of both are really solid. Plugins are installed and upgraded easily. It is a widely supported and growing platform and would not hesitate to recommend it to you.

    I hope this helps a little bit.

    #5854
    mlemberg
    Participant

    To me it seems odd, that site administrators are visible to other users. At my site I have two members named “Admin” and “Forum Admin”, Their roles goes without saying.

    But all my other members are regular users with regular names. Therefore it bothers me, that these two accounts show up in the members directory and the “Who’s online” widget.

    I would very much like the possibility to hide certain members from the directory, site wide activity and widgets, so that they can be sort of “silent watchers”.

    Any body else who’d like this feature

Viewing 25 results - 851 through 875 (of 908 total)
Skip to toolbar