Vimal Roy

Hello @bruceallen,

Thank you for your reply.

We already saw a message from you on some other thread mentioning this same addon, so we already tried it.

We initially downloaded the plugin and installed it. After activation, it was automatically removed from the plugins. The mentioned tables in the database are still there after activation and self-removal of the addon plugin.

Did we do anything wrong? Do we need to install the Jetpack plugin? How can we fully remove these unwanted tables in a proper way?

Please let us know your feedback.

Thank you

PFA:- https://imgur.com/a/3jmejx8

• This reply was modified 1 year ago by Vimal Roy.

Hello @sterndata,

Thank you for the response. I checked the ticket and found that they fixed the issue and released a new patch for the fix, but don’t know when we will get the fix for the normal WordPress users. Do we need to do the fix by manually adding the code to our core files ourselves?

Anyway, I created a comment over there “When can we expect a fix for the issue for everyone from the WordPress side release ?”. I think it is not included in the new 6.3.2 release.

Anyway thank you for your support.

??

Hi,

Will there be any solution for this? It’s been more than a month since we raised the issue, and we didn’t get any reply back. We checked the temporary solution provided by the WPML team, and it did not work either. We raised the same issue on WPML, and they are saying some other users are also facing this issue, and that’s why they are giving a temporary fix.

Temporary fix:- https://wpml.org/errata/google-xml-sitemaps-wrong-urls-in-sitemaps-when-language-are-in-directories/

Since you don’t have any time to fix the issue, is there any way to remove the translated posts from the sitemap? We just need the English version of the sitemap; we don’t want to include any other languages that we created using WPML because this plugin is causing redirect issues with other languages, as I mentioned in the ticket.

Either you guys fix the issue ASAP or give a temporary solution until the issue is fixed.

Thank you

Hi,

As per the WPML support team, there is a workaround (a temporary solution) to fix the issue, but we tried the same, and it didn’t work for us and didn’t fix the issue. You can check the workaround using the below URL, and please check it with your website to see if the solution is fixing the issue or not.

Workaround:- https://wpml.org/errata/google-xml-sitemaps-wrong-urls-in-sitemaps-when-language-are-in-directories/

Thank you

Hello!

We got the solution. We have some Font Awesome CSS, JS, and web font files that are outdated, and we just changed all those files to the latest version, and now the icon is working correctly.

Thank you

Thanks a lot, it worked.

Hi,

We have found a solution for the issue, there is an option to include the subdomains as the internal links and we checked the option and now the WPML language URLs working fine. PFA

https://imgur.com/a/ZTjMiBl

Thank you

So the free plugin is not compatible with WPML, right?

Okay, Thank you for the update!

Hello @jamesosborne ,

Thank you for your reply!

I understand that this plugin doesn’t have any sitemap functionality. I am not talking about the sitemap generate(we are using Yoast SEO plugin for the sitemap generation) functionality, I am talking about the ability of the plugin to submit the already generated sitemap using the Google Submit API (Google search console API).

Also, we have some doubts regarding the sitemap submission, ranking, SEO, performance, and keywords as I mentioned in the initial question.

Thank you!

• This reply was modified 1 year, 6 months ago by Vimal Roy.

Any updates???

Hi @wfsupport , @wfjoshc

Thank you for your valuable support.

We have changed the .htaccess manually as you mentioned, but it gives the same error message. The solution is not working,

Why it is not working? How can we solve this problem? When we remove the whole code of “<Files “.user.ini”>” it is working fine. With the .user.ini code it is not working at all. We have sent the newly created .htaccess file and .user.ini file to the mail. Kindly check that.

Please let us know your feedback.

Thank you

• This reply was modified 1 year, 8 months ago by Vimal Roy.

Hi @wfjoshc ,

No. It is privately hosted and currently, it is a staging version, but we need to make sure everything is working fine before we point the domain to this AWS hosting. The domain that we will use is purchased from GoDaddy.

Thank you

Sorry, Didn’t understand that!!

Please see the below info.

Server architecture:- Linux 5.15.0-1026-aws x86_64
Web server:- Apache/2.4.52 (Ubuntu)
PHP version:- 8.1.2-1ubuntu2.11 (Supports 64bit values)
PHP SAPI:- apache2handler