www.mysite.com appears differently from mysite.com
Fri, 20/03/2009 - 02:39
I'm having a curious issue where the site looks great when I browse to http://mysite.com, but when browsing to http://www.mysite.com the left and right margins are gone. Furthermore, this only happens in Firefox for some reason.
I tried all the obvious browser-side things like clearing cache, erasing cookies, browser restart, etc.
I came up with a convoluted theory that maybe some server-side caching happened while I was browsing the site as an admin, when things get shifted around because of the extra admin controls that are displayed? Anyway, was wondering how to clear any caching prosepoint may do, and otherwise if you have any clues on how to solve this problem?
Thanks
Fri, 20/03/2009 - 04:43
#1
Offline
Did you try disabling
Did you try disabling caching, disabling optimized css, diabling optimized js, and then clearing the cache? I had a similar issue.
Fri, 20/03/2009 - 09:36
#2
Do you mean the left and right margins, or the sidebars?
See Clearing the cache to help with common ProsePoint issues on how to clear ProsePoint's caches.
As for your issue, do you mean the left and right margins are gone, or are the sidebars gone?
Is it possible that you were logged out, and hence some blocks weren't visible since they're admin-only blocks?
And hence the layout shifted as a result?
Fri, 20/03/2009 - 10:06
#3
Offline
Thanks for the suggestions...
Thanks for the suggestions... I tried these things, no effect. Problem persists.
Fri, 20/03/2009 - 11:17
#4
Hi Beng,
No all the content
Hi Beng,
No all the content is there, it's a layout issue. I am definitely logged out, and simply viewing any page as an ordinary user the left and right greyish background (which provides a left and right margin for the entire page) is gone when I view www.mysite.com, but looks fine with mysite.com. It's kinda mysterious, cuz it only happens in Firefox. Also I just tried on someone else's machine (although they have a Mac, I'm on Windows) and it seems fine for them, so I'm puzzled. Well maybe hopefully it's just a problem localized on my machine, in which case who cares, but would be reassuring to know what's wrong exactly.
Thanks for the help.
Fri, 20/03/2009 - 12:25
#5
When you say the margins are
When you say the margins are gone, you mean they are white rather than the greyish color right? That really sounds like a caching issue... that is exactly what I was seeing.
Try creating a new account and logging in with that account--and see what happens.
Fri, 20/03/2009 - 12:46
#6
Check the background image?
From your description, it may be that the background image is somehow missing or inaccessible. The background image is at .../profiles/prosepoint/themes/tma/tma/images/body_main.png of your site, so try visiting
www.mysite.com/profiles/prosepoint/themes/tma/tma/images/body_main.png
and
mysite.com/profiles/prosepoint/themes/tma/tma/images/body_main.pngand see if there's a difference.
Fri, 20/03/2009 - 12:52
#7
Nope margins are actually gone
Hi,
I tried your suggestion, same result.
No I don't mean that the margins are the wrong color, I mean that they're completely gone, so the content of the page is completely flush against the left edge of the browser window instead of being indented an inch. There's literally no margin at all, as if I had applied a CSS style of
body {
margin:0;
padding:0;
}
Thanks for the effort...
Fri, 20/03/2009 - 13:01
#8
background image
Beng, you're right it does look as if the bg image somehow hadn't been picked up, but I tried the link you suggested with and without the www prefix and in both cases got the bg image ok. Also logged into the server and confirmed the image is there in the filesystem. Very odd. I'm wondering now if maybe my Firebug plugin is flaking out? I'm going to try to find another Windows user to see if I can reproduce the problem on anyone else's machine.
Thanks again for the efforts to help...
Fri, 20/03/2009 - 13:36
#9
identical html delivered
I did a diff of the html delivered by the www.mysite.com versus mysite.com and confirmed that it's identical (except for trivial timestamp fields), so I'm really starting to suspect my browser now... will find another tester and report back.