nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue comparing the DCR versions

Jenni

Hi All,

Thanks in advance. We have recently migrated the TeamSite to 7.2.1. We also did a path change for the inline scripts of the DCT. Now everything related to the DCR works but, when we do a version compare for the DCR, the older version of the DCRs still refer to the old path of the DCT. Does anyone know what can be done to fix this issue?

Windows 2008 VM
TS 7.2.1

Find more posts tagged with

Comments

Adam Stoller

Hi All,

Thanks in advance. We have recently migrated the TeamSite to 7.2.1. We also did a path change for the inline scripts of the DCT. Now everything related to the DCR works but, when we do a version compare for the DCR, the older version of the DCRs still refer to the old path of the DCT. Does anyone know what can be done to fix this issue?

Windows 2008 VM
TS 7.2.1

I assume your last sentence meant to say that the historical versions of the DCRs (accessed through editions?) refer to the historical DCTs which refer to the historical inline script paths - yes?
This would seem logical to me as you are essentially looking though a "window to the past".

If you create a [temporary] workarea on the same branch and populate it with the contents of the edition you were looking at - and then update the DCTs in that workarea from the staging area (make sure you don't submit anything from this [temporary] workarea!) - you should then be able to compare the DCRs within the two workareas rather than comparing the current DCR against an historical DCR within an edition.

Jenni

I assume your last sentence meant to say that the historical versions of the DCRs (accessed through editions?) refer to the historical DCTs which refer to the historical inline script paths - yes?
This would seem logical to me as you are essentially looking though a "window to the past".

If you create a [temporary] workarea on the same branch and populate it with the contents of the edition you were looking at - and then update the DCTs in that workarea from the staging area (make sure you don't submit anything from this [temporary] workarea!) - you should then be able to compare the DCRs within the two workareas rather than comparing the current DCR against an historical DCR within an edition.

Hi,

Thanks for the reply. We are not accessing the editions. Here is the scenario:

Say there is a DCT (abc/def/inline.pl) and DCRs created based on that DCT. The DCR is submitted and Version 1 is created for the DCR.
The DCT inline path is changed to (ghg/sge/inline.pl).
The existing DCR is edited/submitted/Version 2 is created.

Now if we compare version 1 and Version 2, we get an error message stating that the DCT is referring to the old inline path.

But id I again edit the DCR, submit, create Version 3 and do a compare between Version 2 and 3, there is no problem.

Migrateduser

Either create a copy of your scripts and put them in the old location, or run makelink to your scripts like you did for your `iwhome`.

Here is the iwhome example that I gave you a while back.

mklink /D e:\iw-home e:\Interwoven\TeamSite

Jenni

Thanks for the suggesstion. I will give it a try and keep you updated.

Adam Stoller

Hi,

Thanks for the reply. We are not accessing the editions. Here is the scenario:

Say there is a DCT (abc/def/inline.pl) and DCRs created based on that DCT. The DCR is submitted and Version 1 is created for the DCR.
The DCT inline path is changed to (ghg/sge/inline.pl).
The existing DCR is edited/submitted/Version 2 is created.

Now if we compare version 1 and Version 2, we get an error message stating that the DCT is referring to the old inline path.

But id I again edit the DCR, submit, create Version 3 and do a compare between Version 2 and 3, there is no problem.

If you're comparing the current version with an historical version you are using editions - they're just unnamed editions - and hence you are running into the contextual problem that I was talking about before.

If you go through the process of creating the temporary workarea and populating it with the historical version of the DCR (but the current version of the DCT) you can compare the files between the two workareas and should not run into the contextual problem.

Jenni

Either create a copy of your scripts and put them in the old location, or run makelink to your scripts like you did for your `iwhome`.

Here is the iwhome example that I gave you a while back.

mklink /D e:\iw-home e:\Interwoven\TeamSite

Hi Talgaard,

I tried your cmds and below are the output. It says that the file already exists (althought my cmd is for creating a directory link). Any ideas?


C:\Users>mklink /D \iw-home \Interwoven\TeamSite
Cannot create a file when that file already exists.

C:\Users>rmlink \iw-home
'rmlink' is not recognized as an internal or external command,
operable program or batch file.

Migrateduser

Hi Talgaard,

I tried your cmds and below are the output. It says that the file already exists (althought my cmd is for creating a directory link). Any ideas?
C:\Users>mklink /D \iw-home \Interwoven\TeamSite
Cannot create a file when that file already exists.

C:\Users>rmlink \iw-home
'rmlink' is not recognized as an internal or external command,
operable program or batch file. 

Don't use those as is. You already did that a while back.

What was the full path (from the root) of your inline call?
What is the new full path (from the root) of your inline call?

Jenni

Don't use those as is. You already did that a while back.

What was the full path (from the root) of your inline call?
What is the new full path (from the root) of your inline call?

Original path: d:\\iw-home\\iw-perl\\bin\\iwperl.exe d:\\iw-home\\httpd\\iw-bin\\perlscript.ipl

New path: d:\\iw-home\\TeamSite\\iw-perl\\bin\\iwperl.exe d:\\iw-home\\TeamSite\\httpd\\iw-bin\\perlscript.ipl

I also tried the below one:

C:\Users>mklink /D

\iw-home\iw-perl\bin

\iw-home\Teamsite\iw-perl\bin
Cannot create a file when that file already exists.

nipper

The link is there, does that inline work ? Try that command from the DOS shell, though you may need to get rid of the extra \

Jenni

The link is there, does that inline work ? Try that command from the DOS shell, though you may need to get rid of the extra \

No luck..

C:\Users>d:\iw-home\iw-perl\bin\iwperl.exe d:\iw-home\httpd\iw-bin\perlscript.ipl
Can't open perl script "d:\iw-home\httpd\iw-bin\perlscript.ipl": No such f
ile or directory

nipper

in DOS do this

dir \iw-home
dir \iw-home\httpd
dir \iw-home\httpd\iw-bin

Migrateduser

If I'm following this correctly, you should need to perform the following.

mklink /D d:\iw-home\iw-perl d:\iw-home\TeamSite\iw-perl
Should now have an iw-perl folder inside d:\iw-home.

mklink /D d:\iw-home\httpd d:\iw-home\TeamSite\httpd
Should now have an httpd folder inside d:\iw-home

Also, to delete the links you just use del d:\abc\xyz. Or delete it from windows explorer.

nipper

While I expect your fix is correct, I wonder what else will need to be changed for her ? There may be other paths that are hardcoded to iw-home

Jenni

in DOS do this

dir \iw-home
dir \iw-home\httpd
dir \iw-home\httpd\iw-bin

I did that. Still the same issue.

Jenni

If I'm following this correctly, you should need to perform the following.

mklink /D d:\iw-home\iw-perl d:\iw-home\TeamSite\iw-perl
Should now have an iw-perl folder inside d:\iw-home.

mklink /D d:\iw-home\httpd d:\iw-home\TeamSite\httpd
Should now have an httpd folder inside d:\iw-home

Also, to delete the links you just use del d:\abc\xyz. Or delete it from windows explorer.

Here is the output of the commands

C:\Users>mklink /D d:\iw-home\iw-perl d:\iw-home\TeamSite\iw-perl
Cannot create a file when that file already exists.

C:\Users>mklink /D d:\iw-home\httpd d:\iw-home\TeamSite\httpd
Cannot create a file when that file already exists.

I did try deleting the *folder* (they are not links).

Jenni

While I expect your fix is correct, I wonder what else will need to be changed for her ? There may be other paths that are hardcoded to iw-home

I believe we can narrow down to the iwperl.exe and anything under httpd/iw-bin.

nipper

OK, I think there is some mis-communications here.

To my reply you said same issue. Run the commands and copy/paste the output

Also, open up windows explorer to

, right click on iw-home and view properties. It should be a folder. Then enter it and right click on the objects in that folder, tell what you get.

There is an issue with the httpd shortcut/link. The one for Perl works as expected, so you just need to compare the two and see what is different.

Jenni

Hi All,

Now I deleted the folders and tried the commands for mklink and it worked fine.

Thanks very much for helping us in resolving the issue.

Migrateduser

Hi All,

Now I deleted the folders and tried the commands for mklink and it worked fine.

Thanks very much for helping us in resolving the issue.

Does that mean your inline scripts are working now?

Jenni

Does that mean your inline scripts are working now?

Yes they did.

Symlink solution is the best solution for the iw-home path change on the 7.2.1 version.

Thanks for the help.