Posted By Ratikant on 11/20/2023 4:33 AM

Hi,

I wanted to downgrade from Eqov 09.03.07 To DNN Platform 09.03.02. Can anyone guide me step by step process to migrate from Evoq to DNN.

Also wanted to understand the Web Farm support once we migrate from Evoq to Dnn free version platform.

Any help will be highly appriciated. 

I don't think downgrading is possible with the available standard options. (not even from Platform to Platform) You could upgrade though and I strongly suggest to do so as a lot of security issues have been fixed. Read here about webfarm support in DNN platform  

 

 

Yes, as Timo says, you can't really reverse an upgrade. That would in many ways be like moving from Windows 11 to Windows 10. You can't. :) However, you can migrate from Evoq to DNN Platform (of the same base DNN version), then you'll be able to upgrade to newer versions of DNN from that point forward using DNN Platform. (Exactly how to migrate from Evoq to Platform has some common steps from site to site, but a lot of it is unique to the site in question. So, we won't be able to get step-by-step instructions. Sorry.)

I am new to the DNN Community as well as Dnn Platform. We have been using Evoq Basic until recently. They are increasing their cost so we had to look at options. I researched the downgrade from Evoq Basic to Dnn Platform and have successfully completed the downgrade except for an issue with Module/Page Permissions. In Evoq, additional permissions are available but in Platform it's minimized to View and Edit. In Evoq it shows Content Manager and Content Editor with Edit and View permissions. After the downgrade which includes a script to remove several "Evoq" permissions those two roles are missing in the Permissions tab of both Page and Modules grid. I have screenshots and actual scripts that I ran if you need any assistance.

Cory Trento Senior Software Engineer Exit Row Solutions

Posted By Cory Trento on 3/21/2024 9:09 AM

I am new to the DNN Community as well as Dnn Platform. We have been using Evoq Basic until recently. They are increasing their cost so we had to look at options. I researched the downgrade from Evoq Basic to Dnn Platform and have successfully completed the downgrade except for an issue with Module/Page Permissions. In Evoq, additional permssions are available but in Platform it's minimized to View and Edit. In Evoq it shows Content Manager and Content Editor with Edit and View permissions. After the downgrade which includes a script to remove several "Evoq" permissions. I have screenshots and actual scripts that I ran if you need any assistance.

Cory Trento Senior Software Engineer Exit Row Solutions

Honestly, I would characterize what you have in DNN Platform as an upgrade.  I mean, you went from Evoq to DNN Platform, after all. 😎 

Anyway, the difference you're seeing now is that you have to manually create and assign those roles everywhere.  It's a time-consuming task on some sites, but worth it in the end. 

Now, for the granular permissions, those can be reproduced by someone writing a provider for you, but my personal experience over the years is that everyone wants the granular permissions, but few truly use it for what it was intended.  Most sites are better off using permissions at a combined site <> page <> module level.  This often can get you what you need.  It just needs to be planned in advance in order for it to be useful.😉 

 

You are right, not downgrade but upgrade. Such a smarter move on our part given our use case and how we have used DNN for our business. The manual solution might be time consuming but is there a quick way to script this for all page/module permissions? or do I have to touch each page/module and apply  permissions manually? Either way, it would be a small bump in timeline due to the nature of 175+ websites with 15-20 pages per site.

Thanks, Cory

The permissions will need to be planned ahead of time, based on how you intend to have people manage the site.  I recommend having a lower "admin" role that can edit content everywhere, and then determine how granular you need to get on other parts of the site.  The lower "admin" role would simply have edit permissions on all pages, but not be in the Administrators role.  Then, each page that needs to have a different person(s) manage the content there could have a role for editing on the page level, and I also tend to have a content-level role on some pages. 

Whereas the page-level editor would have someone in a role named something like Editor-Page-PageName, the content editor role would be something like Editor-Content-PageName.  In this example, the latter would have edit permissions assigned to all of the modules on the page you wish that role to manage.  The page-level role would have edit permission on the page like the "lower admin" role I mentioned above.  

Hopefully, I've explained it well enough.  If I haven't, please feel free to ask more questions.  Other than that, yes, it will be time-consuming to setup, but well worth the headaches you'll save yourself from in the long run.  😎😉

Not sure if anyone would benefit from having a script to assign the Content Manager and Content Editor roles to each page with Read and View permission, but if so, message me and I'll send you my MSSQL script that generated all the roles perfectly without having to manually add these on each page. This is especially helpful when you have 150+ portals with 20-25 pages for each portal.

if you don't mind downloading SQL files then you can get it from a shared Google Drive.... https://drive.google.com/.../view?usp=drive_link

Posted By Cory Trento on 5/16/2024 6:45 PM if you don't mind downloading SQL files then you can get it from a shared Google Drive.... https://drive.google.com/.../view?usp=drive_link

 

If you are a GitHub user, you could post to a "New gist" (via the + sign in the top bar on GitHub).  This would probably be viewed as less "risky" than clicking a Google Drive link.  That said, thanks for sharing - looks good!  ;-)