Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Upgrade Process to remove Telerik #4888

Closed
Tracked by #4887
mitchelsellers opened this issue Oct 26, 2021 · 5 comments
Closed
Tracked by #4887

Update Upgrade Process to remove Telerik #4888

mitchelsellers opened this issue Oct 26, 2021 · 5 comments
Labels
Alert: Pinned Used to prevent this from becoming stale
Milestone

Comments

@mitchelsellers
Copy link
Contributor

mitchelsellers commented Oct 26, 2021

The process to remove Telerik during DNN 9.11.0 upgrade should include the following actions

  • Install Resource Manager
  • Update all Digital Asset Manager modules to be Resource Manager modules
  • Uninstall DigitalAssetsManagement (Digital Asset Management)
  • Uninstall DotNetNuke.Web.Deprecated (DNN Deprecated Web Controls Library)
  • Uninstall DotNetNuke.Website.Deprecated (DNN Deprecated Website Codebehind files)
  • Uninstall DotNetNuke.Telerik.Web (DotNetNuke Telerik Web Components)
  • Uninstall DNNSecurityHotFix20171 (DNN Security HotFix 2017.1)
  • Remove SiteUrls.config entries for Telerik
  • Remove packages from App_Data\ExtensionPackages for all above uninstalled packages
@daguiler
Copy link
Contributor

I'm scratching my head with this one.
Any ideas on how to go about it @mitchelsellers @valadas @david-poindexter @bdukes ?

@daguiler
Copy link
Contributor

The stages of upgrade process are defined by this code in UpdateWizard.aspx.cs:

image

Essentially, we are dealing with:

  • direct database data updates
  • installation of new extensions
  • page module replacements
  • removal of some existing extensions
  • search and replace in config files
  • removal of files

The only tools we have to get this done are database upgrade scripts and extension manifest files, correct?
So replacing a page module with a different one will have to be a direct database data update?

@daguiler
Copy link
Contributor

Maybe we can create a new Extension to take care of this cleanup, and install and run this new extension as part of the upgrade? And then auto-remove the extension if everything went well, or leave it installed for the user to manually retry later in case of failure?

@stale
Copy link

stale bot commented Jul 31, 2022

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

@stale stale bot added the stale label Jul 31, 2022
@david-poindexter david-poindexter added Alert: Pinned Used to prevent this from becoming stale and removed stale labels Jul 31, 2022
@valadas
Copy link
Contributor

valadas commented Aug 30, 2022

This has been done in #5212

@valadas valadas closed this as completed Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Alert: Pinned Used to prevent this from becoming stale
Projects
None yet
Development

No branches or pull requests

4 participants