DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.
  • Search Forums
    Advanced Search
Prev
Next
Forums Using DNN Platform Performance and Optimization

DNN 9.11.3 - Modifying Skin .ascx files

 15 Replies
 4 Subscribed to this topic
 21 Subscribed to this forum
Sort:
Page 2 of 2 << < 12
Author
Messages
jacton
New Around Here
Posts: 19
New Around Here
10/2/2024 5:41 PM
After some extensive testing here is what I've figured out:

1. It's NOT incrementing the CRM that causes the changes to appear. The changes show up after doing "Server", "Restart Application" (or recycling app pool in IIS).
2. It's NOT specific to the DNN version, as mentioned this is happening on 9.11.2, but I did a fresh install of the same version on the same server and it works fine.
3. I've compared DNN performance/caching settings between the broken and working sites and they are the same.
4. I've compared web config settings related to caching, and they are the same between the 2 sites.
5. I've compared IIS app pool settings, they are the same between the sites.

Can anyone think of anything else that I can check? It seems like it has to be a IIS setting or something.

Thanks
David Lee
Advanced Member
Posts: 207
Advanced Member
Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
New Poster
New Poster
Congrats on posting!
10/2/2024 9:42 PM
I will throw this in, although you've probably already checked it. The browser cache has gone crazy, I always develop with DevTools(F12)>Network>DisableCache turned on. Then I always run with DevTools Open so the setting is active and removes any browser cache.
jacton
New Around Here
Posts: 19
New Around Here
10/3/2024 9:24 AM

Thank you, David.

Yes, I have checked that, and always do the same myself.  Browser cache can definitely get you sometimes.

I'll keep digging and post any solution I find here.

jacton
New Around Here
Posts: 19
New Around Here
10/3/2024 9:50 AM

I FINALLY figured this out.

It was an obscure setting in the web config file called "fcnMode".  After comparing web config of a working site with the site that didn't work I noticed the difference in values.  The working site had fcnMode="Single".  

After testing that, it indeed fixed my issue.

Here's a blog post with more info on what exactly that is: https://shazwazza.com/pos...ge-notification-fcn/

As previously noted, this changed when we upgraded from an older version of DNN 9.X to 9.11.2, so something in the upgrade process changed that value.

During testing for this issue, I did a fresh install of DNN 9.11.2 and it worked fine, so install packages aren't affected.

Hope this helps someone else, as I was at the end of my rope.
 

Timo Breumelhof.
Senior Member
Posts: 1322
Senior Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
Lifesaver
Lifesaver
You're Life Saver!
New Poster
New Poster
Congrats on posting!
3 Engaged Reader
Engaged Reader
You are an engaged reader!
10/3/2024 1:07 PM

Glad you found it and thank you for posting the solution :-)

Will Strohl
Senior Member
Posts: 1607
Senior Member
MVP
MVP
You're an MVP!
New Poster
New Poster
Congrats on posting!
10/4/2024 12:09 PM
For the most complex issues, I often find myself doing a diff/compare of the web(dot)config against a clean instance of the web(dot)config of the same version of DNN. I do this after each upgrade too, just to prevent these issues in the future. Another place to look next time is in the Bin folder.

Also sometimes, a DLL will have a complimentary .config file named after the DLL, and I've found them to sometimes override the values in the root config file.
Page 2 of 2 << < 12

These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy. 
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved