Conflict with '.html' permalinks

I’m using custom permalinks like “/%category%/%postname%”.

Why put .html also ? No need.

i need it in fact because i delete the /categoy/ slug with a simple coma in the field if i don’t add .html sub category won’t work :

/%category%/%postname%.html : in custom structure
. : in prefix

that way without the category slug i can create a page that override the categorie when the url is load :

https://www.my-site.com/cat1/subcat1 : subcat is shown
https://www.my-site.com/cat1 : (category) without category slug =
https://www.my-site.com/cat1 : (page) when the url is load, the page is shown not the category

and fot the seo the page appear to be static but it’s not for that i use it

That’s interesting. For the most part, WordPress cache plugins, including GatorCache, use the ‘.html’ extension for cached pages, which may cause a conflict. However, I’d have to agree with MassimoD that the use case is limited – any modern cms, including WordPress, will use “pretty urls”.

i know many dev’ who use that technic for seo : https://www.seomofo.com/wordpress/seo-friendly-permalinks.html

but there for me it’s also for functionality purpose.

do you know why the cache make the the generated cache bug ? double work on the file because it not understant that the page is dynamic ?

Not really sure what you really are looking to accomplish, but this may work in the new 2.0 version.