TinyMCE HTML codes working in new branch but not in copied iwstore\branches

Hi Guys,

I'm having a strange issue. I have done migration from old server v6,7.2 to new server v7.4.1. TinyMCE customizations render HTML codes correctly in a newly created branch on new TeamSite server v7.4.1 on ouput/preview. However, these HTML codes are not rendered giving me errors on existing branch copied from old TeamSite server v6.7.2. On old server same TinyMCE customizations renders correctly for existing branches.

Any ideas why issue occurs with existing branches on new server where ouput/preview complains about HTML codes &nsbp; ...etc. Output will only show when all these HTML codes are removed.

Thanks

Phlatcalm

Find more posts tagged with

Comments

Rick Poulin

It's hard to answer that without having access to see your system. There's nothing overly different in formspub between those versions, and TinyMCE is exactly the same.

You'll have to find what's different between the working copy and the broken one -- either content or JS exceptions or something else. Once you know the difference we can perhaps help you figure out the why.

Basil Smart

Thanks, I see the issue but it may be with interwoven. Old server templates work well with extension="xml" but not on new server, even on new branch/new server.

I thought it was working in new branch but it isn't, on further obersvation, example test from interwoven engineers had extension="html", which I overlooked in templating.cfg.

When I tried their test example on new server using extension=xml" with HTML codes it breaks on new server. HTML codes doesn't break on old server with same template config.

Rick Poulin

Is there a reason why you need to use xml rather than html?

Basil Smart

The client uses xml on old server, so I wanted to keep the same convention and not change it on new server.

Rick Poulin

Ok, but are you outputting XML or HTML? From what you were saying, I'm thinking you're producing HTML so it shouldn't matter what setting you had in the past -- make it correct now. You might have to change more than one "convention" during an upgrade, you know.

Basil Smart

Okay thanks for reply, I'll let you know outcome on resolution.