DCR Saving Issue

rayvdz

Can anyone help me with this recurring problem that we seem to be having with Saving DCRs.

We recently migrated 6 websites into teamsite 5.0.1 (NT) from a(n awful) Lotus Notes content management system that we had. We are having problems editing and then saving some of these DCRs with the basic (HTML) templating interface after making simple changes. The symptoms include:
1) "Saving ..." appears at the top of the screen and the browser is busy for a second and then comes back, but the saving remains on the screen.
2) If we check the actual DCR file (through direct file access) the change has not been saved.
3) If you hit preview of generate, is says we have not saved the DCR, would we like to save it. If you hit Yes, the same thing in 1) happens.
4) the only way to get it to actually save the changes is to hit close, in which case it asks if we would like to generate the file. If we hit yes, it then saves the file and generates the HTML no problem.
5) This does not appear to happen to any DCR created in teamsite itself.
6) We have compared the two types of DCRs (one migrated from Lotus Notes and the one generated in TS) and the only difference is that the TS saved DCR uses the usual Windows CR/LF for new lines and the Lotus notes doesn't.
7) this does not effect how the HTML is generated.

What I want to know is:
1) Has anyone come across this before?
2) Is there an easy way to fix this without having to go through each DCR and resave them? Is there some TS configuration that can be tweeked to be able to handle this?
3) Is our diagnosis the actual cause of the problem or could it be something else??

Regards

Raymond van der Zalm
Australia

Adam Stoller

1) "Saving ..." appears at the top of the screen and the browser is busy for a second and then comes back, but the saving remains on the screen.

For TeamSite 5.0.1 this sounds like a known bug (might have been fixed in a SP - definitely fixed in 5.5.2) - in which syntactically incorrect validation-regex strings within the DCT would cause this behavior.

Check the DCTs for validation-regex's and verify that they are written for Regex(5) Extended not Regex(5) Basic.

If this is the case, we ship a utility that might be able to help you: iw-home/install/upgrade_dct_cfg.ipl - I'd suggest running it with the -h option first to get the details of how/when/why it might be used.

Hope that helps

--fish
(Interwoven, Curriculum Development)