moniheli

Heya! Sorry, I realised I wrote the answer in my head but not here.

The empty plugin worked, thank you so much! I contacted Crocoblock but they wanted me to log in to be able to file an actual ticket, and I do not have login access to our account. I asked our webmaster to do it but I don’t know if he sent the ticket. So just so you know, not sure the issue is “officially” known there. Sorry about that! But as long as it works for us, we’re good.

I did open another topic though, because our translations seems to have broken in the process, around words containing accented characters (? ? ?).

PS: Issue was not resolved after the first solution provided, if the Resolved flag could be removed from this thread, thank you! Our website has lost massive functionality due to the issue and as a bilingual organisation it really impacts our work, so want to make sure this ticket stays open until we find how to move forward.

Hi again! Just lost my whole post upon posting, let’s try again.

We tried the rollback but it didn’t solve the issue, pretty much only disconnected most of the text strings translations, but it’s at least fixable.

We have also noticed that the whole page menu is fully gone from the English version of the website, this wasn’t mentioned in my original message. When accessing the English version of any page via the Translation Editor, the list of translatable strings is much shorter and the menu choices do not appear in there at all. The translated strings are in the menu of the Translation Editor and their translations are there as well. Same in the Regular tab.

Considering this as well as the navigation menu issue, it really does feel like the display of pages in the secondary language is broken, rather than it being missing or broken translations. What could be the next step?

Hello!

Thank you for replying! For the dropdown options – they are coming from Fluent Forms. We used the translation memory to translate – added a hidden text box elsewhere on the website, added the terms, translated the terms as text strings, and the translations were successfully pulled to the dropdown from the TM.

And we’re indeed on 2.8.4, we’ll do the rollback and I’ll update! Thank you so much!