Taxonomy question dropdown options gone, switching redirects to front page

Hello,

The actual HTML is empty. Can you please tell me how exactly you’re listing the <select> tags? Is it custom code? Or another plugin is responsible for it?
Did you translate them as option blocks? Selects are translatable, you just can’t select it.

If a string isn’t selectable with the pencil tool, you can search for it using the list of strings, https://translatepress.com/wp-content/uploads/2017/08/meta_information.png, available for translation from the Translation Editor, https://translatepress.com/docs/translation-editor/. You can search for it also in the String Translation Interface –> Regular tab (this tab requires to be activated from TP Settings –> Advance tab), https://translatepress.com/docs/translation-editor/string-translation/.

If you remove the integration you did, do the options appear back (even if they are not translated)

Also, what TranslatePress version do you have?

We suggest doing a rollback to: TranslatePress-Multilingual 2.8.3 if you have 2.8.4 We had issues with that update and it had to revert it to 2.8.3 untill we fix the issues.

You can do this by using the WP Rollback plugin.

Best Regards,

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!

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?

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.

Hello,

Do you have JetSearch? Because it seams like JetSearch added some compatibility with TranslatePress and applied a filter

//Translatepress Compatibility
if ( class_exists( ‘TRP_Translate_Press’ ) ) {
   add_filter( ‘trp_force_search’, ‘__return_true’ );
}

This applies this filter on ALL queries basically braking queries entirely.

The only posts that worked, were the posts that we indexed for search, basically posts that were accessed in a secondary language before installing JetSearch.

To fix this
* Create an empty plugin like this: https://gist.github.com/sareiodata/76f701e01db6685829db
* Add the following code to the end of it:
* add_filter( ‘trp_force_search’, ‘__return_false’, 99 );
* Install this plugin via FTP (copy it inside wp-content/plugins) or create a zip archive with it and install it via the WordPress plugin upload functionality

And if possible contact JetSearch via their support and ask they remove the filter as it completely brakes queries in secondary languages.

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 (? ? ?).