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

Custom Preview link

Bunty

Hi all,

I have created a CGI script for an CGI task, which will list DCR's and will allow me to preview the cms html output (using a link), and a link to view live web page.

How can I create a custom preview link on my CGI screen to preview my output file.

I have tried "iw-cc/perviewfile", but insted it allows me to preview DCR.

Is anyone else aware of handling preview using certain other options?

regards
Atul

Find more posts tagged with

Comments

CRB

if i understand your issue, you want to preview the DCRs? if yes, then you can do something like this:
[HTML]
genurl = "http://hostname/iw-cc/urlgenerate?dcr=" + dcrpath + "&pt=" + ptfile + "&output=" + outputfile + "&override=true";
popup(genurl,800,600);
[/HTML]

Adam Stoller

if i understand your issue, you want to preview the DCRs? if yes, then you can do something like this:
[HTML]
genurl = "http://hostname/iw-cc/urlgenerate?dcr=" + dcrpath + "&pt=" + ptfile + "&output=" + outputfile + "&override=true";
popup(genurl,800,600);
[/HTML]

Hmm - interesting URL - just looked it up in the 671SP1 FormsPubliser Developer's Guide. The text is a bit unclear:[indent]A URL command is also provided to generate [color=red](but not preview) display data.[/color][/indent]Does that mean that it will only perform the operations of Generate (DCR + PT > HTML + load HTML into browser window) and not the operations of Preview (DCR + PT > zz_tst_HTML + load zz_tst_HTML into browser window) - or - does it mean that it will do the first part (DCR + PT > HTML) and not do the second part (load HTML into browser window)?

If Bunty has already taken care of generating the output file - then wouldn't a simple

window.location("uri-to-page-in-teamsite");

-- if it's not already generated - then it sounds like you might need both operations.

CRB

Ghoti, you are right!

Sorry i was in hurry when i replied to this post. yes, the URL will generate a file (my_zz_output file). so if he only needs to preview, he will have to manually delete the generated file. he can either do it immediately after the user is done previewing, or as cleanup task after the workflow is done.

Bunty

Hi Gothi,

I am giving a preview option in CGI, and based on this preview URL will approve the DCR for output generation... which is an xml file.

well have configured two tpls both for html and xml. So generation of file will only be done after Approval on CGI screen.

I have tried to form a URL based on the syntax mentioned

---> genurl = "http://hostname/iw-cc/urlgenerate?dcr=" + dcrpath + "&pt=" + ptfile + "&output=" + outputfile + "&override=true"; <--

Now my URL looks something like this.

"http://132.146.16.115/iw-cc/urlgenerate?dcr=//ap21cnedc403/btgsportal/main/supersite/inprocess_db/WORKAREA/content_classes/templatedata/page/product_solutions/data/products/dg_en-gb_4477&pt=//ap21cnedc403/btgsportal/main/supersite/inprocess_db/WORKAREA/content_classes/templatedata/page/product_solutions/presentation/presentation-html.tpl&output=//ap21cnedc403/btgsportal/main/supersite/inprocess_db/WORKAREA/content_classes/test.html&override=true"

I tried to hit this URL in browser.... but got an error saying...

"The current PT Compiler is not supported through URL. Please check this configuration in templating.cfg."

Am I doing correct thing here?

Adam Stoller

Hi Bunny,

You should learn to read the manuals - there's a note there on page 75 of the FP Dev Guide that says:[indent]NOTE
URL command access is supported only for XSLT presentation templates. It is not
supported for Perl presentation templates. [/indent]My solution would have the CGI run iwpt_compile.ipl (or iwgen) to generate the HTML file and then do a open a new window with the newly generated file for previewing. Once approved, I'd do another iwpt_compile.ipl (or iwgen) to generate the XML file and probably delete the HTML file - before transitioning the workflow.

Bunty

exactly,

I have started working on same lines.......

Thank you Gothi Smiley Happy