Custom CSS causing IE to shut down!
Custom CSS causing IE to shut down! We're mostly using IE 6 and ever since we installed custom CSS (feature purchased 2 days ago), visitors to the wiki are getting booted out of IE. Last time I asked for help from support the support person just said "use Firefox." This is NOT an option at my company and would really like some help on this issue.
Thanks
Thanks
1 person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Laura - sorry you're having trouble, can you tell me a little more about which version of IE you were having problems with?
-
Inappropriate?We're using IE 6 in most locations and IE 7 on a few of the machines. We do have Firefox installed on all machines and recommend it, but many users just use IE b/c that is what they are familiar with and I cannot control what they use. I deleted the CSS (modified elements of the Minimalist theme) and am starting from scratch to see if I can find what caused the problem and am also now doing all development in IE 6. I also suspect that it is the sidebar script modifications that might be causing problems though nothing crashed it until the CSS went live.
With the wiki.css I have noticed that although I change the "body" font in the CSS editor and it shows in the preview that in the actual pbwiki site nothing changes. Does this mean that even though I purchased the customizable CSS I am still stuck with the fonts from the minimalist theme? I noticed that this is the case for other elements that I change in the wiki.css that don't display in the live pbwiki. I noticed this question in an earlier post but the answer was not helpful.
any reply would be appreciated
I’m workin on it...
-
Inappropriate?Hi,
Could you possibly show me your CSS code? I can be emailed at vu.nguyen[at]pbwiki[dot]com
Thanks!
Vu
I’m the resident CSS dude, apparently
1 person says
this solves the problem
Loading Profile...





EMPLOYEE
EMPLOYEE