https://docs.dnncommunity...rade-path/index.html

IMHO there are diffferent scenarios for the need to upgrade. When it comes to security: asap. When there is a major release: I would hold on a bit until properly tested in the real world. For instance, in DNN 10 workflow was introduced. It takes a bit of time to understand how it was meant to be used.

From both experience, and according to the suggested upgrade path:

• if you are at 9.13.09, skip 9.13.10
• you only want to go to 9.13.10 if you cannot yet successfully upgrade to v10
• upgrade to 10.02.01 (regardless of what you read anywhere, do NOT upgrade to 10.02.00)
• now use the new upgrade process to 10.02.03

DNNDocs: New Upgrade Process
https://docs.dnncommunity...st-10.2.0-steps.html

DNNDocs: DNN Platform Suggested Upgrade Path
https://docs.dnncommunity...rade-path/index.html

I very highly recommend doing the upgrade on a clone of the site in a test environment. In the jump to v10, the most difficult to diagnose errors have been related to the new Client Resource Framework changes in 10.02.00. Which means, on failure, the theme is probably at least one of your issues.

One idea that has helped us a few times is do NOT use or goto your home page after each upgrade. Before upgrade, make a new page and set it to the Theme/skin with the least Panes and do NOT add any modules. After upgrading to the new version, if the site fails to start going to the home page, try also/instead going to your nearly blank upgrade page. If that works, you are now on the path to figuring out which module might be causing problems. And if it doesn't, the theme is a strong candidate for being the issue.

Make sure you review where to look for errors:

• DevTools Console in your browser
• PB/Manage / Admin Logs
• PB/Settings / Servers / Server Settings, Logs - YYYY.MM.DD.log.resources
• On screen and page source
• Some errors may only include needed detail if you view them on the browser directly on the server (or change settings** in web-config)
• In extreme cases, you may need to know how to find the Windows Event Log errors or even S-Q-L error logs.

** https://stackify.com/web-...ustomerrors-asp-net/

Posted By Jeremy Farrance on 3/17/2026 6:05 PM

From both experience, and according to the suggested upgrade path:

• if you are at 9.13.09, skip 9.13.10
• you only want to go to 9.13.10 if you cannot yet successfully upgrade to v10
• upgrade to 10.02.01 (regardless of what you read anywhere, do NOT upgrade to 10.02.00)
• now use the new upgrade process to 10.02.03

DNNDocs: New Upgrade Process
https://docs.dnncommunity...st-10.2.0-steps.html

DNNDocs: DNN Platform Suggested Upgrade Path
https://docs.dnncommunity...rade-path/index.html

I very highly recommend doing the upgrade on a clone of the site in a test environment. In the jump to v10, the most difficult to diagnose errors have been related to the new Client Resource Framework changes in 10.02.00. Which means, on failure, the theme is probably at least one of your issues.

One idea that has helped us a few times is do NOT use or goto your home page after each upgrade. Before upgrade, make a new page and set it to the Theme/skin with the least Panes and do NOT add any modules. After upgrading to the new version, if the site fails to start going to the home page, try also/instead going to your nearly blank upgrade page. If that works, you are now on the path to figuring out which module might be causing problems. And if it doesn't, the theme is a strong candidate for being the issue.

Make sure you review where to look for errors:

• DevTools Console in your browser
• PB/Manage / Admin Logs
• PB/Settings / Servers / Server Settings, Logs - YYYY.MM.DD.log.resources
• On screen and page source
• Some errors may only include needed detail if you view them on the browser directly on the server (or change settings** in web-config)
• In extreme cases, you may need to know how to find the Windows Event Log errors or even S-Q-L error logs.

** https://stackify.com/web-...ustomerrors-asp-net/

This is a very good post Jeremy!  great details and very specific, maybe think about throwing a blog article about the overall update process (just an idea).