Forum Update

**TinCow** · 11-04-2012, 17:07

The forum has just received a significant software update. This update was a lot more complex than most and as a result many of our add-on features had to be adapted to work with the new systems. I have fixed all of the issues I was aware of, but I am certain that more will crop up in areas I haven't checked yet. Please post any issues you find so that I can fix them.

**Tellos Athenaios** · 11-05-2012, 03:04

Not really an issue, but still: the Org favicon is no longer a mask.

**drone** · 11-05-2012, 15:28

Might just be my old browser here at work, but I see:

Code:

'); var sidebar_align = 'right'; var content_container_margin = parseInt('290px'); var sidebar_width = parseInt('270px'); //-->

at the top of the page above the Org banner, but only in the main index page. Firefox 3.6, TWS2 skin.

**caravel** · 11-05-2012, 15:39

Originally Posted by drone

Firefox 3.6, TWS2 skin.

Why sticking with 3.6?

**TinCow** · 11-05-2012, 16:34

Originally Posted by drone

Might just be my old browser here at work, but I see:

Code:

'); var sidebar_align = 'right'; var content_container_margin = parseInt('290px'); var sidebar_width = parseInt('270px'); //-->

at the top of the page above the Org banner, but only in the main index page. Firefox 3.6, TWS2 skin.

That's part of the javascript code that drives the forum sidebar. Do you see the sidebar at all?

**drone** · 11-05-2012, 18:11

Originally Posted by caravel

Why sticking with 3.6?

Work machine, don't get me started.

Originally Posted by TinCow

That's part of the javascript code that drives the forum sidebar. Do you see the sidebar at all?

Yes, I do see the sidebar. I'll check it out from home to see if I can discern any difference in how it displays.

**TinCow** · 11-05-2012, 18:20

Originally Posted by drone

Work machine, don't get me started.

Yes, I do see the sidebar. I'll check it out from home to see if I can discern any difference in how it displays.

While you're still at work, try disabling javascript and see if it makes that code error disappear. That should help determine whether it's a javascript issue or something else.