High,

I downloaded the CTP2 of DNN 7.0.0, and my first impression is quite positive. The install went like a charm, and most of my custom modules seem to work.

What I don't like:

• before being able to edit a module, I have to switch to edit mode on the page, and this for every time I change the page. This is especially a pain when I want to install a new extension from Host :: Extensions. Before being able to get the module action menu, I must change to page edit mode.
• a lot of the link buttons (or command buttons) in the standard skin appear as they would be disabled (the grey color is too light in my opinion), and this is a bit confusing
• in the control bar, the tiles for "new module" on a page look very nice, but if you change to "All categories", it is a pain to scroll horizontally to find modules at the end of the alphabeth
• new empty pages fire an error because they can't find the Dark Night skin (which is not there, that's true). When inspecting the page settings, the skin and container is set to "undefined". After changing to "site default" or a present skin, it works.
• did the UX guidelines change? Some of the classes (e.g. dnnFormRequired) seem not to be implemented.
• to be continued... :-)

Best wishes
Michael

The effect of the Page Edit button "enhancement" on module action menu visibility is a serious issue for more complex modules such as my ePrayer forge project which exposes action menu items such as "Manage Moderators", "Moderate Requests", "Manage Users", "My Requests", "My Preferences" to users who are not page or module editors. As display of those action menu items is controlled by custom permissions within the module's view control the user unless granted page or module edit permission will not have the Page Edit button available and thus will never see the module action menu. It will be necessary to forego use of the action menu and expose each SecurityAccessaLevel.View action menu item as a button or in a custom menu within the module control.

As for the Admin modules such as Extensions, I believe that a change will be made so that the module will be placed into edit mode upon browsing to the page, thus exposing the action menu to those with the appropriate permissions.

Please see my reply to your other post on UX form pattern changes and the dnnFormRequired css class in particular.