[Assigned] Post deletion documentation, when what?
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.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Background of the issue:
I am working on a site under development and have activated the setting in WPML to delete translations when a post is deleted. I want to understand how this setting works, especially in relation to synced duplicates of posts.
Symptoms:
I am unsure if the deletion setting works for copies and what happens when original or synced copies are deleted.
Questions:
Does the setting to delete translations when a post is deleted also apply to duplicates?
What should happen if the original post is deleted?
What should happen if a synced duplicate is deleted?
Must the deleted post be removed from the trash for the duplicates to be deleted as well?
If we choose the *When deleting a post, delete translations as well* option in WPML>>Settings>>Posts and pages synchronization it will work like the following. Please try it after a full site backup and let us know your feedback.
1) When we Trash an original/default language post its translations will be also trashed
2) When we Trash an original/default language post its duplicates (in the secondary languages) will be also trashed
3) If we permanently delete a post from Trash, its translations/duplicates will be deleted permanently
4) When we Trash/Delete permanently a translated post its original/default language post will not be trashed/deleted
Managing of the jobs is only allowed in the language in which the job is created, because changes are synced then to the copies.
So also deletion is also only allowed in the language, in which the job was created. But the deletion by the user only delets the original job post, the copies are not deleted.
Only if the admin go to the job listing trash and delete this job permanet, all the copies are gone.
Is it possible to get all the copies deleted into the trash with deleting the original post?
Thank you for the details. Yes, if we activate the *When deleting a post, delete translations as well* option, deleting an original language post will also move its translations to the trash.
However, please note that if a post is created in a secondary language and then translated into the site's default (original) language, the post in the secondary language must be deleted first.
You can also select the *When deleting a taxonomy (category, tag or custom), delete translations as well* option of WPML>>Settings>>Posts and pages synchronization.
Hi,
Thanks, I had set also *When deleting a taxonomy (category, tag or custom), delete translations as well* already.
In my system it is set this way:
User adds a job in a second language, this job is duplicated (no translation) and by this there a copies of the by the user created job. The user is only allowed to delete the one he created, and if he do so, the copied jobs are not set to trash and are still in the system published.
So my question: is this a standard function? Then we should check this here. If not I have to go forward with a custom code here.
Thank you for the updates. I have tested a similar case in a sandbox site (fresh installation). It works as expected. I created a couple of custom posts (Books) in the secondary language and duplicated them in the default language. The default language posts moved to Trash when I Trash the post was created in the secondary language.
Please click the following links for more details.
Hi,
Thanks, good idea, yes, I installed here the Jobmanager and made the same test. Yes, all duplicates are in the trash. And I added field manager and acf taxnomies and added a tax field, and it is deleted into the trash. OK.
So remains the question, why is not this way in my site?
