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 virtualising preview

sara

Hi,
I have problems previewing the data in a DCR.
Frames show 'page not found', images and stylesheets don't display.

I have found only one relevant thread in devnet.
and I tried some things out.

preview-dir
I defined the same directory as where the result is generated, to have the same regexes applied on both versions. The generated result displays fine, but the preview of the DCR shows 'page not found'.

templatedata/iw_preview
I tested out some regexes that take into account these templatedata directories, but I have no result. Is this still the case in TS 5.5.2, or only before TS 5.0.1?

I wanted to understand what the proxy was looking for with iwproxy in debug mode. But when I preview from the DCR, there is no debugging output produced. (there is when virtualising the generated result)

Could someone explain what is happening, or pass me some locations where I can find relevant information?

Thx,
Sara

Find more posts tagged with

Comments

sara

Can anyone give me a hint?

nipper

First question is are the generated pages working fine ? for other files, are you using relative paths or absolute. If relative, are the files available with the preivew directory path ?

If those all look good, then you may need to play with the proxy. Kill iwproxy and run with the debug turned on. It iwll give you lots of info.

HTH

Andy

sara

- Generated pages work fine
- In my testing I have worked with absolute links to another server, absolute links to the root of the workarea and with relative links to the file.
- What do you mean with 'are the files available with the preivew directory path'? Do the files have to be in the directory or subdirectory of the preview directory path? Does this make a change. But my preview directory path points to the directory where the results are generated, so there should not be a problem.
- I have tried out the proxy in debug mode, but it does not give any output when previewing a dcr.

s.

nipper

WHen you generate /place/here/foo.html and you use a relative path (../../images/foo.jpg)

then you can have trouble with preview finding those images IF you preview in the root (or anywhere else than 2 levels deep, /preview/here/zz_foo.html)

Are the thngs broken using relative paths ? Check where your preview dir is (defined in templating.cfg) and make certain that the relative paths are reachable from that path. If you have a path like: ./images/foo.jpg then you may need to be creative.

ANdy

sara

I still didn't resolve the problem.

- the absolute paths virtualize fine
- the other paths are all relative to the root of the workarea: /images/image.gif

As I said before I preview in the directory where the results are generated, so the same proxy settings should apply. The generated page virtualises fine, the preview does not.
I even changed the name of the zz_ts_... via the UNIX file interface to let the temporary file used by the preview becomes available in TeamSite. When virtualised from TeamSite this virtualises fine.

Why doesn't it work when previewing?

Adam Stoller

check your iwproxy settings in your iw.cfg file.
you might need to run iwproxy in debug mode (see docs and/or search DevNet for further info) in order to fully diagnose what is (or isn't) happening.

--fish
(Interwoven Senior Technical Consultant)

sara

is there a difference in the regexes for preview? because the generated files, and the modified zz-tst-... file virtualize fine.

I tried that before, but when previewing a dcr, the proxy in debugmode does not output anything (which he does when previewing the result)

Adam Stoller

If you had upgraded from an earlier release of TeamSite (don't recall which version this changed in right now) - there used to be proxy settings explcitly for preview. If you had maintained those proxy settings in the iw.cfg file after the upgrade, preview wouldn't work correctly. Unless you're doing something particularly customized with regard to preview - you should not need any proxy settings for Preview anymore.

I find it difficult to believe that running proxy in debug mode (iwproxy -d, after having killed off existing iwproxy processes) resulted in no output when previewing files in TeamSite.

--fish
(Interwoven Senior Technical Consultant)

sara

this time there was some output when previewing a dcr, I must have done something wrong last time.

I noticed that the proxy is looking for a file
comnav/menunl/zz_tst_g61160_2_fixnav2.htm in stead of a file
comnav/menunl/fixnav2.htm
which wll not be found. how come?
the output of the debug is in the attachment (the output when previewing the dcr is separated from virtualising the result with multiple

For information
a part of my templating.cfg
<category name="inet">
<locations>
<branch vpath-regex=".*"/>
</locations>
<data-type name="menu" dcr-type="iwov">
<presentation>
<template name="preview.tpl" extension="html">
<locations>
<branch vpath-regex=".*" preview-dir="/"
>
<directory dir-regex=".*" />
</branch>
</locations>
</template>
</presentation>
</data-type>

a part of iw.cfg
[teamsite_templating]
# use_java_ui=false
# data_root=templatedata
pretty_print_dcrs=true
enable_formapi=true
preview_history_limit=5

Adam Stoller

The zz_* prefix is used by templating for transient preview-generated files - and by default, all files that are generated during preview receive this prefix string so that the preview will work.

Is the file fixnav2.htm generated when you click Generate? (as opposed to Preview)?
Are you sure the file zz_..._fixnav2.htm is not getting generated when you click Preview? If not in the directory listed - is it perhaps in the workarea root?
Do you have any iwproxy_preconnect_remap settings in your iw.cfg?
Could you post them?

--fish
(Interwoven Senior Technical Consultant)

sara

the fixnav2.htm should not be generated, only used.
neither is a zz-...-fixnav generated at Preview(I checked the root, and its directory)

I will post the other regexes in iw.cfg
_regex=^.*/(default/main/FXIN-BR/IZLI-BR/WORKAREA/.*/[Ss][Cc][Rr][Ii][Pp][Tt]/.*)=http://i-net907-de
v.be.fortis.bank/$1
_regex=^.*/(default/main/FXIN-BR/IZLI-BR/WORKAREA/.*/[Cc][Ss][Ss]/.*)=http://i-net907-dev.be.fortis.
bank/$1
_regex=^.*/(default/main/FXIN-BR/IZLI-BR/WORKAREA/.*/[Ii][mM][Aa][Gg][Ee][Ss]/.*)=http://i-net907-de
v.be.fortis.bank/$1
_regex=^.*/(default/main/FXIN-BR/IZLI-BR/WORKAREA/.*/[Cc][Oo][Mm][Nn][Aa][Vv]/.*)=http://i-net907-de
v.be.fortis.bank/$1

_regex=^.*/(default/main/FXIN-BR/IZLI-BR/WORKAREA/.*)$=http://i-net907-dev.be.fortis.bank/$1