codejp3

Ok. So the Impreza Theme offers font styling for bbPress, and you’re using those settings for fonts instead of using Style Pack for fonts.

Tha lazy/easy answer is: Just use Style Pack for your font styles instead of the theme. Problem solved.

The better answer/solution is: For Style Pack to account for your theme’s font settings, and either:

1.) Apply those to Style Pack as the new “bbPress default”.

or

2.) Don’t include those fonts as part of the generated CSS for Style Pack.

Either option has a few potential issues to figure out, and I’m undecided which option is the best approach right now.

Option #1 would require you to regenerate the CSS file any time you change font values in your theme.

Option #2 may involve a lot of extra code for a not-so-common feature and unnecessarily complicate future updates.

Later today I will install Impreza Theme and see what font values it offers, and then I will work on an update for Style Pack to make sure any theme values you have set get the priority.

@robin-w – I’m on this one, but appreciate your input as always.

That is the default. No settings exist except for the ones you select. Everything is disabled by default.

NOTHING should be active by default and bbPress should look and function exactly as it was prior to activating Style Pack.

Are there any specific settings active on Style Pack activation that you’re referring to? If so, let us know and we’ll look into it.

OK. Good to know! If there are any specific bbPress strings you want to set translations for not currently present within the Style Pack template files, let me know and we can add them so you can do your personalized translations for them.

I hope to have the translation update done by this weekend. Once it’s kicked out, you’ll want to re-sync your custom translation file for Style Pack.

Marking this as resolved, but feel free to post any translation issues you run across.

I was afraid all translations had been replaced (which would have been a disaster in my case as I did change a lot of them), but it seems that it is not the case.

@maksanse

There are translation plugins that can handle “on-the-fly” translations site-wide (Style Pack can do this in the “Translations” tab, but it is limited).

As LocoTranslate allows you to work on translation files PER PLUGIN, that’s how translation strings are handled: per plugin. Changing any translation strings there will only affect the specific plugin’s .pot/.po/.mo files, but has zero effect on any other plugin.

That’s why I mentioned writing a custom script to do so. Manually making those changes could be a daunting and time-consuming task. I will keep thinking about a solution that will prevent the need for manual edits and see what I can come up with.

A warning for custom translations too:

When a plugin is updated, so is the included translation files. If bbPress releases a new version, the translation files included within the new bbPress version will overwrite the custom ones you currently have. Make a backup! And you’d have to reapply your customizations to the new plugin version too. Using a diff tool (like Meld) will help, but it’s still a bit of a pain.

• This reply was modified 3 years, 1 month ago by codejp3. Reason: Added translation warning

@blinkweb – An official fix for this will be released this weekend. Marking as resolved, but if you still encounter issues after the update, feel free to update this topic.

Details:

The issue actually had nothing to do with Divi theme. The exact issue is that on the “Freshness Display” tab you had “Custom” selected for “Date Format” and “Time Format“, but you left the text boxes empty instead of specifying your desired custom format.

The fix that will be released this weekend will default to using the default format any time “Custom” is selected, but left empty, like in your case.

In the meantime, you could select ANY of the pre-specified formats for Date/Time instead of “Custom”, which will then allow you to use your preferred “Hybrid” option for #6. Freshness format

@blinkweb – just letting you know I did get the settings export, imported it in my local test server, and the issue you described appeared immediately.

I’m now looking into the cause of it and will update this topic as soon as I know more.

The only shortcode used is in the sidebar. the rest of the screens as you drill down use the BBPress template – whichever that one is

@blinkweb

Are you sure you’re not using custom pages with shortcodes?

Your Navigation Menu link points to:

https://emgs.org/forum-temp/

But your breadcrumb for the forum root points to:

https://emgs.org/members-forum/

And BOTH URLs display identical content.

You should only be using one link for your forum root content. Having 2 links pointing to identical content is horrible practice that search engines will hold against you and rank you lower because of it. Plus it can confuse your members due to multiple links pointing to the same content.

Which one is the slug specified for “Forum Root” in the in bbPress settings (/wp-admin/options-general.php?page=bbpress) ?

My guess is “members-forum” is the correct one, which indicates that you have created a custom page with the slug “forum-temp” and uses and embedded shortcode.

The slug specified as the “Forum Root” is the one you should be using in your nav menu (probably “/members-forum/”). The duplicate link should be deleted/removed altogether (probably “/forum-temp/”).

Clicking on the “Forum Notes” forum points to:

https://emgs.org/members-forum/Forum/forum-notes/

The breadcumb shows:

Home Icon › Members Forum › Forum Notes

Clicking “Members Forum” in that breadcrumb takes me to:

https://emgs.org/members-forum/

That pretty much confirms that /forum-temp/ is the one that needs to be deleted and no longer used and that /members-forum/ is the one that should be in your navigation menu.

Also, all of your slugs should ideally be lowercase …

https://emgs.org/members-forum/Forum/forum-notes/

… So the slug for “Forum” in “Forum Single Slugs” (/wp-admin/options-general.php?page=bbpress) should be changed from “Forum” to “forum”. It looks fine for topics, but if any others are capitalized there, change them to lowercase as well.

You have some URL/slug/link issues like these mentioned here. Fixing them will certainly help and improve your site, but none of these changes will fix the issue you mentioned in this topic. I just noticed these issues as I was browsing your site and wanted to pass on the info so your site doesn’t keep getting ranked lower by search engines.

As for addressing the original issue you created this topic for – Once I get your reply for the post above, we’ll go from there.

@blinkweb – Here’s what I’ve tried on my test server:

I had several forums/subforums with old topics/replies already in them. That should simulate the “old” topics/replies.

I installed Divi theme version 4.21.0 using all default settings for the theme.

I then activated Style Pack version 5.5.0 and updated it to 5.5.1. The topics/replies on the index displayed properly.

I then created some new topics/replies within those forums/subforums and the index still displayed properly.

Then I tried by installing Style Pack 5.4.7 and updated it to 5.5.1. The topics/replies on the index displayed properly.

Just for good measure, I created some new topics/replies within those forums/subforums and the index still displayed properly.

SO….

I can’t replicate the issue you describe on my test server. which brings me back to the clarifying information both myself and @robin-w asked:

1.) Does the issue exist with all forums, or only forums where there’s been new topics/replies after the Style Pack update?

2.) Does the issue exist with the primary forum/topic index pages, or is the issue happening with shortcodes/widgets that you’re using?

3.) Do you have a link you can provide that shows the issue in-action? You can email it privately to me at [email protected] if you prefer.

4.) Did the issue clearly and immediately happen after updating Style Pack with no other site changes, or were there multiple changes applied to your site at the same time?

5.) Have you specifically used the bbPress tools (/wp-admin/tools.php?page=bbp-repair) for:
“Recalculate parent topic for each reply“,
“Recalculate parent forum for each topic and reply“,
“Recalculate last activity in each topic and forum“,
“Recount topics in each forum“,
“Recount replies in each forum“,
and “Recount replies in each topic“,
and most importantly:
ONE REPAIR AT A TIME !! ( I’ve noticed that when you do multiple repairs, they don’t always get performed, so ONE AT A TIME is the way to do it).