Hi Lee

I have just created a few child sites.

I am having difficulty trying to access some admin and host pages in the child sites.

 I am taken to an error page instead. 

Bla Bla ***** Message: System.Exception: Unhandled Error: ---> System.Web.HttpException: The file 'n' does not exist *********Bla Bla Bla

I expected some problems because I am still using Inventua Menu, I understand that DNN 4.4 0 has a problem with this menu. However I understood that errors only occured if not logged as host or admin.  (I was logged in as host)

(As my site is 'install DNN", I am unable to fix menu bug)

I changed to menu HouseMenu and still I was unable to gain access, but this time I was unable to open any host or admin pages.

Does DNN 4.4 0  have a problem with all menu's systems except SolPartMenu?  

I have yet to change 'child' menu's over to SolPartMenu, I thought that I would ask first, in case this is a regular and expected error with child sites and the problem is something else.

Lynn

 

 

Hi Lynn,

I have recently tested version 4.4 using the house menu on a child portal with a SIFR skin and it works fine.

The only problem I came across is that you can't use the drop-down actions token on the containers. You have to use the solpart actions token.

Hope this helps,

Thanks,

PS. I also found that the beta version of the house menu does not display the menu correctly so I was using the latest official release of the house menu.

Hi Lee

Thanks for the reply and information.

Yes I was using the Housemenu beta 1.4. Also although I did not insert the HouseMenu inside a container, the containers on the page did not have solpart action tokens, which might have had a strange adverse effect (sending errors from a distance).

BTW Where might I obtain the official Housemenu Release. I have searched, but so far I am only able to fine the Beta 1.4 version as the latest.

It is a relief to realise that a posible, simple solution might be to hand.

Thanks


Lynn

Hi Lynn,

You can download the HouseMenu skin object from this address: http://houseofnuke.com/Downloads/ta...fault.aspx

scroll down and select v1.3.0

On the containers  I am not using the HouseMenu.

If you recall from the video tutorials, I said to use the drop down list token instead of the solpart token ie:

[DROPDOWNACTIONS] instead of [SOLPARTACTIONS]

This was because the SolPartMenu was not compatible with XHTML transitional mode.

The problem with the current version of 4.4 is that it throws an error if you use the [DROPDOWNACTIONS] token in your containers, so you need to replace this with [SOLPARTACTIONS] - the good news is that SolPartMenu is now compatible with XHTML transitional mode.

Hopefully in the next release of 4.4.x they will release a fix for the [DROPDOWNACTIONS] token.

Once it is fixed I will be using [DROPDOWNACTIONS] again. - I prefer to use this if I am using the HouseMenu rather than SolPartMenu as the main menu -  because it seems pointless having the SolPartMenu load up all of its Javascript code in the background when you are just using it on the containers menus. - So you should get a small performance benefit from using [DROPDOWNACTIONS] instead of [SOLPARTACTIONS] when using the HouseMenu as the main menu.

Hope this makes it clearer,

Thanks,

Hi Lee

Thanks for the explaination, yes it does make sense. Also as I am only using DROPDOWNACTIONS, in the main and child containers, is a possible explaination why I have been getting other exception errors.

I will have to make a new set of containers with SOLPARTACTION. I will copy/paste the current set of containers and change the DROPDOWNACION to SOLPARTACTION, still it is a nuisance as I will have to change containers in every page. Or alternatively to save changing every page, edit the current containers to be SOLPARTACTION and make an extra set of DROPDOWNACTION containers for a later date. It is starting to feel like a lot of extra work.

Thanks for the link to the Housemenu. When you said not to use the beta version (I wrongly assumed you refered to 1.4 not 1.3 ) I was searching houseofnuke site and others under the wrong conclusion that HouseMenu 1.4 Alpha was available somewhere, ooops! my mistake.

Thanks once again for your help, as per.

Regards

Lynn

Hi Lynn,

Yes it is extra work and if anyone else reading this is using [DROPDOWNACTIONS] I wouldn't ugrade to 4.4 until they fix the bug.

What I would do is take a copy of your containers and keep them the same name as the current containers and edit the tokens to be [SOLPARTACTIONS] - when you upload the edited containers all of your current containers will automatically get updated and use the solpartmenu for the containers.

Then, later on when the bug has been fixed re-upload your original containers and it will change all of them back to the original containers.

You should not have to manually edit any of your pages, it should just be a matter of uploading a set of containers.

Thanks,

PS. I would first of all test it out with one container on a single page to make sure you have done it correctly before updating your entire site.

Hi Lee

Thanks, oh it is not as bad as I thought.

As I have created containers in several colours, I was thinking of hours of extra work. So all I need to do is edit all the tokens to be [SOLPARTACTIONS] FTP it and it will automatically change the container.ascx file.

I thought that I also needed to editl the "Register TagPrefix="dnn" TagName="DROPDOWNACTIONS" Src="~/Admin/Containers/DropDownActions.ascx" and the .dnnROPDOWNACTIONS runat="server" id="dnnDROPDOWNACTIONS". Then parse each container.

Thanks

Lynn

p.s. I don't know where the smiley face came from, it is not mine.

he he, sometimes the smilies appear when you least expect it! - other times they don't appear when you want them to!

Hi Lee

I have now successfully changed all my containers to SOLPARTACTIONS, what a tedious task.

I have also successfully uninstalled the Housemenu 1.4 beta and uploaded/installed the Housemenu 1.3, however, this has not helped.

The error below is when I tried to open a host page using Housemenu in my Main (Parent) site (same problems occur in child sites)


----------------------------------------------------------------------------------------------------------------

Server Error in '/' Application.
--------------------------------------------------------------------------------

The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /Host/File Manager.aspx

-----------------------------------------------------------------------------------------------------------------------------

As I am using a custom menu inserted into a text/html module on my parent site, I am unable to view any "Host or Admin" pages via this menu, so it is neccessary for me to have access to a second menu linked to the core, so I installed Housemenu.

Fortunately I also now have a page (admin access only) using SOLPARTMENU so I can access host and admin settings, so far only SOLPARTMENU only on the parent site.

Thanks

Lynn