Background of the issue:
Remove a "Shop" page that does not exist, and is not translated, but shows as a live, published translation page
Please see screenshots below.
Main language is English.
Translation langauges are Punjabi and Punjabi Shahmukhi script, "pa" and "pa_sh" respectively.
"Shop" page in English is set to "Draft." It does not have translations under WordPress Dashboard > Pages.
Shop page in "pa_sh" is publiclly available, but with no way to edit the page.
Why would translated pages of the "Shop" page appear and be public, with no way to set them to Draft?
How do we remove these translations that we did not designate for translation?
How do we stop WPML creating translated pages that we did not deliberately set to be translated?
hidden link
hidden link
hidden link
hidden link
hidden link
hidden link
Symptoms:
Translated pages of the 'Shop' page appear and are public, with no way to set them to Draft. A Shop page with a translation language URL is not available as a translated item under WordPress > Pages.
Questions:
Why would translated pages of the 'Shop' page appear and be public, with no way to set them to Draft?
How do we remove these translations that we did not designate for translation?
How do we stop WPML creating translated pages that we did not deliberately set to be translated?
Thanks for contacting WPML forums support. Before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.
1) Please publish this draft shop page and translate it. After that, please go to WooCommerce-> Settings and check the selected shop page ID to make sure that it's the correct page.
2) It's not related to the issue, but according to your Debug.info, the WP memory limit needs to be increased. PHP memory is fine, but WordPress uses 40Mb as default. The minimum requirements for WPML are 128 MB. (Kindly check this page https://wpml.org/home/minimum-requirements/)
You can increase it by adding the following code in your wp-config.php file right before the /* That's all, stop editing! Happy publishing. */ line:
These are the English dashboard settings for the Shop page under WooCommerce > Settings > Products
hidden link
These are the Punjabi dashboard settings for the Shop page under WooCommerce > Settings > Products
hidden link
Note: I need to set these pages to draft because they are not needed at all. We only use the payment functionality in WooCommerce, to work with another plugin. Our Shop is empty. We don't want anyone reaching this page, nor any search bots to index it.
Thank you for contacting the support. I'm assigned this ticket and 'll try my best to help you further on the matter.
Since you've published the page and translation as of your last message, can you now set these to draft and see if it works?
To set a translation to the draft, you can switch from top admin bar to the other language and set the status of the desired page accordingly.
If that doesn't work, can you please try the following?
1) Take a full backup of your site and database before proceeding. It is highly advised to try these on a dev or staging site first, so your live site isn't compromised.
2) Deactivate all plugins except WPML and String Translation.
3) Switch to a standard WordPress theme like 2021 or 2024.
4) Check for the issue if it still happens.
5) Then start activating plugins one by one while keep checking for the issue. This way you 'll be able to pinpoint a conflict when & where it starts creating the problem.
6) If after activating all plugins you see that it still works fine, then switch to your theme and see if that's causing it.
Please let me know and I'll try my best to help you further on the matter.
I have performed this test and found that the issue occurs with the Genesis Connect Plugin by StudioPress. It causes WooCommerce Shop pages that are in both the original and translated langauges to be published even after they have been set to "Draft."
However, I am in touch with WP Engine, which owns StudioPress, to further troubleshoot the issue. I have not yet heard back from them.