Hello: 

I don't recall the theme file itself being impacted by that feature.  🤔

I'm not sure that you can "disable" this feature entirely.  Though, it's a provider, so it would be pretty easy to make a copy of the provider in the core and add logic to help you with this use case. Though, that's probably not the correct solution for you.  

For example, I'm guessing you're primarily annoyed during theme development.  I'm used to a hard-refresh being all that's necessary. 

It would be trivial to add logic to look for a query string value in your dev environment (for example), and then auto-increment using a bit of code.  This can be done in your theme files, directly.  An alternative provider wouldn't be necessary.  

Provider in the webconfig: 

<code><clientcapability defaultprovider="aspnetclientcapabilityprovider"></clientcapability></code>

Thanks, Will.

Glad to see you're still around. I remember you from DNN world back in 2011 in Orlando I believe.

You're correct, it's only a problem when making tweaks to the skin file. I too was used to only having to do a hard refresh, but something has changed and that's not getting it done anymore.

Let me poke around some more and see if anything is configured wrong.

Was there supposed to be something after "Provider in the webconfig: " in your reply? I don't see any image/text after that.

Thanks again!

Yes. I had intended to display the provider to look for in the web-config, but it keeps getting removed. 

<code><clientcapability defaultprovider="aspnetclientcapabilityprovider"></clientcapability></code>

Okay. I give up, but you can find the provider by searching for "<code>aspnetclientcapabilityprovider</code>" in your config file. 

 

from web(dot)config

Only JS and CSS changes would be impacted in this way. Changes to ASCX files only (as long as they aren't directly loading CSS or JS files that have also been changes) should be render fresh on every load, as they are server-side controls.

The only thing that comes to mind would be page cache. You could adjust the cache settings. Does it happen both for unauthenticated and authenticated ?

That's what I would expect and how it's always been (used DNN since 5.X days).  Unfortunately that isn't what I'm seeing.

I've tried in both Evoq Content and Platform editions, using a custom skin and also the out of the box Xcillion skin.  Both have the same issue.

I'm starting to think it may be a bug.

Here are the exact steps I've done to test:

1. Modify the ascx file and add a simple CSS class to an existing div (changed this div: 
   to this: 
2. Refresh the page (both authenticated and unauthenticated) and view the page source and it still only shows the
   without the class that was added

I'll put a ticket in with DNN support and see what they say.  I tried previously, but couldn't get through the unwanted AI assistance, haha.

Thanks

There is no page cache on the page and it's happening to both authenticated and non-authenticated users