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

problem with preview

garima

we had a requirement to generate multiple html files from a single DCT.We used iw_ostream to generate these htmls.
Now since multiple files are getting geenarated, preview is giving an error.
Is there any way to customize preview or anything else
so that the user gets the option to preview any one file from the list of generated files

Find more posts tagged with

Comments

ISCBorisB

we had a requirement to generate multiple html files from a single DCT.We used iw_ostream to generate these htmls.
Now since multiple files are getting geenarated, preview is giving an error.
Is there any way to customize preview or anything else
so that the user gets the option to preview any one file from the list of generated files

1. Your preview error is not directly caused by the number of generated Files, iw-ostreams etc... In other words, that's your bug,
not system's. Perhaps we can help if you provide details.

2. There are many possible scenarios to achieve what you want. For example, Generate all "real" pages with ostream if that's
your preference and output "fluff" page from your PT with links like "view Page A", "view Page B", etc. Do not forget to assign
proper Extended Attributes to "real" Pages.

The disadvantage of this approach is that there is no real difference between "preview" and "generate". Also, you would have to attach
generated files yourself if that generation is a part of a Workflow. Please note that from your post it looks like that's already your case anyway.
If this scenario works for you you may even want to suppress "generate" button and leave only "preview" - fluff's path/name is irrelevant.

garima

in the documentation of iw_ostream tag it is given

Advanced Users:

If this tag generates additional output files, and the
template is being "previewed" (see -iw_pt-preview in
the FLAGS documentation of TeamSite: Smiley Tongue

T::iw_pt), then
the tag will exit with an error message.

This is to prevent clobbering "generated" output and to
avoid leaving auxilary "preview files" hanging around.

ISCBorisB

in the documentation of iw_ostream tag it is given

Advanced Users:

If this tag generates additional output files, and the
template is being "previewed" (see -iw_pt-preview in
the FLAGS documentation of TeamSite:T::iw_pt), then
the tag will exit with an error message.

This is to prevent clobbering "generated" output and to
avoid leaving auxilary "preview files" hanging around.

You may want to consider "buffer" attribute usage instead of "file/file-val".
IMHO if you have enough in-house expertise it is better to write entire PTs within single <iw-perl> tag.
This way peculiarities of PT Tags suddenly (and gratifyingly) become somebody else problem.