Import/Export Feature To Include Theme Options

[moorecreative]

Description of problem

A feature of the old DNN8 features for Portal Export & Site Wizard was that you could export a Site Template for a portal and then when applying a Site Template, you could, in the wizard steps, choose to apply a Theme, or skip that step and apply no different Theme changes during the process.

The current DNN 9x Import/Export feature is a wonderful improvement on those main features. The Site Template creation has checkboxes for several wonderful things to be selected or omitted from the Site Template, but "Include Theme & Containers" isn't one of them.

During the Import process, it applies the Theme of the site which is active during creating the Site Template to that target Portal when applying the Site Template.

I would like to suggest a checkbox either during creation (during Export action), or better/additionally during the selection of the Site Template (during Import step) which allows users a choice to not apply a Theme during the import.

Description of solution

The Theme for the Portal level Site Settings and/or the page Tab level Tab Settings are recording the Theme within the Export step of creating a Site Template. This means the data is already present and action is taken with that data on Import. The suggestion is to add interface options such as:

Basic Additional Function

• Add a checkbox in the Import screen which allows a user to de-select an "Apply Theme" option.
• Add logic to the process which can include or skip the Theme application steps based on passed settings

Extra Additional Function

• Add a checkbox in the Export screen which allows a user to de-select a "Theme" item in the "Include In Export" section

[moorecreative]

Also posted in the DNNCommunity.org Forums under Feature Requests https://dnncommunity.org/forums/aft/3012

[stale[bot]]

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[bot]]

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!

[moorecreative]

Timo says, and I quote, "I think this would be a great improvement" glowing endorsement for a wonderful improvement!

When I retire and invent a time machine, I'll learn more about DNN core project development so that I can come back in time to submit code to help with this improvement.

Until then, I'll start working on my time machine.