possible mono sitemenu bug

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
5/15/2009 7:42:55 AM
evert
Gravatar
Total Posts 3
View Posts

possible mono sitemenu bug

mojoportal 2.3.0.1 (and older versions we tested)

mysql

debian linux / mono (latest and older version)

We have recently encountered an interesting potential bug in the mono implementation of mojoportal. We have been developing skins on a windows iis/asp.net/mssql system and deploying them on a linux / mono system.

The potential bug is that the menu appears to ignore the following specification in the layout.master page when running on mono and at least one of the pages has child pages:

<portal:SiteMenu id="SiteMenu1" runat="server" TopLevelOnly="true"
UseTreeView="false" HideMenuOnSiteMap="false" UseSpanInLinks="true"
Direction="Horizonatal" />

The iis/asp.net implementation renders this:

<div class="AspNet-Menu-Horizontal" id="ctl01_SiteMenu1_ctl00">
<ul class="AspNet-Menu">
<li class="AspNet-Menu-Leaf AspNet-Menu-SelectedLeaf">

 

<a href="link" class="AspNet-Menu AspNet-Menu-SelectedLeaf" title="title">
<span>text</span></a>
</li>

</ul>

</div>

The mono implementation renders this:

<div class="AspNet-Menu-Horizontal" id="ctl00_SiteMenu1_ctl00">
<ul class="AspNet-Menu">
<li class="AspNet-Menu-WithChildren AspNet-Menu-SelectedWithChildren">
<a href="link" class="AspNet-Menu AspNet-Menu-SelectedWithChildren" title="title">
<span>text</span></a>

<ul>
<li class="AspNet-Menu-Leaf AspNet-Menu-ParentSelected">
<a href="link" class="AspNet-Menu AspNet-Menu-ParentSelected" title="title">
<span>text</span></a>
</li>
</ul>
</li>
</ul>

</div>
 

It would appear as if the mono implementation ignores the parameters specified in the sitemenu control. This was reproduced using exactly the same skin files, and appeared to happen with the default skins as well.

5/19/2009 4:56:04 AM
evert
Gravatar
Total Posts 3
View Posts

Re: possible mono sitemenu bug

has anybody else encountered this issue or found a fix for it?

5/19/2009 5:23:14 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: possible mono sitemenu bug

I would report this to the mono bugzilla. I have not analyzed the markup but I have not noticed any problems with mojoportal skins under mono not rendering correctly in the browser. I think its possible issues like this are caused by differences in browser definition files on the platforms. I'm not sure debian gets the same browser definition files that opensuse gets. So if there are differences it can affect whether the control adapters work to render the menu.

Or it could be worked around possibly by adding css to handle either rendering the same.

Best,

Joe

6/10/2009 4:15:13 AM
evert
Gravatar
Total Posts 3
View Posts

Re: possible mono sitemenu bug

Hi Joe

We have just tested this in 2.3.0.4 b on a OpenSuse 11 Mono box, and the problem still appears to be happening. An easy css workaround is possible by just hiding the child ul, but this does result in uneccessary html in the page that is not being shown.

We have come across another minor Mono issue (also apparent in 2.3.0.1) - when adding a content instance to a page from the PageLayout.aspx page, the redirect returns a 404 error. It does actually perform the function it is supposed to, and hitting the back button shows that it has created the content instance, but it does mean that you have to keep hitting the back button.

Evert

You must sign in to post in the forums. This thread is closed to new posts.