Page 5 of 9

Re: New site glitch report

Posted: Sun Mar 15, 2015 9:53 am
by copeg
markskor wrote:Now about this codding?
First Mike with the carp wrangler, and now you and Greg doing cod? Fishing-wise, things are going downhill.
I'll take what I can get - spent hours fishing in the surf yesterday with nothing to show for it.

Re: New site glitch report

Posted: Mon Mar 16, 2015 11:56 am
by maverick
Update: The header columns are lining up inside the text box as seen in the photo below but one
can still write and post text.
Image

Re: New site glitch report

Posted: Mon Mar 16, 2015 3:55 pm
by rlown
Mav, I'm thinking your kitchen's pc didn't have its browser cache cleared. You have to do this on any computer you use to access HST.

instructions at: https://support.mozilla.org/en-US/kb/ho ... efox-cache for firefox.

Russ

Re: New site glitch report

Posted: Mon Mar 16, 2015 4:26 pm
by maverick
Cache was cleared, same issue Russ.

Re: New site glitch report

Posted: Mon Mar 16, 2015 6:12 pm
by BSquared
I'm seeing exactly the same thing as Maverick, and I think it just started to do that. Here's a screen capture of what it looked like:

Re: New site glitch report

Posted: Mon Mar 16, 2015 6:21 pm
by ERIC
I cleared cache in the backend. Let me know if that helps. For good measure, clear your browser cache one more time.

Re: New site glitch report

Posted: Mon Mar 16, 2015 6:31 pm
by ERIC
Please let me know what operating system, browser and screen resolution you are using so I can address the issue.
BSquared wrote:I'm seeing exactly the same thing as Maverick, and I think it just started to do that. Here's a screen capture of what it looked like:

Re: New site glitch report

Posted: Mon Mar 16, 2015 6:57 pm
by Jimr
I see it as well. Windows 8.1 Firefox 36.0.1 resolution 1600 x 900

Re: New site glitch report

Posted: Mon Mar 16, 2015 7:09 pm
by maverick
Running same computer, same info as indicated earlier, cache cleared again, same issue Eric.

Re: New site glitch report

Posted: Mon Mar 16, 2015 7:16 pm
by ERIC
OK, I see it now. Thanks. Think this is only an issue with Firefox. I'll look into it.