Make Default Module Action Menu Configurable

[mikesmeltzer]

Follow-up to RFC #2700

Description of problem

Currently, the path to the default Module Action menu control (/admin/Menus/ModuleActions/ModuleActions.ascx) is hardcoded within the C# in the Container base class and does not allow a developer to configure the site to use a different action menu control by default on a per site basis.

The default action menu can be overridden on a per module basis by using a container that uses it's own action menu control. However, it would be ideal if we could define the action menu at a portal level and override the default action menu regardless of the container being used across the site, unless the container supplied it's own action menu as you can today.

Description of solution

Add a new Portal Setting called DefaultActionMenu, similar to how the default skin path, container path, etc. are stored.

Have the setting defaulted to the existing action menu path and allow users to swap this behaviour out by changing the setting value to point to an action menu control of their choosing.

This change would include the SQL to include the new portal setting in the DB, change the container base class to read from the portal setting instead of the hardcoded path, and changes to the Portal Settings and Portal Settings Controller to add the new setting into the API.

Affected version

This is net new functionality targeted for DNN v9.4.

Affected browser

This is a server side feature and is therefore browser agnostic.

[ohine]

Closing issue as PR was merged.