Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site malfunctional when viewed in Firefox after upgrade to ver. 17Site malfunctional when viewed in Firefox after upgrade to ver. 17
Previous
 
Next
New Post
11/29/2012 7:25 AM
 

After upgrading Firefox to v. 17 my site (actually my homepage only) became malfunctional - slow responsiveness, endless read-in, etc. Other browsers - Opera, IE9, Chrome, Safari - did not have any problems

Seeking a solution I found this DNN Exchange thread where Gilles pointed to an applicable solution. However that did not work for me as you can see in my posts over there.

Having investigated the issue on my own I came to ff. conclusions:

1. deleting both files, i.e. MozillaPatch.browser and Net4Patch.browser from the App_Browsers did not change anything so FF17 could do without them at all;

2. downgrading Firefox to 16.0.2 solved all my problems with my DNN site regardless of those two files in the App_Browers folder

 Is there anything else we could do to keep up with FF17 without any problems on our dnn-powered sites?

Thanks for your valuable insight into this.

 Greg

My configuration: DNN 6.2.5 CE, IIS 7.5, .NET  4.0


English-Polish translations, one-to-one English/Polish tutoring, Windows server management, website development - HTML/JS/CSS/Razor
 
New Post
11/30/2012 11:05 AM
 

I'm having the same problems.  It is also breaking some of my legacy websites that were still using the FCK editor.  I have some 5.6x sites that are still on the FCK editor and the WSYWIG is not working.

I have another site where the FF 17 has broken the entire skin and menu system.

 It's only a matter of time before my customers start screaming. 

 
New Post
11/30/2012 5:37 PM
 

Well, I found the culprit. It was an outside source which sent malformed javascript through my iframe module.

For those who have problems with FF17 the link I gave in my first post would hopefully be of help. See Gilles's solution to FF17 problems there.

Interestingly, other browsers did not have any problems with my site then. Is FF17 oversensitive?


English-Polish translations, one-to-one English/Polish tutoring, Windows server management, website development - HTML/JS/CSS/Razor
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site malfunctional when viewed in Firefox after upgrade to ver. 17Site malfunctional when viewed in Firefox after upgrade to ver. 17


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out