Does the plugin works with BuddyBoss Platform?
We do not support BuddyBoss Platform integration for any of our bbPress-related plugins.
Dev4Press plugins for bbPress right now all require bbPress 2.6.2 or newer version, and old 2.5 versions of bbPress are no longer supported! BuddyBoss uses very outdated bbPress 2.5.12 (from 2017), and the current bbPress version is 2.6.11 (as of September 2024), which means that Dev4Press plugins for bbPress will not allow activation with bbPress 2.5.x (and because of the old version, it will not be active with BuddyBoss also). On top of that, BuddyBoss has made significant changes to the bbPress they are using, so a lot of stuff is no longer compatible with the standalone bbPress plugin. Also, BuddyBoss uses BuddyPress 4.3, released in 2019 (the current standalone BuddyPress is 14.1.0 in September 2024), and again, their version of BuddyPress has significantly changed from the standalone BuddyPress, making the compatibility a considerable issue.
Even if BuddyBoss is updated to bbPress 2.6 or newer, we have no plans to support It with our plugins due to the changes they made to bbPress, making proper support impossible.
This FAQ will be updated when something changes with bbPress or BuddyBoss.
TLDR: Dev4Press plugins for bbPress can’t be used with the BuddyBoss platform.
Why plugin’s JavaScript files are not loaded?
All Dev4Press plugins and addons require jQuery. However, they will work only if the jQuery is loaded with WordPress’s proper Enqueue method. If you are replacing jQuery that comes with WordPress with some other version loaded from another location, my plugins will not function properly, and that goes the same for most of the other WordPress plugins that depend on the proper way for loading jQuery.
Does plugin works with WordPress MultiSite installations?
Yes. Each site in the network can activate and use the plugin.
Can I translate plugin to my language?
Yes. POT file is provided as a base for translation in the root folder for each plugin. Translation files should go into languages directory, and WordPress must be set to your language to load the file. As an alternative, translation file can go into wp-content/languages/plugins directory.
The file name for translated and compiled MO file must be the same as POT file with the addition of language code: {plugin-name}-{language-code}.mo.
You can check out this for translating plugins using POEdit program:
support.dev4press.com/kb/article/translating-plugins-or-themes-using-poedit
