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; } } }

6.5 to 6.7.1 upgrade (generation error)

chitresh

Hi All,

We have upgraded our TS from 6.5 SP3 to 6.7.1.0 on Win 2000 Platform. Now we are facing this weird error of regex not working properly.

my $path = $outPage;
print $fhandle1 "\n\n pathbefore $path \n\n";

$path =~ s#.*\$htdocs\\.*\$.*\.xml$#$1#;

print $fhandle1 "\n\npathbetn $path \n\n";

$path =~ s#\\#\/#g;
print $fhandle1 "\n\npathafter $path \n\n";

In the above code the outPage path is in the following format

Y:\default\main\bt_global\intranet\main\content\global\products\root\WORKAREA\maintenance\htdocs\9731_test2\xyz

after applying the regex we get htdocs\9731_test2\

This only works ifor the new form generation . But when we try to regenrate the DCR the regex is not working. Alothough the 2nd regex
($path =~ s#\\#\/#g; ) works fine for new form and the old DCR too. We are not able to figure out why is this happening.Can anyone please help.

Find more posts tagged with

Comments

Adam Stoller

Hi All,

We have upgraded our TS from 6.5 SP3 to 6.7.1.0 on Win 2000 Platform. Now we are facing this weird error of regex not working properly.

my $path = $outPage;
print $fhandle1 "\n\n pathbefore $path \n\n";

$path =~ s#.*\$htdocs\\.*\$.*\.xml$#$1#;

print $fhandle1 "\n\npathbetn $path \n\n";

$path =~ s#\\#\/#g;
print $fhandle1 "\n\npathafter $path \n\n";

In the above code the outPage path is in the following format

Y:\default\main\bt_global\intranet\main\content\global\products\root\WORKAREA\maintenance\htdocs\9731_test2\xyz

after applying the regex we get htdocs\9731_test2\

This only works ifor the new form generation . But when we try to regenrate the DCR the regex is not working. Alothough the 2nd regex
($path =~ s#\\#\/#g; ) works fine for new form and the old DCR too. We are not able to figure out why is this happening.Can anyone please help.

I'd suggest making your life easier and switch to forward slashes earlier rather than later - e.g.:

(my $path = $outPage) =~ tr|\\|/|;
print $fhandle1 "\n\n pathbefore $path \n\n";
$path =~ s|^.*/(htdocs/.*/).*\.xml$|$1|;
print $fhandle1 "\n\npathafter $path \n\n";

This should produce something like (minus extra newlines):

pathbefore Y:/default/main/bt_global/intranet/main/content/global/products/root/WORKAREA/maintenance/htdocs/9731_test2/xyz
pathafter Y:/default/main/bt_global/intranet/main/content/global/products/root/WORKAREA/maintenance/htdocs/9731_test2/xyz

But wait (you say) - that's not what you wanted - well, that's because the path you showed does not end in ".xml" which your regex is expecting - so you need to figure out why you're not getting a full file path and/or if you are getting a full file path why
it doesn't show a .xml extension, and/or fix your regex to accomodate that - most simply by changing the regex to something like:

$path =~ s|^.*/(htdocs/.*/).*$|$1|;

Migrateduser

$path =~ s|^.*/(htdocs/.*/).*$|$1|;

As was posted earlier, though I would make the captured .* in the regex above a non-greedy match.

$path =~ s|^.*/(htdocs/.*?/).*$|$1|;

This will insure you only get the directory immediately following the "htdocs" rather than all directories below it, unless of course, that is what you are trying to do.

Adam Stoller

$path =~ s|^.*/(htdocs/.*/).*$|$1|;
As was posted earlier, though I would make the captured .* in the regex above a non-greedy match.
$path =~ s|^.*/(htdocs/.*?/).*$|$1|;
This will insure you only get the directory immediately following the "htdocs" rather than all directories below it, unless of course, that is what you are trying to do.

I would assume the latter - that the intent is to get the complete relative path to the file, but not the file itself.

ScatterChart.PNG

chitresh

Thanks for your support guys.
What i have found is that there is no .xml extension (rightly pointed out by ghoti). Now this .xml is not coming in tha path only when i generate the old DCR. With the new DCR it has .xml attached to it. So even if i try fixing the regex i get 2 DCR's generated in the same area (i.e for eg the original DCR has work.xml and after editing & generating it become work).Now i am trying to figure out why .xml is not getting appended in the path.

hyperlink.rptdesign

Adam Stoller

Thanks for your support guys.
What i have found is that there is no .xml extension (rightly pointed out by ghoti). Now this .xml is not coming in tha path only when i generate the old DCR. With the new DCR it has .xml attached to it. So even if i try fixing the regex i get 2 DCR's generated in the same area (i.e for eg the original DCR has work.xml and after editing & generating it become work).Now i am trying to figure out why .xml is not getting appended in the path.

That's probably either user-error or FormAPI-coding error (if you're talking about a DCR being saved from an Edit DCR session), or an output argument error being provided to a PT (if you're talking about an XML file being generated from a DCR) - depending on who is responsible for actually providing the name of the file.