Released on:
Fixes
- Fixed trying to get property of non-object issue when wp_rerite wasn’t set
- Fixed fatal error Uncaught exception ‘InvalidArgumentException’
- Default custom language switcher options are now initialized after the setup wizard
- Language switcher in menu is properly shown when the source language of the menu is different than the default language
Usability
- Disabled the Save button in language switcher settings after clicking it
Download and Update
You can get this release directly to the WordPress admin or download and install manually. To receive automatic updates, you need to register WPML on your site. Then, visit the Plugins or Updates admin pages. To download manually, visit your wpml.org account and go to Downloads. Follow the installation and upgrade instructions for complete details.
When you update WPML, be sure to update together all the components that you are using. Don’t use a mixture of new and older versions.
Feedback? Need Help?
We love feedback. To make a suggestion, ask a question or give an idea, leave your comment here. If you need technical support and help troubleshooting problems, please use our technical support forum.
Hi,
Fatal error: when I activate the plugin the website doesn’t load, just the logotype.
I just wonder if I introduce a wrong secret key, please let me know how I can change this? I’ve been advised by the theme developers that the theme supports WPML. Please, could you provide with help?
This can be anything, so just “fatal error” doesn’t tell enough information. Can you please post about it in our technical support forum? Our supporters will find what the actual problem is and sort it out for you.
After update, I’m still getting error after trying to update ACF field group:
Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘No translation entry found for query: s:42:” element_id = %d AND element_type LIKE %s “;a:2:{i:0;i:455;i:1;s:15:”post_acf-field%”;}’ in /var/www/clients/client0/web20/web/wp-content/plugins/wpml-translation-management/classes/records/class-wpml-tm-icl-translations.php:183 Stack trace: #0 /var/www/clients/client0/web20/web/wp-content/plugins/wpml-translation-management/classes/records/class-wpml-tm-icl-translations.php(60): WPML_TM_ICL_Translations->select_translation_id(‘ element_id = %…’, Array) #1 /var/www/clients/client0/web20/web/wp-content/plugins/wpml-translation-management/classes/records/class-wpml-tm-icl-translations.php(41): WPML_TM_ICL_Translations->build_from_element_id(Array) #2 /var/www/clients/client0/web20/web/wp-content/plugins/wpml-translation-management/classes/records/class-wpml-tm-records.php(137): WPML_TM_ICL_Translations->__construct(Object(WPML_TM_Records), Array, ‘id_type_prefix’) #3 /var/www/clients/client0/web20/web/wp-co in /var/www/clients/client0/web20/web/wp-content/plugins/wpml-translation-management/classes/records/class-wpml-tm-icl-translations.php on line 183
Thanks for the note. Konrad, the developer working on this, should be in touch soon to get debug information.
After updating to 3.6.1 there ist a .git-folder in /vendor/otgs/intaller. PLease make sure to remove it by next update so that this folder and changes made in this folder can be tracked by my own git repo for that WordPress project, thanks.
Sorry about this leftover. We’re cleaning it up in a small update on Monday.
Hello,
Since updated to wp 4.7, I got the:
“Fatal Error (E_ERROR): Call to a member function add_filter() on a non-object”
I cant’ access to my admin and each time I deactivate WPML 3.6.1 the Admin come back!
This could happen due to different reasons. I suspect that it’s compatibility with a theme or a plugin. Can you please post about it in our support forum? One of our supporters will take this and probably ask you to disable other plugins and then gradually enable them. Then, we’ll see where the conflict is and we’ll be able to debug it.
The support forum is here:
https://wpml.org/forums/forum/english-support/
Thanks for your reply.
I just went back to wp 4.6.1, with lots of work and a few hours of sleep, but my website woke up!