Forum Replies Created
-
In reply to: bbpress 2.6.7 body class
Going to release 2.6.8 ASAP.
In reply to: HTML editor doesn’t appear on bbpress 2.6.7Going to release 2.6.8 today to fix this. Sorry everyone!
Hi @outkax 👋
The functionality you’re looking for does not currently exist.
The
bbp_get_template_part
filter exists to hook into this API and extend the template parts to attempt to locate, so it would be achievable with some custom code.In reply to: List Of ShortcodesSplit this topic off of the 7 year old one, so that the old one goes back into the pit of despair.
In reply to: Topic/Reply FormThis is the default behavior of bbPress. Unless a plugin already provides a simple modification of this behavior, the easiest way to customize this would be by overriding the
/bbpress/form-reply.php
template part in your WordPress child theme.In reply to: help please with importer wrong authorHi there. Sorry that you’re having trouble. What forum software are you importing from?
In reply to: bbPress 2.2.6 – Upgrade ForumsNo. There are no upgrades specific to 2.6.6.
If there’s a bubble telling you to run something, it’s only because the tool could not run automatically on its own for a previous version.
Usually this is because your site has more than 10k users, but it could also mean the upgrade simply failed for an unknown reason.
The upgrades are non-destructive. You should be able to run them anytime.
The Repair tools are intentionally destructive. They delete a bunch of invisible data and then recalculate it.
It’s wise to backup your data before running them, but you also really shouldn’t have to worry about them.
In reply to: Can AJAX be enabled for bbPress?Probably an issue with a plugin conflict or theme.
Standard troubleshooting rules apply. Deactivate one plugin at a time and switch to a WordPress Twenty Something theme until it starts working, then work backward until you identify what’s causing it.
This is likely related to some kind of server configuration issue.
Does this happen with a regular WordPress Post or Page?
In reply to: Custom type topic cardOla!
I’m so sorry, but I deleted your other topic (the one in English) because I thought it was an accidental duplicate.
If you’d be willing to repost it in English, I’ll be happy to try and help you out. 🙏
This is already fixed in bbPress and will be part of the next release.
These are just notices. There is nothing wrong or failing. They are annoying. I think misused in this situation. But it has been addressed.
In reply to: Any Way to Convert WordPress Comments to BBPressSome functionality similar to this is planned for bbPress 2.7.
It is plausible that plugin will be used for inspiration, though the final code will likely end up being completely rewritten/modernized/debugged.
It sounds like you no longer have the Keymaster forum role.
Be sure to update to the latest version of bbPress, and check your Users for any other Keymaster accounts that you don’t recognize.
In reply to: display views by topic?Topic views are not standard in bbPress.
By default, the problem with Views is they trigger database writes on pages that should only be performing database reads.
We’ve considered ways of circumventing this, but have never seriously attempted to build it.
Is there a simple fix for a non-programmer type guy?
You could try installing: https://wordpress.org/plugins/gd-bbpress-tools/
I forget if it offers it, but it does so much other stuff that maybe it will tide you over? 😁
In reply to: Changelog v 2.6.5?!Codex updated. Thanks for pointing that out.
In reply to: Ive deleted a user with the keymaster statutHey @gathero,
Sorry for this inconvenience. You definitely discovered a situation that the bbPress team has not really considered. It should not be possible to delete the last remaining Keymaster, just like you cannot delete the last remaining Administrator.
I’ll make sure this gets addressed in a future release of bbPress.
MySQL 8 removing support for zero dates is the problem.
WordPress is incompatible with
NO_ZERO_DATE
mode, but it being dropped entirely means these errors are going to pop up.See: https://bbpress.trac.wordpress.org/ticket/3354
Going to patch and fix for 2.6.6, likely for a release next week.
In reply to: Users Can Post Bad HTML ContentBasically all of the extra attributes you are allowing can be used to disrupt your design in some fashion.
style, class, align, height, width, etc…
In reply to: Random Replies being marked PendingIt would be awfully helpful if bbPress could email the admin when this happens, rather than the admin having to spot hidden posts
I would suggest starting with 2.6 instead. There are so many improvements since 2.5, you’ll want to make sure you have them all. The farther behind you’re working, is the more work you’ll end up needing to do later.
The code changes in your original post are all still pretty close to correct if you want to make paginated hierarchical replies work like Comments do. If you need more help, I can guide you here for the time being. Then maybe we can take that work and turn it around into getting it done for 2.7. What do ya say? 😄
In reply to: Clarification about searching mechanicsHey @gdragon, sorry for the trouble, but thanks for keeping up to date!
Is it possible that when you updated to 2.6 you ignored the Upgrade routines?
If so, you may want to try reinstalling bbPress 2.6.3, as a last minute fix went in after it was originally packaged.
https://downloads.wordpress.org/plugin/bbpress.2.6.3.zip
If I’m correct, then you will also want to consider running the database upgrades soon. Forums with over 10k users need to do it manually, in your Admin > Tools > Forums > Upgrades
In reply to: WordFence Security warningYou’re welcome. Sorry for the scare!
If we can’t see your forums, we can’t debug them.
You’ll need to make someone an account so they can login and browse around and see what you see. Screenshots simply aren’t enough to help anyone. We’ve gotta see the code, inspect it, and then recommend changes to improve it.
In reply to: WordFence Security warningEngagements.php received a last minute fix specifically for code that is running on WordPress.org. Your best bet is to simply ignore the warning and wait for 2.6.4 to be released next week.