I've developed an ascx to show a custom navigation menu. When I try to register it in the Module Definitions page inside the Skin Objects "Module" the drop down list is disabled and has the "View" option selected, because of that (I think) the control never shows in the list of recognized tokens. I guess this is a bug but I want to be sure before submiting it in Gemini.

Regards

if you want to register your control by hand, you can also use some sql, that would look like this:

IF ( SELECT COUNT(*)
  FROM {databaseOwner}{objectQualifier}ModuleControls
  WHERE ControlKey = '[YOURSKINOBJECTNAME]') = 0
BEGIN
  INSERT INTO {databaseOwner}{objectQualifier}ModuleControls
    (ControlKey, ControlTitle, ControlSrc, ControlType)
  VALUES
    ('[YOURSKINOBJECTNAME]' , '', 'DesktopModules/MLLanguageSelector/MLLanguageSelector.ascx', -2)
END
GO

DNN Blog | Twitter: @erikvb | LinkedIn:

I had used the add skin objects control before to add the DNN360Menu to replace SolPart, but that was on DNN 4.4.1.

The first time I tried to add a control in  4.5.3 in skin objects was for the DNN360Menu. I did not realize that the type was VIEW instead of SkinObject and went through with the install and the skin object works in my skin.

I was about to install this on a new test site and realized that it said VIEW instead of SkinObject, so I went back to look at the previous install and I see now that I cannot see the skin object in the list. But it does work, as my menu functions properly. So I just went into the ModuleControls table and changed the ControlType from 0 (VIEW) to -2 (SkinObject). Now the menu still works and the skin object is visible in the list.

Does this sound reasonable or could I have created a problem elsewhere by doing this?

Thanks.