Forum Replies Created
-
What plugin are you using to put the login at example.com/login instead of example.com/wp-login.php? It’s likely that this is involved in causing the redirect trouble.
It would help to debug if you could collect some information from your browser console. In Firefox, hit F12, and look for the Network tab (peut-être “Réseau” en français). Click the “XHR” tab, which will filter by AJAX requests only. Then, attempt to add a friend as you normally would. You should see a new request to
admin-ajax.phpin the developer tools, and if you click on it, you’ll see more information about the request: what code was sent back (200, 404, 500, etc), the response body, etc. Record this info, or take screenshots, and share them here.Hi @plumbingsuperstore – Oof, sorry to hear about the problems, but glad your hosting provider had a way to roll back.
BuddyPress doesn’t touch user credentials, so it’s highly unlikely that BuddyPress itself would be the cause of your admin creds not working after BP was installed. I’m guessing that either there’s some user error here, or there’s another plugin interfering with the process. To reiterate, logging into WP should be exactly the same before or after the activation of BP.
Regarding the 404 error when activating your account: When you install BuddyPress, it should create pages called Register and Activate. It sounds like this worked for Register (since you were able to register a new account), but didn’t for Activate. If you try this again, take careful note of the URLs you see in your browser when registering, the URL that appears in the activation email, and the URL you see in the browser after clicking the activation link. There could be a clue here.
One final tip: You can stay logged in as an admin in your browser and still test as another user. Open a private browsing window: Firefox https://support.mozilla.org/en-US/kb/private-browsing-use-firefox-without-history, Chrome https://support.google.com/chrome/answer/95464?co=GENIE.Platform%3DDesktop&hl=en, Safari https://www.macworld.com/article/1133941/software-web/safariprivate.html
Ah, so that is the issue. Something in your theme, or another one of your plugins, is causing the navigation to be rendered two times. If you’re able to switch to Twenty Sixteen or another default WP theme, you could verify that the theme is the culprit.
In the meantime, I’m not quite sure how to address the problem. Is it important for your purposes that
Homeisselectedin this view? If not, it may be possible to drop in a bit of JavaScript that’ll unselect it, which will probably cause the search to work again.I’d suggest starting a topic at https://bbpress.org/forums – bbPress is the software that is responsible for creating the index at /forums/, and the folks over there will probably be able to give better advice about how to limit what appears there.
Hi @ovizii – Changing to a separate theme just because of a single styling issue is a pretty big step. If you’re generally happy with the way your site looks and works, it may be worth putting a bit of time into solving the specific issue, rather than looking for a larger switch.
If you do want to change, BuddyPress now supports a feature called “theme compatibility”, which means that it works well in most WordPress themes – whether or not they have specific support for BuddyPress. A nice place to start is the WP default themes (Twenty Sixteen, etc), some of which are particularly well suited to running a BuddyPress site.
Can you say what you mean by “locked out”? Exactly what pages are you visiting, exactly what are you doing (typing user/pass, etc), and exactly what do you see?
Group descriptions are filtered at the time of saving, via
wp_filter_kses(), and at the time of display usingbp_groups_filter_kses(). https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-groups/bp-groups-filters.php#L35It seems like a bug that we do different things at the time of save vs the time of display, but there you have it.
I’d suggest removing the
groups_group_description_before_savefilter, replacing withbp_groups_filter_kses, and then filteringbp_groups_filter_ksesto add allowed tags (as @r-a-y describes above). https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-groups/bp-groups-filters.php?marks=117#L87Thanks for sharing the markup. So are there *two* separate
list-item-tabselements on the page? I don’t see aMembersnav item here.Yes, the
alphabeticalsort doesn’t require last_activity, which is why it probably caused it to work. In any case, I’m glad you’ve got it sorted out!Glad you got it working!
You can pay us back by coming back occasionally and answering a support question or two 🙂
@scribit – Thanks for following up. We are getting closer 🙂
Do you have any idea why the
homeelement has theselectedclass? Does this mean that, when you view the group nav tabs, both Home and Selected have the “current” styling? BuddyPress doesn’t do this out of the box, so I wonder if perhaps there’s something in your theme that’s causing it to happen. Figuring out what’s causing that extraselectedclass, and disabling it, would probably fix the problem you’ve described.It is also the case that this JavaScript is quite fragile. I wonder if we could use the body class or something like that as a more reliable way of deterimining which tab we’re looking at. On the other hand, the JS for the new, upcoming template packs (bp-nouveau) is totally different here, so maybe it’s not worth fixing.
Hi @Sander – Thanks for reporting this. It looks like a legitimate bug. I’ve opened a ticket to track it: https://buddypress.trac.wordpress.org/ticket/7631
While we try to figure out a way to make this work better, you can work around the issue by disabling autolink for the field in question. Dashboard > Users > Profile Fields > Edit, and look for the Autolink metabox at the right.
Thanks for the report, @onedevstudios. This sounds like it’s probably a bug. Could you please open a ticket at https://buddypress.trac.wordpress.org with detailed instructions to reproduce? Thanks!
> Should I give you access to my website? Or do you have a better understanding of the problem now?
Hi Naomi – I and other members of the site post here as volunteers, so please understand that there may not always be immediate feedback to your posts.
> I uploaded an image to the link you provided, the file is called “Comment_Overlap”
Can you please share a URL?
The following snippet, in your theme’s functions.php or your bp-custom.php file, will prevent users from leaving more than one top-level comment on a given activity item:
add_filter( 'bp_activity_can_comment', function( $can ) { global $activities_template; // Users who are already forbidden from commenting should still be forbidden. if ( ! $can ) { return $can; } // If the user has already posted to this activity item, disallow more posts. $activity_id = $activities_template->activity->id; $children = BP_Activity_Activity::get_child_comments( $activity_id ); foreach ( $children as $child ) { $activity = new BP_Activity_Activity( $child->id ); if ( bp_loggedin_user_id() == $activity->user_id ) { return false; } } return $can; } );I’m unable to test with the proprietary Magnum theme, but with the free version of Optimizer, I’m unable to reproduce the problem. Group member searches are working as expected: https://postimg.org/image/axag5nsjr/
Here’s the relevant part of BP’s JavaScript: https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-templates/bp-legacy/js/buddypress.js?marks=863#L848 The first thing to check is that your theme is actually requiring buddypress.js (or buddypress.min.js) out of the buddypress theme directory; if not, it’s possible you’re running an out-of-date version bundled with a theme or something. Then, you may need to deminimize (or set
define( 'SCRIPT_DEBUG', true );) to debug. Then, check to see whether this bit of script is actually able to find thesearch_termselement. It’s possible that your theme, or some other plugin, is modifying the markup so that the selectors or the element hierarchy has changed.Hi Naomi – Thanks for the additional details.
I’m afraid I still don’t understand what you mean by “the comment input box” and “the reply area”. Here’s what the activity commenting area looks like on Twenty Sixteen: https://postimg.org/image/yzra0j1h3/ I assume that “the comment input box” is the field at the bottom, just above the ‘post’ and ‘cancel’ buttons. But I’m unsure what in this screenshot represents “the reply area”, and I don’t see any overlap at a glance. If possible, perhaps you could upload a screenshot to a third-party service like https://postimg.org/ and drop the URL here, so that we could better understand the display problem.
The problem I am currently experiencing is that each unique user can make multiple comments on a single post. They should only have the capability to make 1 comment to each post.
And when a user makes a second comment (which they are not allowed to do) that’s when the malfunction occurs and the input box overlaps the reply box.
I’m unclear on what’s happening here. You say that users “are not allowed to” leave a second comment on a post, but I guess what you mean is that you don’t *want* them to be able to do it?
I don’t know of a ready-made plugin that would allow you to limit commenting in the way you’ve described. It would probably be possible to write a small bit of code that would make it work, but I’d need a clearer understanding of what you’re trying to accomplish. If I understand https://buddypress.org/support/topic/how-do-i-make-the-comment-button-read-only-in-the-activity-stream/#post-269197 correctly, you mean that users ought to be able to leave a single *top-level* reply to a given activity item, but they should be able to leave as many replies-to-comments as they want. Is that correct?
A few things to check:
1. After submitting the first page of the group creation process, is the group actually created in the database? Check Dashboard > Groups, or the
wp_bp_groupsdatabase table if you know how.2. Check your browser cookies to see if the
bp_new_group_idandbp_completed_create_stepscookies are set. If so, please share the details, especially the Domain and Path.3. If you have access to PHP error logs on your server, please check them for related errors. Otherwise, consider enabling
WP_DEBUGto see if anything relevant is shown after submitting the first step of the creation process.What theme are you using? I wonder if the JS that you’re using is out of sync with the search template.
I don’t have access to the proprietary ARMember plugin, so I can’t say anything about that.
Here’s one way to show arbitrary content in a BP user’s profile header:
add_action( 'bp_before_member_header_meta', function() { $user_id = bp_displayed_user_id(); echo 'Here is the badge for user ' . $user_id; } );You’ll need to use the
$user_idto fetch the ARMember badge and display it.See https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-templates/bp-legacy/buddypress/members/single/member-header.php for other hooks you could use instead of
bp_before_member_header_meta.Glad you tracked down the error – leading spaces are a huge headache in XML/RSS documents.
Whoa, this is a pretty obscure problem. Thank you very much for following up with your solution.
It looks, at a glance, like the LH Private BuddyPress plugin ought to be doing what you’re asking for. https://plugins.trac.wordpress.org/browser/lh-private-buddypress/trunk/lh-private-buddypress.php#L101
If it’s not working, it’s either because of an error in the plugin logic, or because something on your server or WP setup is interfering with the
redirect_toparameter.Can you share the format of the URL at various points of the process? For example, when visiting example.com/groups/my-private-group as a logged-out user, you should be redirected to:
example.com/wp-login.php?redirect_to=/groups/my-private-groupIf, after login, you’re being redirected back to wp-login.php, what is the format of the URL then?
What is the URL format of your BP/WP installation? Are you installed at the top level of a domain
example.comor in a subdirectoryexample.com/buddypress/?Looking more closely at your styles, the problem might be the width of your
#item-meta. Remove themargin-topdeclaration you entered before, and try this instead:#buddypress div#item-header div#item-meta { width: 200px; }Your next step is to start getting familiar with CSS 😀 https://developer.mozilla.org/en-US/docs/Learn/CSS/Introduction_to_CSS
What theme are you using? It’s possible that this problem is specific to the theme. Try on a default WordPress theme like Twenty Sixteen to be sure.
Can you share a screenshot of the “comment box” and the “reply box”? It’s unclear from your questions whether you’re talking about textareas or about buttons. Also, BP doesn’t have separate Comment and Reply functionality for activity items, which makes me think that this may be a conflict with another plugin.
