×

Notice

The forum is in read only mode.

TOPIC:

16 years 2 months ago #7

Interesting. I haven't seen this error. Can you each tell me what browser and version you are using? I switched the site to use compressed output when delivering pages, which has sped the site up and has dramatically reduced the bandwidth used. Most browsers should handle this.

The fact that it works on a retry suggests it's not a "deep" issue, but I'd like to figure out if this GZip function is what is doing it. It's quite a common feature, so I'd be surprised it was causing a major problem, but it is the only change I've made to how the site delivers pages in the past week or two.

Atticus, the bridging mechanism between the front site and the forum is quite clunky. When you change your e-mail using Your Details on the front page, it doesn't always update the one stored in the forum part, and vice versa. Check your profile in both parts of the site to be sure they are both set to the one you want. I'd do it for you now, but I don't know if you updated via your forum or front end profile <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->

When the site migrates to Beoir there will be a considerably better mechanism to handle this.

16 years 2 months ago #8

IE7

16 years 2 months ago #9

Actually, can each of you also answer the following:

Are there extended error messages, or just that?

Is it only when you hit the link from a topic notification mail or do you get it when browsing the site normally?

Is it every time?

Is it on the forum only, or also on the main site?

Any other patterns you notice before you get this error?


Just tested following a notification link on IE 7 (7.0.5730.13) with no issue. Also works for me on FireFox 3.5.2.

Thanks guys, we'll figure it out.

16 years 2 months ago #10

[quote:1ojuw9zq]Are there extended error messages, or just that?[/quote:1ojuw9zq]
Content Encoding Error
Server response could not be decoded using encoding type returned by server.
This is typically caused by a Web Site presenting a content encoding header of one type, and then encoding the data differently

[quote:1ojuw9zq]Is it only when you hit the link from a topic notification mail or do you get it when browsing the site normally[/quote:1ojuw9zq]
Can happen with both

[quote:1ojuw9zq]Is it every time?[/quote:1ojuw9zq]

No. quite sporatic.

[quote:1ojuw9zq]Is it on the forum only, or also on the main site?[/quote:1ojuw9zq]
Only the forum.

[quote:1ojuw9zq]Any other patterns you notice before you get this error?[/quote:1ojuw9zq]

I don't get the error with IE8.

16 years 2 months ago #11

&amp;quot;Barry M&amp;quot;:2s2tq6hm wrote: Atticus, the bridging mechanism between the front site and the forum is quite clunky. When you change your e-mail using Your Details on the front page, it doesn't always update the one stored in the forum part, and vice versa. Check your profile in both parts of the site to be sure they are both set to the one you want. I'd do it for you now, but I don't know if you updated via your forum or front end profile <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->[/quote:2s2tq6hm]
Ahhhh, didn't know there was two log in areas. I always logged in on the main page and always wondered why there wasn't a place for more detailed profile editing. It's located on the top righthand side of the main banner. All fixed now. Well done! Keep up the good work! <!-- s:D --><img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" /><!-- s:D -->

16 years 2 months ago #12

Hahaa! <!-- s:D --><img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" /><!-- s:D -->

Yeah, the profile stuff in the front end is crap. I may make the forum the place where users first register in the next site so there's a chance to enter more information immediately on registering.
Time to create page: 0.150 seconds