Preview is different in one workarea

Am I missing something elementary? We're running TS 6.7.1 SP1 on W2k3. When previewing any pages in one particular workarea they render differently (as if it isn't reading css properly) than any page in every other workarea. The css is consistent throughout Teamsite/Livesite and the css file to use is configured in 'Shared Resources' under the 'Site Map' tab in Content Center. Is there a css file that preview uses that I can check for consistency? I must be overlooking something simple. Thanks.

Find more posts tagged with

Comments

Ambuj

Am I missing something elementary? We're running TS 6.7.1 SP1 on W2k3. When previewing any pages in one particular workarea they render differently (as if it isn't reading css properly) than any page in every other workarea. The css is consistent throughout Teamsite/Livesite and the css file to use is configured in 'Shared Resources' under the 'Site Map' tab in Content Center. Is there a css file that preview uses that I can check for consistency? I must be overlooking something simple. Thanks.

I do not see any issue from TS side.... It must be some trivial manual mistake..

- Check the configuration in templating.cfg as how you have configured for both workareas?
- Check your TPL file and find out how many other associated files you are using?
- Check both the DCTs. I hope they are similar but still just to confirm.

jamessteel

Thanks... it's not just forms that display differently in preview in one particular workarea... it's all .page files.

I can preview a .page file in any workarea but one and they look right. If I go to the "problem" workarea and do a get latest on the same file and preview it there then it looks different. Everything looks ok being served by the LiveSite runtime so it seems to be a problem with preview in just one TeamSite workarea.

Adam Stoller

Thanks... it's not just forms that display differently in preview in one particular workarea... it's all .page files.

I can preview a .page file in any workarea but one and they look right. If I go to the "problem" workarea and do a get latest on the same file and preview it there then it looks different. Everything looks ok being served by the LiveSite runtime so it seems to be a problem with preview in just one TeamSite workarea.

This sounds like an iwproxy regex issue - or something similar.
A quick test might be to try renaming the workarea (temporarily?) and see if the problem persists - that and/or renaming the existing workarea, creating a new workarea with the original name of the problematic workarea and then updating it with files from staging and the old renamed workarea.

Between those tests you should be able to determine if the problem is tied to the name of the workarea. If so - then next steps are to determine if the workarea name is used in a proxy regex somewhere or if you happened to stumble across a "reserved" name or something that causes problems with the preview internals.

Out of curiosity - what is the name of the problematic workarea?

jamessteel

Thanks for that advice... I will have a look at the issue from a workarea naming perspective today as you suggest and post a reply subsequently.The anomolous workarea is named "Admin"

jamessteel

I now don't think this issue is attributable to naming of the workarea. ghoti, we had a visit yesterday by someone I think you may know, Brett Clifton, and he seems to remember coming across this at our organisation once before. The main symptoms seem to be that in preview the font size gets bigger than it's supposed to be and positioning of components is out of whack. I'll give him a couple of days to recover from jet-lag Smiley Wink

and then follow it up with him if no-one has any other suggestions?

Adam Stoller

I now don't think this issue is attributable to naming of the workarea. ghoti, we had a visit yesterday by someone I think you may know, Brett Clifton, and he seems to remember coming across this at our organisation once before. The main symptoms seem to be that in preview the font size gets bigger than it's supposed to be and positioning of components is out of whack. I'll give him a couple of days to recover from jet-lag and then follow it up with him if no-one has any other suggestions?

That sounds more like a CSS proxy issue then - which would still be attributed to the naming of the workarea --or-- you have CSS files in the workarea and they're different in that one workarea than the others (in which case it's a workarea content and not a naming issue)

jamessteel

All right... this issue was resolved by doing a 'Get Latest' in the affected WorkArea for the default.site file. It looks like this file was out of sync somehow or other and making sure that it was the same as the other WorkAreas did the trick. Thanks for your advice on this one! Smiley Very Happy