Replies
- Brajesh Singh on September 13, 2022 at 1:58 pm in reply to: [Resolved] Hide header on Settings, Visits, Activity and Notifications pages #46502
Hi Carsten,
In BuddyPress, only the part after the username is called component. The part that comes after component is called action.In your examples, ‘edit’, ‘change-cover-image’ etc are actions not component. ‘profile’ is the component in this case. so, you will need to exclude ‘profile’ is using the above code.
Regards
Brajesh - Brajesh Singh on September 13, 2022 at 9:42 am in reply to: [Resolved] Handling Acceptance Checkbox field from php? – BuddyPress Xprofile Custom Field #46496
Hi Richard,
Thank you for sharing.It looks good based on your use case. Earlier, I thought that you wanted users to accept the terms on a new page but I now see you wanted it differently.
I think the approach in second step is erroneous as it will add anyone visiting that page as someone who has accepted the terms even if they did not.
Regards
Brajesh Have you put the code in bp-custom.php? It won’t work from your theme’s functions.php
I will be testing later today after installing the plugin.Regards
brajesh- Brajesh Singh on September 13, 2022 at 8:56 am in reply to: [Resolved] Hide header on Settings, Visits, Activity and Notifications pages #46493
Hi Carsten.
The component is the slug that is being used after the user name. e.g ‘profile’, ‘groups’, ‘friends’ etc.Have you added change cover image as top level?
You can put any slugs in this array in the above code
array( 'activity', 'notifications', 'messages', 'settings' )as
array( 'activity', 'notifications', 'messages', 'settings', 'some-slug-with-dashes-and-string', 'some-other-slug' )and so on.
Regards
Brajesh - Brajesh Singh on September 13, 2022 at 8:53 am in reply to: how to add reach text field in a user profile #46491
Hi,
Thank you for the replies.1. For BuddyBoss core related questions, BuddyBoss is the authority and I will suggest checking with their support.
2/3. We did not add it in core as it is not the experience we are looking for. If we ever added an option like that, we will need to implement some kind of the fedeback mechanism to the user on the chars length. Without that, this only applies on save and is not very helpful for the end user.
Regards
Brajesh You may use the following code(Please test as I haven’t tested)
add_action( 'bp_follow_activity_loaded', function () { $bp = buddypress(); if ( empty( $bp->follow ) || empty( $bp->follow->activity ) || empty( $bp->follow->activity->module ) ) { return; } if ( ! method_exists( $bp->follow->activity->module, 'add_activity_directory_tab' ) ) { return; } remove_action( 'bp_before_activity_type_tab_favorites', array( $bp->follow->activity->module, 'add_activity_directory_tab' ) ); } );Regards
Brajesh- Brajesh Singh on September 13, 2022 at 8:49 am in reply to: [Resolved] Branded login 403 forbidden error #46489
Hi Tosin,
It seems your theme has some kind of login handling mechanism too(redirect etc) and that is conflicting with Branded Login. I will suggest looking into your theme and checking if you can disable that.Regards
Brajesh - Brajesh Singh on September 13, 2022 at 8:37 am in reply to: The BP Menus PERSONAL MENTIONS FAVOURITES FRIENDS GROUPS #46485
Hi Daniel,
I had a look.The plugin does filter on the delete link on user profile.
Here is the code for that
// let us apply our mod. if ( ( is_user_logged_in() && $activity->user_id == bp_loggedin_user_id() ) || is_super_admin() ) { return $del_link; }it simple enabled the delete link for user’s own activity or if the site admin is logged. It does not affect the link in any other way.
Regards
Brajesh Hi Tosin,
You may use the following css#activity-follow{ display:none;}If that does not work(may happen for some theme) you will need to ad the !important flag to enforce it.
Regards
Brajesh- Brajesh Singh on September 13, 2022 at 8:28 am in reply to: BuddyPress Custom Xprofile Fields (field type number_minmax) #46483
Hi Quint,
Thank you for bringing it.The problem is there is no standard consistent way specified.
Some of the field types in core have it as you have specified and some have it differently.
1. After Input fields
https://github.com/buddypress/buddypress/blob/master/src/bp-xprofile/classes/class-bp-xprofile-field-type-selectbox.php2. before input fields
https://github.com/buddypress/buddypress/blob/master/src/bp-xprofile/classes/class-bp-xprofile-field-type-datebox.phpThere are many field types with this inconsistency, so we don’t have a standard here.
I am willing to change as you have suggested but I am worried about its ipact on the existing installs.
Do you have suggestions to deal with that.Thank you
Brajesh