Home » discuss » Public forums » iMIS Community

Telerik RadMenu Nightmare

Posted February 25th, 2011 by KierenZ
| | | | | | | |

Hi All,

I am trying to edit the new 1700 template to fit with a website I am building. Most of the conversion is going well and I have to say that the new 1700 template is a lot cleaner and easier to understand than the previous templates. However, I am running into a lot of problems around the RadMenu component for the navigation.

RadMenu is inserting it's own styles and I can't find any way to override certain things like the background images.

Here is the problem:

The gray background image to that menu item should not be there, I've tried adding "background-image: none;" to practically every stylesheet item combination I can think of and it just won't disappear.

 

This is the stylesheet entry that's creating the background, found with Firebug:
 
 
.RadMenu_Default .rmRootGroup, .RadMenu_Default a.rmLink, .RadMenu_Default .rmGroup .rmText, .RadMenu_Default .rmLeftArrow, .RadMenu_Default .rmRightArrow, .RadMenu_Default .rmTopArrow, .RadMenu_Default .rmBottomArrow {
    background-color: transparent;
    background-image: url("WebResource.axd?d=vb8hCLoctoCFN1q4G54v9WCyrF9e2wA8FbqKjylDqRFckkkuGAuZDarS1HyHuLpBIETStla8-zlSzGk_mpyHkg2&t=634163770200000000");
}
 

That entry is being generated by the WebResource.axd page, as is the image that it's inserting and I can't see any way of stopping that happening or changing the items it inserts.

On the 1600 template, the NavMenu.skin file contained the classes that made up the RadMenu items and you could override them quite easily to style the menu how you liked, that functionality appears to have been lost in the new template and it looks like I am stuck with the standard RadMenu style.... unless someone can help me?

 

Regards,

Kieren Zealand

‹ Does anyone use major key (-) on the Customer Profile? Best Practice for WCM template design by 3rd party ›
login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Something to try...

On February 25th, 2011 Melissa Burpo says:

Hmm...maybe you could try adding those styles to one of your 1700 stylesheets and then apply the !important attribute to the background-image property, so that it beats out the auto-generated stuff. For example:

 

Give it a try and see if that works.

 

.RadMenu_Default .rmRootGroup, .RadMenu_Default a.rmLink, .RadMenu_Default .rmGroup .rmText, .RadMenu_Default .rmLeftArrow, .RadMenu_Default .rmRightArrow, .RadMenu_Default .rmTopArrow, .RadMenu_Default .rmBottomArrow {

    background-image:none !important;
}

login or register to post comments

How to Modify 1700 Rad Menu, ASI doesn't support this template

On February 25th, 2011 jharrison says:

We have run into the same issue. The only way to solve it is to rewrite all of the CSS styles for the menu with your own by calling in a stylesheet at the end of your master page template. The style sheet has to be called in separately at the end to MAKE SURE that you re-write the styles in the WebResource.axd file.

We checked with ASI tech support and they do no know how to access the WebResource.axd that is generating the CSS for this menu. So the only way to make your own is to overwrite the css that this AXD file creates.

We also asked tech support for a little more info and finally were told that they DO NOT SUPPORT the 1700 series template. This is a surprise and a shame, as I agree that it is much easier to build a site with this template than the 1600 series.

One work around is to put the 1600 series menu in your 1700 template. If you need to have drop downs you can turn this functionality on. It works, and in the end of the day it is just all ASP.NET (ASP.NET doesn't 'know' you are using an older menu...). one note the older menus don't work in Chrome or Safari.

Hopefully ASI will give us access to the CSS for the RAD menu one day soon, because it is a very good menu system and works on all browsers.

If someone knows how to edit the WebResource.axd files please share.

Thanks

James Harrison

login or register to post comments

Thanks for the responses

On February 28th, 2011 KierenZ says:

Thanks for the responses here, Melissa's method worked great with the least amendments to the code.

I'm sure your idea would work James, but I don't like the idea of adding stylesheets into the body of the page, and most of the sites I've read regarding the subject regard that as unsupported and not a very suitable solution except in extreme cases.

The idea of going back to the old style RadMenu did cross my mind, but quite frankly the biggest reason for going with this template was actually to get away from the previous "div inside a div, inside a table, inside a div, inside a table, inside a div....." method that old menu used! Also the fact that it is not useable on a vast number of web clients was a serious downside for our clients.

I do have to agree though, that it is a very strange way for ASI to operate to be showing off the merits of a new template at the UK NiUG conference a few months ago, and then to state categorically that they don't support it if you do try to use it.

 

Thanks again for the speedy responses both of you. Now I just have to wrangle IE7 back into line with proper W3C compliant browsers!!

 

Regards,

Kieren

login or register to post comments

If you have access to

On March 1st, 2011 nmuhammad says:

If you have access to RadMenu tag in the template, then try setting these properties of the tag to false

EnableEmbeddedSkins
EnableEmbeddedBaseStylesheet

This should stop webresource.axd styling of the RadMenu control.
Furthermore, you could create your own skin to modify the look and feel of the control.
Try searching on RadMenu custom skins on google, you'll find a lot of help around.

WebResource.axd is part of the ajax framework, which allows .net controls to bundle in javascript which is eventually injected at runtime as and when required.
Unfortunately you cannot edit webresrource.axd unless you want to write one of your own controls.

Nasser
Avion Software
www.avion-software.com

login or register to post comments

I'm sure your idea would

On March 12th, 2011 jharrison says:

I'm sure your idea would work James, but I don't like the idea of adding stylesheets into the body of the page, and most of the sites I've read regarding the subject regard that as unsupported and not a very suitable solution except in extreme cases.

I meant put a link to your style sheet at the end of the master page, not the actual styles in the master page.

 

Nasser, thanks for the rad menu tags , I will try that out. It would be great to use the Rad menu natively as it is meant to instead of creating work arounds

James

 

login or register to post comments

Would this help

On April 17th, 2011 Andie Millet says:

Would this help http://www.asp.net/cssadapters/. I use this in the 1600 templates to style my secondary navigations.

login or register to post comments

Any Luck?

On May 23rd, 2011 tmndi says:

Has anyone had any luck with this topic? If you did, did you add new styles or did you add a new skin to the app_themes folder? 

Terry Hammond enSYNC Corporation Fort Worth, TX terry@ensync-corp.com

 

login or register to post comments

One solution

On August 31st, 2011 james_schwartz says:

I ran into this exact issue tonight and at first I tried to override the RadMenu styles, but this quickly became a nightmare.

I took Nasser's advice and decided to create my own control that does the exact same thing as the PageNavR control *except* it sets EnableEmbeddedSkins and EnableEmbeddedBaseStylesheet to false on the RadMenu control.

Now I don't see all the styling that is defaulted on the RadMenu control and I can control the styles myself.

Would certainly be nice if these two properties were exposed on the PageNavR control so that we could simply set these properties in the PageNavR tag in the master page. It shouldn't take ASI more than 5 minutes to update the code to accommodate this, so hopefully this request gets into the next release :)

-James
Bursting Silver

login or register to post comments