-
-
Notifications
You must be signed in to change notification settings - Fork 774
[Bug]: CRM/CDV Cache Busting Stopped working after upgrade to DNN v10.02+ #6946
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
In brief
With the removal of enable composite and minify, the ability to control the CDV (CrmVersion) in page source output is no longer working. The UI (PersonaBar settings) is stuck in "site" mode. The actual page output is using "host" mode.
Workaround: manually incrementing the dbo.HostSettings CrmVersion does still work.
Important thing to test as part of a fix - right now, in the database, manually changing PortalSettings' CrmUseApplicationSettings to True or False makes no difference.
Long detailed version w screenclips
The Enable Composite Files was removed:
Above shows DNN v9.13.10, below is what we see now in DNN v10.02.01:
Notice the CRM Mode is also missing. It should not be, right?
Here is the problem: on two of my upgraded sites (started life on DNN v9.x and are now v10.02.01) where I've checked, the site is locked on delivering the ?cdv=826 while in PB Server settings above, you can see that its showing 400.
So, I switched into the database and in dbo.HostSettings, I changed CrmVersion from 826 to 827, recycled the app pool and now on page refresh, as expected I get ?cdv=827. In dbo.PortalSettings you can see I changed CrmVersion to 400 and it matches what you see in PersonaBar, but is NOT what is output in the page source.
Basically, what i need someone to confirm in DNN v10.02+ is that...
- incrementing the SITE VERSION does nothing
- DNN no longer respects True or False in the portal settings'
CrmUseApplicationSettingsand - always uses only the host settings' CrmVersion
Also, just confirmed this does NOT affect sites deployed on 10.02.00 (started life after enable/min features were removed), they properly use only the PostalSettings' CrmVersion and incrementing it works (number goes up and matches what you see in your page source). In the DNN v10.02.01 version, PostalSettings has
False (to me) should mean that we are using Portal/Site settings, which is 1 as you can see above.
In HostSettings CrmVersion is 52
Since I think 'UseApplication' should mean host, then False means use portal settings and in my page source output I should see ?cdv=1
However, its 52:
Steps to reproduce?
Covered above I think.
Current Behavior
On upgraded sites your ?cdv=555 stays stuck on whatever the HostSettings' CrmVersion was prior to upgrade.
Expected Behavior
You should be able to switch between using the Portal/Site and Application/Host version of the CrmVersion value in the PersonaBar.
Relevant log output
n/aAnything else?
No response
Affected Versions
10.2.0 and 10.2.1 (latest v10 release)
What browsers are you seeing the problem on?
Chrome
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
Type
Projects
Status