I got it to work by adding the info described above and adding <%@ Register TagPrefix="dnn" TagName="ACTIONS" Src="~/Admin/Containers/SolPartActions.ascx" %> to the top of the page, but now when I hover over the menu that contains the module options the menu doesn't show near the title, it gets crammed in the upper left corner of the window. I think someone earlier was decribing the same relocation of teh menu.

Thoughts?

thanks,

John

Hi,

I am still not getting this to work. I still get the "Object reference not set to an instance of an object" exception when I try to create a new blog. I am on DNN 5.1.4 with Blog module 3.5.1.

In my container ASCX I have the following lines:

 Any other ideas?

Thanks,
Mike

<%@ Register TagPrefix="dnn" TagName="ACTIONS" Src="~/Admin/Containers/SolPartActions.ascx" %>
...
<dnn:ACTIONS runat="server" id="dnnACTIONS" ProviderName="DNNMenuNavigationProvider" ExpandDepth="1" PopulateNodesFromClient="True" />

I updated from 4.9.3 to 5.1.4 yesterday and just notice this issue as well with my Blog module. No other modules presented a problem with the actions menu. When I make the recommended fix to update the container.ascx file, it disturbs all other action menus for any module using same container. Menu is far left, and action drop down gif is a red box with black down arrow. I tried changing the container for the module and it had no effect.

What is more interesting is that I note on the same page a "New Blog" module appears above my primary blog. It has the same settings (blog description, etc.) as my original blog. I don't recall creating a duplicate, and I am wondering if this was created somehow during the upgrade to v5 by mistake. Perhaps the problem is not with the container (esp. since the containers work with all other modules site wide) but with a database problem after upgrade.

Was there a final resolution to the problem? A month ago and no new comments.