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

prevent page generation based on DCR value

Hans

I would like to somehow prevent page generation based on a certain DCR values. Any idea how to do this?

One of the ideas I had was to redirect the generation to a different location, i.e. either a file, trash.html, that could be overwritten as needed, or redirect it to /dev/null. So far this is just an idea, I haven't done much research.

If anyone has done this and has a better approach, please let me know.

I am using TS 6.1 sp1 on Solaris 8, if this is relevant.

Thanks!

Find more posts tagged with

Comments

Migrateduser

Sure, this is possible.


<iw_perl>
my $flag = iwpt_dcr_value('dcr.content.generate_page_flag');
if ($flag) {
  --- do stuff ---
} else {
  --- redirect to trash.html ---
}
</iwperl>

Is that clear?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Hans

Thanks Dave,

Well, that's straightforward as far as it goes, but I think I need I need a little more.

I can include a Perl block at the top of the PT, but the part I'm unclear about is how to redirect the default output stream.

Have you done this ?

thanks again,

Hans

Migrateduser

Do you want to prevent generation through the UI or as an automated process? If through the UI, I think you can use FormAPI to check the field and disable the buttons (you probably want an onChange handler on the item that enables/disables the buttons, and also call this handler when the form loads). If you are talking about an automated process, it should probably just parse the DCR to set a flag, then generate or not depending on this flag.

Ottawa_IWOV

So that is just an example of grabbing the value of a field in the DCR, correct?

Lucas Cochrane
lucas.cochrane@baucanada.com

Migrateduser

No, I haven't tried this -- but I got a different idea...

In the DCT, have a onSaveValid event handler which will dictate the output file with IWDCRInfo.setDCRName('value'); setting value to some pre-calculated string, based on whether or not this file will be generated.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Migrateduser

Yes, but that doesn't address where the output stream is directed -- I didn't consider that in my initial response.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Migrateduser

****, that won't prevent regeneration when a user looks at the DCR in read-only mode, since that ignores any FormAPI. So you would want to do both - FormAPI and PT logic.

Hans

I guess I could have included a bit more info... I do need to save the DCR but its location is not important.

I am generating a news index page (among other things) using a Perl script to parse the DCRs. But if the DCR has an alternate_URL field that is populated, the index page will point there, I don't need to generate the html page for that DCR.

Generating pages for these DCRs doesn't cause any harm but it clogs up the htdocs folder with useless files. Slows down the scrolling if the file list gets too long.

thanks again for your input.