Search Results for 'Hide Admin'
-
AuthorSearch Results
-
December 10, 2009 at 10:27 pm #58439
In reply to: Group Wiki Plugin (not a release, but in progress)
D Cartwright
Participant@Boone Gorges
Initially I wanted to have the wiki pages privacy completely controlled by the group privacy level but unfortunately we have a need to be able to ‘unhide’ individual wiki pages so in the implementation we’re working on pages will be individually controlled via the group wiki admin page.
As stated above, I completely agree. Whilst the work we’re doing at the moment will involve mediawiki I think it’s highly likely that I’ll simultaneously (though at a much slower pace) work on something similar to you’re describing in your last post.
November 24, 2009 at 1:52 pm #57379maburker
ParticipantI am sorry the bp-core-adminbar.php
November 14, 2009 at 8:38 am #56682In reply to: Admin bar conflict with blog themes
Brajesh Singh
Participanthi
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.
November 12, 2009 at 3:11 pm #56548In reply to: what about bp-plugins?
Xevo
ParticipantYou 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.
November 9, 2009 at 9:41 pm #56312In reply to: Broken activity
arghagain
ParticipantOK, 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?
November 1, 2009 at 4:59 pm #55615In reply to: buddybar wont go away after deactivation
still giving
ParticipantA 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.
November 1, 2009 at 11:38 am #55601John James Jacoby
KeymasterAdded 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.
September 30, 2009 at 6:00 am #53310In reply to: Any way to hide admin menu of buddypress?
ryans149
ParticipantHey, thanks. You are great!!! I was looking for the same
September 30, 2009 at 5:07 am #53306In reply to: Any way to hide admin menu of buddypress?
Andy Peatling
KeymasterIn your wp-config.php add the line:
define( ‘BP_DISABLE_ADMIN_BAR’, true );
September 30, 2009 at 4:40 am #53304In reply to: Any way to hide admin menu of buddypress?
Rahul Sonar
Participantsocialpreneur
I didnt get a single one. can you give me any suggestion?
Thanks
September 29, 2009 at 9:35 am #53227In reply to: Any way to hide admin menu of buddypress?
takuya
ParticipantThere’re plenty ways! Search the plugins from Developer menu.
September 25, 2009 at 1:39 pm #53049In reply to: Hide Admin
johnegg
ParticipantAny update on this?
August 31, 2009 at 5:36 pm #51822In reply to: Replace WP profile edit with BP profile edit
peterverkooijen
ParticipantYes, 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.
August 30, 2009 at 9:27 pm #51782In reply to: Plugin request: Removing "create a blog" options
Jeff Sayre
Participantbut 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.
August 25, 2009 at 9:10 pm #51562In reply to: Only admin can create a group!
John James Jacoby
KeymasterEasiest 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.
August 18, 2009 at 1:30 am #51193r-a-y
KeymasterI’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!
August 10, 2009 at 9:01 pm #50862webatease
ParticipantGigya 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.
July 22, 2009 at 10:15 am #49782In reply to: Should we use WP/BP or another platform?
Mariusooms
ParticipantThere 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.
July 8, 2009 at 8:02 pm #48837In reply to: default to ‘just a username’
r-a-y
KeymasterHey Peter,
It’s safe, but when upgrading to the newest BP version, you’ll have to remember to make this change again.
Either that, or until some option in the admin area is made.
I’m using BeLogical’s fix plus a CSS hack to hide the “Create a Blog” field right now.
—
There is no voting system, Peter. Although you can leave a message on the trac:
https://trac.buddypress.org/ticket/835
You can login with your existing BP username and password there.
July 5, 2009 at 5:22 am #48556In reply to: Way to disable admin bar on certain themes?
r-a-y
KeymasterHi Tedmann,
There’s two ways to go about this:
(1) CSS route:
In your /wp-content/themes/carrington-mobile-1.0.2/style.css file, add this:
body {padding-top:0 !important;}
#wp-admin-bar {display:none !important;}(2) Theme functions.php route:
In your /wp-content/themes/carrington-mobile-1.0.2/functions.php file, add this:
remove_action( 'wp_footer', 'bp_core_admin_bar' );
remove_action( 'admin_footer', 'bp_core_admin_bar' );—
Option #1 will simply hide the admin bar from view, however it will still be loaded if you view the HTML source.
Option #2 will completely remove the admin bar from the HTML source.
Not completely 100% that code will work, but give it a shot and report back.
July 2, 2009 at 12:24 am #48393In reply to: Changing the Blogs Creation Function**
John James Jacoby
KeymasterJust read over your post again and you say you want to eliminate the entire backend? Off the top of my head, I don’t know if that’s possible.
Best way to do this would be to integrate the P2 theme into your user blogs.
Otherwise, I know there is a WPMU plugin out there to help limit the admin side bar’s available links. If you manually navigate to the page you can still get to them, but it hides the options from view.
June 19, 2009 at 4:53 pm #47786In reply to: Add admin bar in all Themes
3206013
InactiveHello,
I’ve tried to check that option “Hide admin bar for logged out users to (No) ” , where shoud I include wp_footer() in the themes ,
June 19, 2009 at 4:34 pm #47783In reply to: Add admin bar in all Themes
Burt Adsit
ParticipantIf it’s not showing on all your blogs then check the setting of: wpmu back end > BuddyPress > General Settings > Hide admin bar for logged out users?
If some themes are still not showing the admin bar then that means they are not written to calll wp_footer() in the theme itself.
June 16, 2009 at 8:04 pm #47609In reply to: What is the correct way to alter the admin-bar.css
21cdb
ParticipantAs mentioned above the solution is working for me. I also figured out a way to remove the original admin-bar.css out of the header. I’m not at work at the moment, so i can’t look it up and write it down here, but i will do so tomorrow!
One problem remains for me. In the admin-bar.css and also in my-admin-bar.css there is a padding-top width the height of the buddybar applied to the body of the page.
If i don’t use my-admin-bar.css and check the “hide adminbar for users that aren’t logged in” in the settings of the dashboard the padding-top isn’t applied to the body. However if i use my-admin-bar.css it gets loaded all the time and not only if a user is logged in. This implies that i always have an extra gap, because the padding si applied all the time!?
Any hints for this problem?
May 21, 2009 at 6:22 pm #45815In reply to: Showing members of private groups to non-members
eelambuddy
ParticipantIs there anyway I can hide the “group creation” option from the users? Basically, only admin can create the “groups”.
-
AuthorSearch Results