POT file for this plugin includes duplicate strings with different contexts, but POEditor currently doesn’t check for context to determine if the string is valid, it just checks for string duplicates, regardless of context. Until that is fixed, POEditor can’t be used to edit translations for this plugin. We have opened ticked with POEditor for them to properly support duplicate strings with different contexts, and hopefully, they will support that soon.
All Dev4Press plugins and addons require jQuery. But, they will work only if the jQuery is loaded with the WordPress proper Enqueue method. If you are replacing jQuery that comes with WordPress with some other version loaded from other 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.
Errors like this point to the problem with the plugin installation process when additional database tables need to be created. If that has not happened, it points to the problem with database access or something else related to the database server, but it is might be simply WordPress related issues preventing the normal update.
To check this out, open bbPress Toolbox menu -> Tools -> Recheck and Update. This panel will recheck and recreate tables in possible. If not, you will see the error messages. If that happens, you need to create tables manually (via phpMyAdmin, for instance). Here is the SQL schema for all 3 database tables plugin needs: Database Schema.
Before you go on, make sure you have configured the plugin properly. Check out this article for more information.
To confirm that topic tracking for users is working (new topics, unread topics, and new replies), you need two user accounts: one to create a new topic, and the second account to visit the forum with the new topic to get to see the mark for ‘new‘.
If it is not working, check if the database tables are created during the update. Table name is ‘wp_gdbbx_tracker‘. You can run Tools -> Recheck and Update to make sure all is OK.
No. WordPress Media Library has no options or controls to limit access to use of files based on the user role. Also, all files uploaded through Media Library are publically accessible via the URL. WordPress doesn’t have any mechanism for limiting access to files in media library.
In bbPress, only some user roles are permitted to post unrestricted HTML content. Other users can only use some basic set of HTML tags, and tags like UL, LI, DIV… will not work, and bbPress will save them as text, not HTML. Because of that, when you quote complex HTML content, tags normally not supported will be displayed as text, not HTML.
To fix this, you need to allow all user roles to use the expanded set of HTML tags. And to do that, open the GD bbPress Toolbox Pro Settings -> Various Tweaks -> Expand KSES allowed HTML tags and attributes -> Allowed tags list. Select box there have 3 options, first one is default bbPress set of HTML tags, and the other two include a wide range of supported HTML tags. You need to switch this option to second or third option.
If you set the plugin to use FontAwesome icons for attachment icons and for the forum topic icons (for privacy and other things), plugin will load FontAwesome icons font from CDN. You can disable FontAwesome from loading from plugin Settings Panel -> JS/CSS Files -> CSS Files Loading -> FontAwesome. Also, make sure you switch to use images as icons from plugin Settings Panel -> Standard -> Icons -> For Icons Use -> Images.
Yes. You can nest BBCodes as long as they are different types. You can have UL BBCode and inside it, you can have LI BBCodes.
And No. You can’t nest the same type of BBCodes. You can’t have UL inside another UL. Ordered or unordered list in HTML is allowed, and you can have UL, inside it several LI tags, and in those LI tags, you can have another UL. This will not work in WordPress, and BBCodes written like that will also fail to render properly. This will not change until WordPress fixes the issue.
There are few reasons for BBCodes not working:
- You have disabled BBCodes in the plugin.
- You have disabled some of the BBCodes in the plugin.
- You are using some 3rd party plugin that is causing problems.
Plugin that is often causing problems with BBCodes is ‘bbPress Advanced Statistics’, and this plugin will disabled all BBCodes by default.