Loop /categorie-produit/

Hi @milouze,

This is very interesting! Thank you for bringing this to our attention. Could you please share the steps you took to arrive at that link? Or was this just manually typed for testing purposes? We’d like to learn more to be able to replicate it and find the root cause and fix this issue.

Thanks!
-OP

Hi,

This just manually typed for testing purposes.

And i have website with one error in link structure and a scraper systeme make infinite requeste, and i see that in log, that caught my attention.
Is simple reproduce on every site that use the /categorie-produit/ or other /categorie-produit-custom/ on nginx or apache. Only stop this with removing this slug by add a . POINT into the permalink settings.

Thank you

Hi @milouze,

Thanks for sharing additional information.

I tried to replicate the issue on my testing site but didn’t succeed. Can you please provide the exact steps to reproduce it?

Also, if you think this is a bug, we suggest you create a BUG report in our GitHub repository here.

Rest assured, the URL structure you’ve reported is indeed unusual, and no one else has reported it so far.

Looking forward to hearing from you!

Hello,

The exact test is make a new site (with Local) and i install WooCommerce. I use the “Post name” Permalink structure. I and i create “test” categories. And i try url with add multiple /test/ in url.

I make some research and i have the same result with categories “uncategorized”. I think is unusual structure but i am not sur.

Maybe i ask the question in core track ?

Thank you

Hi @milouze,

Your case is unusual, and we appreciate your efforts in doing some testing and research on your own.

However, I followed the same steps to test with the WordPress category, and it works in the same way: siteurl.com/category/blog/category/blog/

The issue may be related to how WordPress handles URLs, and your idea to ask the question in the core track could also be helpful.

In the meantime, I also recommend creating a bug report in our GitHub repository. This will allow our development team to look into the issue directly and potentially find a solution.

Please include all the details you’ve shared here and any other relevant information that could our developer understand and replicate the issue.

Thank you for your patience and cooperation.

We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.