Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

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.

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

8/4/2012 7:26:14 PM

Stone

Total Posts 27

View Posts

Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Hi Joe,

My website is running in an IIS 7.0, ASP.NET 4.0 and medium-trust environment.

After I upgraded from version 2.3.8.5 to 2.3.9.0, I found the layout of one-line top navigation was changed. Originally, the layout of navigation items is only one line, like 'Home | Site Map | Search | Sign In'. Now, it is changed into two lines. It looks like:

Home | Site Map
| Serach | Sign In

I view the page source from Firefox browser, an additional element like below was added between 'Site Map' and 'Search':
<div id='ctl00_SearchInput1_pnlS' class=''></div>

How did this happen and how to fix it? I have no idea.

8/6/2012 10:17:01 AM

Joe Audette

Total Posts 18439

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Hi,

How is it declared in your layout.master file?

It should be like this and then it won't have the extra div:

<portal:SearchInput ID="SearchInput1" LinkOnly="True" RenderAsListItem="true" runat="server" />

Hope that helps,

Joe

8/6/2012 12:46:08 PM

Stone

Total Posts 27

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Before and after upgrade, I change nothing in the layout.master file.

Here is the declaration in my layout.master file:
<div class="topnav">
<ul>
<portal:WelcomeMessage id="WelcomeMessage" runat="server" RenderAsListItem="true" ListItemCSS="firstnav" />
<portal:HomeLink id="HomeLink" runat="server" RenderAsListItem="true" />
<portal:SiteMapLink id="SiteMapLink2" runat="server" CssClass="sitelink" RenderAsListItem="true" />
<portal:MyPageLink id="MyPageLink1" runat="server" RenderAsListItem="true" />
<portal:UserProfileLink id="UserProfileLink" runat="server" RenderAsListItem="true" />
<portal:MailboxLink id="MailboxLink1" runat="server" RenderAsListItem="true" />
<portal:MemberListLink id="MemberListLink" runat="server" RenderAsListItem="true" />
<portal:SearchInput id="SearchInput1" LinkOnly="True" RenderAsListItem="true" runat="server" />
<portal:RegisterLink id="RegisterLink" runat="server" RenderAsListItem="true" />
<portal:LoginLink id="LoginLink" runat="server" RenderAsListItem="true" />
<portal:LogoutLink id="LogoutLink" runat="server" RenderAsListItem="true" />
</ul>
</div>

Is there a deeply hidden bug in somewhere else that makes things inconsistent?

8/6/2012 12:51:04 PM

Joe Davis

Total Posts 2253

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Did you add or change anything in your theme.skin? Specifically the portal:SearchPanel control?

8/6/2012 12:57:30 PM

Joe Audette

Total Posts 18439

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

You could add this to your theme.skin:

<portal:SearchPanel runat="server" DontRender="true" />

Hope that helps,

Joe

8/7/2012 1:25:57 PM

Stone

Total Posts 27

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

I tried and updated web.config to verify the result ...... no difference.

To modify the theme.skin file is not a workaround. Is there another idea to remove the additional <div> element?

So far, I don't know the root cause that the additional <div> element is inserted.

Stone

8/7/2012 1:32:14 PM

Joe Davis

Total Posts 2253

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Why is modifying the theme.skin not a workaround if it fixes the problem at hand? There may be another issue at play here but if modifying the theme.skin as we've suggested fixes your issue, then it is workaround.

Is there a reason you can't modify the theme.skin file?

Thanks,
Joe D.

8/7/2012 1:51:10 PM

Stone

Total Posts 27

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Let me clarify.

I did modify the theme.skin as you suggested. But the problem is still there.

What else is possible that an additional <div> element will be inserted over there? Why is there no such a problem in version 2.3.8.5?

Thank you,

Stone

8/7/2012 2:20:33 PM

Joe Audette

Total Posts 18439

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

I'm not sure why that theme.skin setting is not working but I am also able to produce the problem here and was able to fix it in code so it will be fixed in the next release.

For now can you use a css workaround?:

#ctl00_SearchInput1_pnlS { display:none; }

Best,

Joe

8/7/2012 2:27:48 PM

Stone

Total Posts 27

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

I prefer to wait for the next release, because currently I only upgraded my test website instead of the production website.

Thanks for all your help!

Stone

8/7/2012 2:29:43 PM

Joe Audette

Total Posts 18439

View Posts

Re: Layout Bug Found After Upgrading From 2.3.8.5 to 2.3.9.0

Actually the theme.skin setting is working for me but I was editing the wrong file and thought it was not working.

theme cache can be a stubborn thing sometimes, you might try recycling the app pool.

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