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

Where do you capture the temporary file name on preview?

bettineski

System: 6.7.1, Win '03, .NET

I need to write to the sitemap during preview, but I don't know how to capture the temporary file's name (zz_tst_etc_etc_.aspx)

I've searched the forums a bunch looking for an answer, but I haven't come across it.

Where is the place that this happens?

I found this folder
E:\iw-home\httpd\webapps\content_center\formspub\preview

This has the preview.jsp, show_preview.jsp, etc files in it.

I'm guessing these will be related, but I'm not sure where in the process they are called.

Thanks!

Find more posts tagged with

Comments

nipper

Do you mean iwpt_get_ofile_name("basename"); ?

bettineski

Do you mean iwpt_get_ofile_name("basename"); ?

Perhaps it would do it, but I don't know where to interject my code to make my webservice call.

When a user clicks preview, I'm in the dark as to the process that leads up to the temp file being made.

nipper

Are you using PT or XSLT ? The call I provided is a perl call that fits within iwperl tags in a PT

bettineski

Are you using PT or XSLT ? The call I provided is a perl call that fits within iwperl tags in a PT

Whoah.

That did it.

Where would I have learned about this? Is there some documentation on this somewhere?

So, if I put this into the PT and it updates the sitemap, how would I call the sitemap to remove this when the preview is closed?

nipper

http://insert-your-server-here/iw/help/tst/pt/

nipper

So, if I put this into the PT and it updates the sitemap, how would I call the sitemap to remove this when the preview is closed?

That is a design issue and I am not certain why you are doing this in general. What is your use case ?

zz_tst files are temporary, but you may want to regen the sitemap to point to the real page instead of the temp page.

bettineski

That is a design issue and I am not certain why you are doing this in general. What is your use case ?

zz_tst files are temporary, but you may want to regen the sitemap to point to the real page instead of the temp page.

The edict was that we would use a webservice that maintains the sitemap via a database.

Getting this to work for generate is very simple because we don't have to worry about figuring out the random file name, sending it to the webservice so preview works, and then telling the webservice to delete it when preview is closed.

I thought there'd be a way to have a little more control over the preview process, but it's sounding like the only control I have is in the PT?

Is there some way of giving it a sort of "When preview closed" event? This way I can clean up the temporary file name from the sitemap when it's closed?

report2.rptdesign

nipper

The webservice to automatically make the sitemap is of dubious value, how many pages do you have, *all* of them in the sitemap ? I do not see it but I can see some rational behind it.

However preveiwing a file should never be in the sitemap, because that will go away in about 30 seconds.

bettineski

The webservice to automatically make the sitemap is of dubious value, how many pages do you have, *all* of them in the sitemap ? I do not see it but I can see some rational behind it.

However preveiwing a file should never be in the sitemap, because that will go away in about 30 seconds.

We have every page in the sitemap (.NET site).

This functionality is on our dev server, so if we have to put temp. entries into the sitemap, it's not a huge issue.

The issue was the clean up.

Nice Solution: See if there's a way to execute one last command when the preview window is closed. This way the preview enters and removes the entry itself.

Ugly Solution: On preview or generate, we clean up the old entry from the sitemap. This would mean that the temp entry would sit out there until the next time the page was previewed or generated.

Either would work, really, but I really don't like the ugly solution.

But since I don't fully understand how the preview process works, it's the only one I can implement as of now.

nipper

Well, this thread has some code that may help

ISCBorisB

The edict was that we would use a webservice that maintains the sitemap via a database.

Getting this to work for generate is very simple because we don't have to worry about figuring out the random file name, sending it to the webservice so preview works, and then telling the webservice to delete it when preview is closed.

I thought there'd be a way to have a little more control over the preview process, but it's sounding like the only control I have is in the PT?

Is there some way of giving it a sort of "When preview closed" event? This way I can clean up the temporary file name from the sitemap when it's closed?

Would it help if you can transparently redirect HTTP request from the Preview for this particular type -
to whatever you want, generating redirect URL dynamically if needed?

If that helps - I can show you how to do it. Still... I tend to agree with Andy on this one, your Use Case looks
questionable at best. Sure, I know nothing about your rendition Environment and Application so it may be a perfectly
kosher one.

modifiedpages.zip

bettineski

If that helps - it's not all that hard to do, but still... I tend to agree with Andy on this one, your Use Case looks
questionable at best.

I fully agree. The other option was to implement a TS UI driven sitemap solution. We don't have any kind of time to do something like that.

Sure, I know nothing about your rendition Environment and Application so it may be a perfectly kosher one.

I have a solution I can implement now.

And I know a lot more now then I did just a couple hours ago.

Thanks!