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

Preview popup after 'generate'

RonaldV

Hi,

if one clicks the 'generate' button in a dcr-edit-window it generates the outputfile (good) but as a bonus it shows the generated file in a popup preview-window (not good)

Is it possible to stop this preview-popup and only perform the generate-action?

Find more posts tagged with

Comments

Bhargav Coca

Hi,

if one clicks the 'generate' button in a dcr-edit-window it generates the outputfile (good) but as a bonus it shows the generated file in a popup preview-window (not good)

Is it possible to stop this preview-popup and only perform the generate-action?

No and a Yes, From OOTB functionality not possible. I mean in General from USer point of view that Preview is necessary, else how will one know if the file really got generated with out going to the folder in which it got generated. Also that Preview window helps in a lot many ways to debug any syntactical, functional or value errors. I wonder why one wants to get away from that.

If at all you need such a functionality, one has to customize your DCR links and put in custom links for generate.

Thanks

RonaldV

I don't think one can customise the buttons in the top of the dcr window.

Adam Stoller

I don't think one can customise the buttons in the top of the dcr window.

It's been a while since I've tried to do anything like this, but I seem to recall that, with FormAPI, it was possible to capture the Preview and/or Generate events (caused by the buttons in the top) and then do whatever you wanted. I think that if the handler function returns

true

it will continue on and call the OOTB functionality (which would include the pop-up), but that you could also return

false

to prevent that - though you then have to take care of performing all the page generation stuff yourself.

I think the last time I did anything like this was pre-6.5 - so I could be mis-remembering...

Migrateduser

Building up on Ghoti's comments. Here's a basic example.

[PHP]
<script>

function saveHandler(button) {
switch (button) {
case IWDatacapture.GENERATE_BUTTON:
alert('here');
break;
default:
return true;
}
}

init();

function init()
{
IWEventRegistry.addFormHandler("onSave", saveHandler);
}

init();

function init()
{
IWEventRegistry.addFormHandler("onSave", saveHandler);
}

</script>
[/PHP]

For more info, see page 21 of the 6.5 FormAPI Developer’s Guide.

Rick Poulin

taalgaard's solution will fail if you hit generate on a form that's not dirty (hasn't changed since the last save), because the onSave event won't (may not?) get triggered. Lucky for you, the 'onGenerate' form-level event exists in your TS version (p.67 in 7.1 guide)

ISCBorisB

taalgaard's solution will fail if you hit generate on a form that's not dirty (hasn't changed since the last save), because the onSave event won't (may not?) get triggered. Lucky for you, the 'onGenerate' form-level event exists in your TS version (p.67 in 7.1 guide)

Any flavor of FormAPI processing will be ignored if you generate in "View" Mode

Migrateduser

taalgaard's solution will fail if you hit generate on a form that's not dirty (hasn't changed since the last save), because the onSave event won't (may not?) get triggered. Lucky for you, the 'onGenerate' form-level event exists in your TS version (p.67 in 7.1 guide)

Lets forget FormAPI altogether and instead add the following to your tpl file.

[PHP]
<script>
window.open('', '_self');
window.close();
</script>

[/PHP]

You will get a quick window that pops up, but it will close automatically for the user.

RonaldV

Lets forget FormAPI altogether and instead add the following to your tpl file.

[PHP]
<script>
window.open('', '_self');
window.close();
</script>

[/PHP]

You will get a quick window that pops up, but it will close automatically for the user.

Yeah, nice one. This will make my browser close once a visitor will visit my public website. That's is a nice way to scare them off, poor web-visitors. Who needs them anyway? :-)

RonaldV

Using the OnGenerate is a nice option but:

1. it fails for dcr's in preview (as mentioned above)
2. one has to be careful because I found that onGenerate is fired twice: once before the save and once after the save so your function will have to check IWDatacapture.isModified () etc, etc. BTW: the manual (7.1) is completely ignorant and wrong on this event. Who needs a manual anyway these days? :-(

What I will implement is slighty illegal but smooth nevertheless: I modified the iw-cc.war/....../formspub/generate/generate.jsp and changed the form.target from _blank to 'gibberish' (delete the matching files under default/work to force a re-compile). This will open only 1 generate-output-window in stead of the default unlimited. (And yes, I know that any ts-update can ruin my solution!)

Migrateduser

Yeah, nice one. This will make my browser close once a visitor will visit my public website. That's is a nice way to scare them off, poor web-visitors. Who needs them anyway? :-)

That all depends on how you are using your tpl. In my case, I just use it to make database calls and don't actually use it to generate a page. If you're using it to generate a page, then, no, it won't work. But.....since the original poster never mentioned what his tpl does, then my example could help him. Just giving the dude some simple solutions.

ISCBorisB

What I will implement is slighty illegal...

In the past I've used two *legal* techniques when I wanted to suppress automatic Preview.

1. Use Proxy. If you can find representative regex, redirect to one of OTB refresh_and_close.html, close_window.html
or simply your own self-closing HTML.

2. Within presentation template, generate required components where you need them and render only
"stub" Page to standard output who's only purpose in life is to self-close. I also used this stub page to
provide additional (server side) processing diagnostics, error messages and the like.