We are doing our best here to help and there is no passive approach going on here.
We will not be able to do any change on a live website due to our support policy and we do need to have a copy of the website to be able to do investigation about the duplicate queries.
I checked the video you posted and it doe not have any context whatsoever and I am not sure how it is related to the duplicate query issue.
Again, I'd appreciate it if you can provide the copy of the website according to the documentation below:
I asked the second-tier support to go forward and check the live website without touching anything.
He mentioned that in the backend there is no issue showing in the query monitor plugin and the query monitor is not available on the homepage in the first place to see the queries.
I also double checked and he was right.
Any reason that it does not show? And I wonder how you managed to see the duplicate queries in the homepage?
I tried one more time to create a dump of the website and unfortunately it seems that there is space shortage or something that causes the issue.
So to be able to go forward I can ask for access to the Database of your website via your panel and FPT information so I can do the dumping manually by downloading from FTP and download manually the SQL from the database.
Just so you know that will take a lot of time as I do not have any choice here.
I'd appreciate it if you can give me access to the database of your website and the FTP connection information so I can do the process od dumping manually.
Please make sure that you set the next reply as private.
Thanks, I shared the details with the second tier support.
Meanwhile, the second-tiers found out that the query monitor works on Shop page and there they checked and suggested that you switch from display as translated mode to show translation only for the custom post types.
If you go to WordPress Dashboard > WPML > Settings > Post Types translation, you will see that you selected the second option for mist post types there (check the screenshot):
Translatable
use translation if available or fallback to default language
That might have an impact on the current situation and it is recommended that you select the
"display as translated mode to show translation only for the custom post types." -> This does not make sense to me as neither of the options are literally titled this. I believe you are suggesting for me to use "Only Show Translated Items" for ALL options, correct?
Our second tier support reported the duplicate queries issue to the development team in "Translatable | use translation if available or fallback to default language" option mode.
