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

DCR preview issues on 5.52

Drew_The_Goat

We are having DCR preview issues after having upgraded a server to TS 5.52. The PT code and component template execute fine when we click on generate, but when we try to use preview the component template fails. We use a component template to apply metadata to the output file using iwexattr, and it is failing at this point. The temp preview file never even gets generated.

This code has worked fine for over a year on our TS 5.01 enviroments..

Thanks in advance.
Drew

Find more posts tagged with

Comments

LooseCannon

What, if any, is the error message when previewing. Are your generated an previewed files written to the same location? If not check that you have write permissions to the dir you're writing the previewed files to (defaults to WORKAREA root).

Drew_The_Goat

Hi,

Thanks, we have checked the permissions on the preview directory and they are fine. We even changed them to 777 to be safe. The temp preview files are set to be written at WORKAREA root currently, but they never get generated. Only the temp file _manifest gets written. The point the component fails is at the iwexattr command, as it is writing the attributes to the file (we pass dcr nodes as perl variables to be applied as attributes to the file).

LooseCannon

Can you successfully preview a DCR w/a simple or out-of-box .tpl?

Drew_The_Goat

Yes absolutely. All of our other tpls work fine. It is only with the tpls that call the component that uses the iwextattr command. We have also hardcoded it into the PT and determined its not related to the iw_include command.

Adam Stoller

What is your PT calling iwextattr on? Perhaps the problem is that the code for generating the extended attributes doesn't work when you're doing a preview and that you need to conditionalize the code so that it only runs when you're doing an actual page generation.

--fish
(Interwoven Senior Technical Consultant)

Drew_The_Goat

For preview purposes, using the iwextattr command is not neccessary, but I did not know that it was possible to dynamically call the PT code based on the preview or generate command. Is there a perl function I can call that will return a "Preview" or "Generate" status? If so, then I could use that approach to ignore the iwextattr command for preview.

Thanks,
Drew

Gregg Faus

You could use this function:

#####################################################################
# Sets a global variabled 'preview' that determines if a tpl is being 
# used in a preview mode
######################################################################

sub set_preview_status {

 # Get the command line arguments automatically passed to the presentation template
 foreach $arg (@ARGV) {    
  if($arg =~ /zz_tst_(.*)/i) {
   return 1;
  }
 }

 return 0;
}

You could then set a variable for it's return value:

# Determine whether template is used in preview mode
$preview = set_preview_status();

And then use an if statement for your conditional logic:

if ($preview !=1) {
// Execute code that is not in preview mode
}
else {
// Execute code that is being previewed
}

Hope that helps.

- gf

cutomactions.doc

Metadata_of_Document.doc

Drew_The_Goat

hey thanks gf, this code makes perfect sense...I haven't tested it yet but it looks like this approach would work fine...

thanks again!
Drew

wailing

Alternatively:


       # Are we in Preview mode or Generate mode?
       my $is_preview = TeamSite:T::iw_xml::get_flag_param($iw_parser,'-iw_pt-preview');

       if ( defined($is_preview) )
       {
            # Preview mode code
       }
       else
       {
            # Generate mode code
       }

Why don't you play around with the iwpt_compile.ipl script and its options?
It's a fantastic debugger for PTs, and you can feed it any DCRs you want to test out your scenarios.

rgds,
Rika