Sign In  |  Register
 
 DotNetNuke Powered!
DotNetNuke Support Forums

repository postback breaks skin in IE6/7 and FF

Rate this topic:

Please Register to post a reply.
Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

AuthorMessages
packrat
Posts:64



05/02/2007 9:51 AM  

Hi John,

I'm having a problem with my skin breaking when using the repository module.  It only breaks it when a postback is performed.  I have not received much help on this one over on the dnn forums so I thought I would post it here.  Most folks over there say they are not seeing the behavior I have descibed, but everyone here and in our parent community is seeing it so I think the others may not be looking closely enough.  Here is the thread form the dnn forums detailing the problem.

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/54/threadid/129675/scope/posts/Default.aspx

Thanks in advance for any help you may be able to offer.

Paul

John Mitchell
Posts:3033



05/02/2007 10:06 AM  
Yes, I can see the problem. It's fairly subtle to casual observation but it is as you explained it.

The only difference in the output of the pages for the before and after is that the repository has injected the window.open script at the very top of the document.

I think you are on the right track by trying to figure out how to get a new window without a post-back and that javascript injected at the top.

Maybe you can set it up so that you do not use the built-in visit link, but instead build your own visit link in the description of each item. The link could be a simple anchor with target="_blank"
packrat
Posts:64



05/02/2007 10:34 AM  

I might try temporarily relocating that menu just to test how and what that js injection is affecting.  The problem with not using the visit link is that it is referencing the [DOWNLOAD} token which is then connected to a interface for a user form associate with the directory template:

Title:

URL:

Description:

I need to continue to have this feature because i am going to allow teachers to use a "suggest a link" form located on the same page so that they can add educational web resources to the repository, similar to this:

http://www.faktnet.com/DotNetNuke/Suggestwebsitetothedirectory/tabid/144/Default.aspx

This is a must have feature for us since i have already sold the concept to the administration.  I don't think it would be very user friendly if each teacher had to learn how to create a link for their url in the description.  I still think the module should have another token [URL] that doesn't require a post back.

So, here's where I'm at:

I continue to troubleshoot my skin since I know it only happens with my skin and not others.  I can only do this for a little while longer and if I can't get it fixed, I will have to hire someone who knows more than me  to troubleshoot it and make suggestions - any takers?

Redo all my skins in tables since it appears divs are repositioning themselves during post back. I would have to be pretty desperate for that to happen.

Give up and remove the module.  I would lose one of the most valuable features to my site.

Any more thoughts or are you ready to get paid:-)

Paul

 

 

 

John Mitchell
Posts:3033



05/02/2007 10:43 AM  
For a quick test, see what happens if you go into default.aspx and put another carriage return at the top of the page.

If that doesn't work, then you could use a PageBlaster replacement to reposition that invalid javascript.
packrat
Posts:64



05/02/2007 12:36 PM  

Hi John,

The added carriage return did not make any difference.  I did remove some unnecessary css related to the top menu and it fixed that problem. I also completely removed the hover class form the aggregator skin. The tabs still get "smashed"  on a post back but I can live with that.  I only have the left pane problem to deal with.  This is where my Nav Menu resides.  I will continue to look through that specific css to see if I have something causing a problem there. 

What do you mean by a pageblaster replacement page and repositioning the invalid js?  Why is the js invalid?

Thanks,

Paul

John Mitchell
Posts:3033



05/02/2007 2:50 PM  
The <script is being injected at the very top of the page, which is not valid html markup.

PageBlaster can allow you to change the output of any html in your page with replacment rules.

Sounds like you are almost there though.
Maybe just putting a fixed with on the left menu will be enough to keep it from getting squashed.
Please Register to post a reply.
Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Forums >DotNetNuke Support >General-DNN-Help > repository postback breaks skin in IE6/7 and FF



ActiveForums 3.7
Visit our Store for great DotNetNuke Modules and Skins
DNNMasters Sitemap/Google Sitemap 3.0

Item codeSM3-01
Price$29.00
Product Information 
DotNetNuke CSS NavMenu 3.3 (Developers)

Item codeCSSNM33DEV
Base Price$149.00
Product Information 
Snapsis PageBlaster 3.3.2 for DotNetNuke - Professional Edition

AuthorJohn Mitchell
Base Price$79.00
Product Information