6.7 introduced yet more changes to how translations are handled.
I fixed the issue for a japanese site in style pack version a couple of months ago, what version of style pack are you using?
Thank you for you fast reply !
I use the lastest version of your plugin (6.2.1).
ok, I don’t know how much testing you can do without affecting the live site.
On my test site with bbpress, style pack and loco translate activated – I can see French in both bbpress and style pack.
But I have not set anything up in locotranslate – is there a setting I need to do?
and can you give a specific example of an item which is displaying in English
Yes : here is the video I made last year to see what to do with LocoTranslate (it is so painful to be french with bbpress 😅) : https://www.loom.com/share/bf5d4a1fdfa444fcb2de7bb067d07d5a?sid=c1e11f8e-0f03-4ed1-a3f8-c36ee2e4d07b
It should show you exactly the issue can be replicated.
Let me know for any question 👍
Kind regards
Thanks, I remember now.
I’ve just re-run the test and I am seeing
Me prévenir des réponses par e-mail (rew-custom)
ie the custom file I created last time.
I haven’t yet tried any style pack translation custom copies
You say It seems that both « BBPress » and « Bbp Style Pack » translations don’t work when your plugin is activated, but that’s not what I am seeing for bbpress??
Hum. I will recreate a fresh staging tomorrow to validate that the situation is the same (on my prod website, it is 🙄)
Hello Robin,
It took time, but I could reproduce the issue !
Here is a video showing the problem : https://www.loom.com/share/b83d75533a51474b8408f387dd382665?sid=a2a5e318-cc73-4e6c-bac4-8013fb55d4aa
To sum up :
- The issue happens when « Bbp Style Pack » is used in combination with « LearnDash LMS – bbPress Integration »
- When both plugins are enabled :
- BBpress translation is lost and english default displays
- The only way to solve the issue is to disable any 1 of them (= disabling your plugin or disabling Learndash one)
➜ So disabling your plugin and letting Learndash activated corrects my issue 🤔 (but disabling Learndash plugin and lettings your activated also works 🤪)
So it seems the issue is more complex than I thought.
Does it make sense to you ?
Kind regards
Thanks for that, very useful.
I don’t have learndash, but I have some ideas.
Can you contact me via
Contact me – Robin W’s website
with a link to this thread, as I get lots of contacts and that makes sure I know what the email related to !
Sure ! I did that 👍
Have a great we !
Hi,
I’m experiencing the same issue but with spanish language. Do you have any updates of this?
Thanks!!
Hello @osheta,
In my case, the problem is actually related to “Learndash bbpress add-on” plugin and a fix should be implemented by Learndash team in the future.
-> If you use that same plugin, you will get a solution at the time Learndash releases the update
-> Otherwise, you may have another bbpress related plugin that interfers with translations since WordPress changed the way it loads translation files recently (here is a link about the issue faced with Learndash add-on that may be relevant as well for you : https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/#:~:text=Your%20plugin%20might,the%20other%20fields)
Hope that helps 🙏
Hi @maksanse,
I have this plugins: bbPress for forums, bbp style pack for styling forums and LearnDash LMS – bbPress Integration for the integration. I think is the same case as you.
A few weeks ago I had an issue related to languages because of the update of WordPress core, so I think this plugins didn’t updated how languages are handled by WordPress.
Thanks,
Maria
We have submitted the change required to Learndash.
If you are into code the fix is in learndash-bbpress\includes\class-dependency-check.php line 119 – the line needs changing from
$plugin_header = get_plugin_data( trailingslashit( str_replace( '\\', '/', WP_PLUGIN_DIR ) ) . $plugin_key );
to
$plugin_header = get_plugin_data( trailingslashit( str_replace( '\\', '/', WP_PLUGIN_DIR ) ) . $plugin_key, false, false );
This then prevents translations being loaded at that point (too early) and fixes the issue.
Hi Robin,
Thanks for sharing the fix. I’ve updated and it seems working fine. I understand that after doig this changes, if the plugin updates, this fix would be erased, correct?
yes, it will get overwritten so keep a note of this thread.
But they have said they will be incorporating the fix in the next release, so hopefully that should all be ok, but if not, just add it back !
