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.
But, there are some HTML tags that are not permitted (IFRAME, SCRIPT, STYLE) because in general, they can contain dangerous content, and when quoted, such tags will be escaped and saved as plain text. Because of that, quoting content that contains embedded content (FaceBook posts, Twitter tweets…), is not quotable.
Whenever you update the plugin, make sure to clear all cached data from cache plugin, server-side cache, CDN and finally browser cache.
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.
Alignment for complex HTML elements can be a very tricky issue, and it largely depends on the container and styling it has. The plugin has options to add alignment classes to the rating block, but, these classes don’t include actual styling and they are meant to be styled individually for the theme used.
To center element, that element should have the width set. But, if you set width for the rating block, that block will no longer be responsive. The plugin automatically makes stars smaller for the rating block to fit the current screen with. Having fixed width set for the rating block will prevent the plugin from making it responsive.
You can use CSS for responsive breakpoints to set different widths, but that too depends on the theme (themes usually have different breakpoints and different grid systems), and it is best to style rating block alignment for each individual theme to make sure alignment works for your theme. Also, depending on the theme and the grid system use, there might be some other way to center elements.
Plugin alignment feature is only placeholder class name, styling must be defined for theme.
If you don’t see stars, but instead there are letters S, this means that font with icons used by the plugin is not loaded by the browsers. The reason for this is that most likely your website is loading a font from CDN and some browsers are enforcing CORS policy. To get more information about it, and the solution on how to fix it, check out this article: Loading fonts from CDN.