The existing translated BB saved modules stil don't show up in BB panel for the secondary language (EN).
I tried many things:
- Update the existing BB saved modules
- Re-save them in many ways, including with all system fields set to "Copy"
- Save a new BB item and translate it
- …
Another simple test that might give you a clue, just save a BB module in EN, secondary language, no translation involved:
- On an English page, i enter BB Edit mode in frontend to edit the layout
- I save a BB module and name it "Test Button EN 2"
- It shows up in BB panel > Saved tab
- I save the BB layout, exit BB Edit mode and re-enter BB Edit mode
- The saved module has disappeared from BB Panel
Then, in Admin: BB > Saved modules, i switch between the 3 options of the lang switcher in the top admin bar, to make the saved module appear in the list:
- FR (main lang): no module displayed
- EN: no module displayed
- All languagess: the saved module finally shows up
Does this talk to you?
It looks like the language is not properly assigned to the saved module at some point, maybe?
Hi, and thanks for opening a new ticket for this issue.
Please, try WPML's troubleshooting section to fix this problem.
1. Take a backup of the DB of your site.
2. Go to WPML -> Support -> Troubleshooting (link)
3. Once on the troubleshooting screen press the following buttons and check if it helps. Press each button at a time and wait for the process to complete.
- 'Synchronize posts taxonomies' for BB templates.
- 'Clear the cache in WPML'
- 'Remove ghost entries from the translation tables'
- 'Fix element_type collation'
- 'Fix WPML tables collation'
- 'Set language information'
- 'Assign translation status to duplicated content'
- 'Fix terms count'
- 'Fix post type assignment for translations'
- 'Cleanup and optimize string tables'
*** Please make a backup of your database before using this.***
If the above does not help then please let me have access to your site and allow me to take a copy of it with the Duplicator plugin so I can continue to check the issue and escalate it is needed.
If you need further help with this, please share the access details to your site with me.
I'm enabling a private message for the next reply.
Thanks for your instructions.
I applied each action listed above and checked if my BB saved items showed up in BB panel after each action, unfortunately, they're still missing.
I would gladly send you a backup of this site so you can test it on your side.
But i can hardly use Duplicator, always encountered issues with it.
If you agree, i'd rather send you a copy generated by AIO WP Migration, which works fine for me: hidden link
If you can't use AIO WP Migration, i can install the backup on a test drive that you'd provide.
Thanks, but the migration with Cloudways plugin has fail.
Maybe because the site i want to migrate is local (Mamp Pro)?
After sending the first form, i received this error message:
"We are unable to contact the source site. Due to this the migration cannot be completed."
Then a second form shows up, but it requires more informations like :
- Application Folder Name
- Source Website password protected
- Destination password protected
- …
As a workaround, i should be able to install my site using AIO WP Migration on this temporary site, provided that you send me admin access credentials.
Sorry, i'm not sure it will fit, AIO WP Migration works in WP Backend, i'll need an admin access to the WP test site to install the AIO plugin + premium addon to connect to my GDrive, and then import my site from my GDrive.
I can confirm that the issue persists on the copy of your site on our server. I'm consulting our compatibility developer and second-tier supporters regarding this issue and will get back to you once I have more information.
I couldn't replicate the issue on a fresh WordPress installation. It only happens on your site and I couldn't figure out why. Therefore, I escalated this issue to our second tier supporters.
We will keep you updated here on any news regarding this issue.
I understand, it occurs frequently after an issue has been patched in a plugin, it can persist in the old install while it's not happening in a fresh one… i hope you'll find something to fix in my site anyway. 😉
