Split: Translation queue shows jobs not found

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with WPML Translation Management where 'Jobs could not be loaded' due to wp-json being disabled for security reasons. Additionally, they encounter a message stating 'You can only edit translations assigned to you' and are considering downgrading WPML due to these issues.
Solution:
We recommend setting the Classic Translation Editor (CTE) as the default method for creating translations, which does not require the REST API and thus bypasses the issue with wp-json being disabled. Here are the steps:
1. Set CTE as the default translation method: https://wpml.org/documentation/translating-your-contents/translation-editor-options/
2. Alternatively, use the WordPress Editor for creating translations and avoid using WPML > Translation Management and WPML > Translations for these contents.
3. To hide WPML's menu options 'Translation Management' and 'Translations', use the Admin Menu Editor plugin: https://wordpress.org/plugins/admin-menu-editor/
4. If using the WordPress Editor, ensure that translators have the admin user role to create translations.
If these solutions do not resolve your issue or seem outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic is split from https://wpml.org/forums/topic/you-can-only-edit-translations-assigned-to-you-2/

Tagged: Documentation request

This topic contains 22 replies, has 2 voices.

Last updated by Andreas W. 1 year, 6 months ago.

Assisted by: Andreas W..

Author	Posts
June 20, 2024 at 6:18 pm #15765954
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Yes, I mean the creation of translations using the "WordPress-Editor" as the translation method 🙂 Regarding your request: In the past, WPML Translation Management was an additional plugin, so you were simply able to not install the plugin and the modules WPML > Translation Management and WPML > Translations were no longer available on WPML. Then we decided to merge the plugin into WPML Multilingual CMS. For now, we do not have any option available that would allow you to disable the module. I have suggested our Team to review the following design idea: - Hide any content from Translation Management while the "WordPress Editor" is set as the translation method for single content - Hide any post type from Translation Management while the "WordPress Editor" is set as the translation method for the given post type - Hide Translation Management and Translation Queue completely if the whole site is set to use "WordPress Editor" as the translation method for all the site's content. Or: - Redirect jobs from WPML > Translations to the WordPress Editor while "WordPress Editor" is set as the translation method I am waiting for feedback about this request.
June 27, 2024 at 9:13 am #15842311
franciscoR-11	Hi Andreas, the main issue that we have now is that roles author and author_publicador users get message "You can only edit translations assigned to you.". Before WPML plugin upgrade any user was allowed to edit translations post. Does your suggestions, fix this ? Regards.
June 27, 2024 at 9:28 am #15842390
franciscoR-11	Andreas, I forgot to ask you that, How we select "WordPress Editor" in WPML settings ? Classic Translation Editor is equivalent to "WordPress Editor" ?
June 27, 2024 at 5:35 pm #15845780
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, Thank you for your message! About my earlier suggestion, I sadly need to inform you that this feature request was declined. If you choose to use the WordPress Editor for creating the translations for your contents, please take note that you should avoid using WPML > Translation Management and WPML > Translations for those contents. About your question: By default, only admins and translation managers can access any job. The message "You can only edit translations assigned to you." means that currently another translator has this job assigned and this is why no other translator can access it. The translator first needs to resign from the job to make it again available on the general queue at WPML > Translations. Please revise WPML > Translation Management > Jobs and see which translator is currently working on this job and if needed cancel the job on the same screen. After that another translator should be able to assign the job. Relative ticket with a similar question: https://wpml.org/forums/topic/you-can-only-edit-translations-assigned-to-you-2/ --- WPML will by default use the WPML Translation Editor (Classic Translation Editor or Advanced Translation Editor). You can enable the WordPress Editor as an alternative by opening the original content on the WordPress Editor and changing the translation method inside the right sidebar. Please read this guide: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/ Best regards Andreas
July 1, 2024 at 4:56 pm #15869950
franciscoR-11	Hi Andreas, i solved our problem adding this filters. Now, any user can edit all translations with wordpress editor. function my_custom_filter_status_css_class($css_class, $post_id, $lang, $trid) { $css_class = str_replace(array("otgs-ico-add-disabled","otgs-ico-edit-disabled"),"", $css_class); return $css_class; } // Custom filter function for filter_status_text function my_custom_filter_status_text($text, $original_post_id, $lang, $trid) { global $sitepress; $language = $sitepress->get_language_details( $lang ); $text = sprintf( __( 'Edit the %s translation', 'wpml-translation-management' ), $language['display_name'] ); return $text; } // Function to add filters function remove_wpml_original_filters() { // Check if the class exists to avoid any errors if (class_exists('WPML_TM_Translation_Status_Display')) { add_filter('wpml_css_class_to_translation', 'my_custom_filter_status_css_class', 20, 4); add_filter('wpml_text_to_translation', 'my_custom_filter_status_text', 20, 4); } } add_action('plugins_loaded', 'remove_wpml_original_filters', 20);
July 2, 2024 at 1:50 pm #15876055
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, I am glad to hear that you found a solution. Take kindly note that our support is not responsible for providing custom code solutions and that your code appears to manipulate the default behavior of how WPML is supposed to work. In case your approach leads to issues on the site we cannot guarantee or provide support for custom code. WPML Support Policy: https://wpml.org/purchase/support-policy/#:~:text=WPML%20Support%20Policy%20If%20you%20have%20a%20valid,you%20to%20get%20the%20most%20out%20of%20WPML. If you need assistance in such cases we suggest that you contact one of our contractors: https://wpml.org/contractors/ Best regards Andreas
July 5, 2024 at 4:46 pm #15899514
franciscoR-11	Andreas, we had no other options. In the past, WPML Translation Management was an additional plugin, so you could simply choose not to install it, making the module 'WPML > Translation Management' unavailable in WPML. Currently, 'WPML Multilingual CMS' does not have an option to disable the 'WPML Translation Management' module. This results in a malfunction of our WordPress WPML installation, which did not have the 'Translation Management' plugin installed before the upgrade of 'WPML Multilingual CMS'. Regards. Josep Marxuach.
July 5, 2024 at 7:29 pm #15900006
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	I understand, Josep. Indeed, Translation Management is now a core feature of WPML Multilingual CMS, and the main purpose for most users today is to use the Advanced Translation Editor including its feature for automatic translation, while others use Translation Management to administrate jobs for local translators or to send content to professional translation services. Our product management did sadly not consider my suggestions: 1) Remove Translation Management for websites that translate all the site content with the WordPress Editor - This might not be a general solution, as there are in fact contents nowadays that can only be translated with Translation Management, like for example Gravity Forms, Divi Templates or Block Theme Templates. 2) Remove contents from Translation Management if WordPress Editor is set as the translation method 3) Remove post types from Translation Management if WordPress Editor is set as the translation method Those last two suggestions would have been realizable from my point of view and would be a solution for the issue, but they were sadly not considered by our product management. Suggestion: Please make sure to not use WPML Translation Management if your content is getting translated with the WordPress Editor.