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 DCR through XSLPT

Rit

I am getting an issue while trying to preview the DCR through XSLPT.

Issue : “While previewing the DCR, images are not getting displayed”.

Steps :

- Created a DCR at /default/main/BranchName/WORKAREA/wa_name/templatedata/Product_Content/Specifications/data/.

- The xsl file used to preview the DCR is created at /default/main/BranchName/WORKAREA/wa_name/templatedata/Product_Content/Specifications/presentation/specification.xsl

I want to display an image in the preview option of the DCR. For that, I have added the following line :

[html]

[/html]

The hierarchy of images folder is shown below:
wa_name
- html
- images
- includes
- iw
- sites
- templatedata

When I click on Preview, I am getting the attached HTML Page.

The image is not getting displayed. Cross symbol is coming at the top left corner of the image.I tried to hard code the entire path under
[html]

[/html], still it is behaving in the same way.

As in components, we need to append “$URL_PREFIX”, do I have to append something similar to that, to make the image available through XSLPT?

Please let me know if I am missing something. Thanks in advance.

Find more posts tagged with

Comments

vpatel

What is the image path in the browser? Try "view source" or "image properties" and post it here. Unless you are using SitePublisher, you do NOT need $URL_PREFIX.

Rit

By writing image path (thro source code/image properties) directly in the browser, image is coming properly. The issue is coming when i am previewing it through a DCR.

vpatel

When you preview it through the DCR, do "view source" and find the relevant "img" tag and see what are you getting there.

Jamik

well if you're writing out "/image" as the path then you're always going to get an incorrect image path when previewing in DCR. since "/image" tells the browser to look at the root of the website and then go into the images folder from root most likely it's trying to hit "http://teamsitepreviewserver/iwmount/images/pathtoimage.gif" for the image location. The only way around this i think is either using iwproxy to change the location to proper branch/workarea for preview and/or having a second field to use for previewing images. And you probably should post the image location via properties in the browser as vpatel mentions so we have a better idea.

Adam Stoller

If I'm reading this right - you have a directory named "images" directly within the root of the workarea and you are referencing a file (baby.jpg) that lives directly within that images directory - e.g.: /default/main/.../WORKAREA/wa-name/images/baby.jpg -- is that correct so far?

If so - you should not need a proxy rule for images - though you might already have one in your iw.cfg file that is being used when you don't want it (verify).

Assuming you don't have any proxy rules for /images or for doc_root in your iw.cfg, and that the path information is as I stated above - the next question is whether the img directive is within a VFE or TinyMCE textarea - or being written explicitly by you via the XSLT (e.g.: you have an image field in the DCT with a path in it [/images/baby.jpg] and your XSLT takes that and formats it as an img directive). Which is it?

If it's VFE or TinyMCE - there were reported issues where the code was getting munged and being replaced with something like src="http://servername/images/baby.jpg" - which would probably not work - as other's have suggested - if you right-click on the broken image and select Properties - what do you see?

Rit

Thanks a lot guys for giving your valuable suggestions..

If I'm reading this right - you have a directory named "images" directly within the root of the workarea and you are referencing a file (baby.jpg) that lives directly within that images directory - e.g.: /default/main/.../WORKAREA/wa-name/images/baby.jpg -- is that correct so far?
As usual you are correct Ghoti..

If so - you should not need a proxy rule for images - though you might already have one in your iw.cfg file that is being used when you don't want it (verify). Proxy rule for image is configured in iw.cfg as you told..

Assuming you don't have any proxy rules for /images or for doc_root in your iw.cfg, and that the path information is as I stated above - the next question is whether the img directive is within a VFE or TinyMCE textarea - or being written explicitly by you via the XSLT (e.g.: you have an image field in the DCT with a path in it [/images/baby.jpg] and your XSLT takes that and formats it as an img directive). Which is it? I am doing it with the last option which you told. i.e, I have an image field in the DCT with a path in it [/images/baby.jpg] and my XSLT takes that and formats it as an img directive..

If it's VFE or TinyMCE - there were reported issues where the code was getting munged and being replaced with something like src="http://servername/images/baby.jpg" - which would probably not work - as other's have suggested - if you right-click on the broken image and select Properties - what do you see?
If i right click on the broken image and select properties, i am getting src="http://servername/images/baby.jpg".. .....
Also, when i right click-> view source, i am getting [html][/html]
I am trying with various other suggestions provided by my supervisor.. Will let you guys know if it works..
Thanks,
Ritesh.

Adam Stoller

...
If i right click on the broken image and select properties, i am getting src="http://servername/images/baby.jpg".. .....
Also, when i right click-> view source, i am getting [html][/html]
I am trying with various other suggestions provided by my supervisor.. Will let you guys know if it works..
Thanks,
Ritesh.

The fact that you are missing the leading slash when you view source is probably the problem - and this would lead me to think that there's an error in your XSLT that is somehow dropping (or not adding) the leading slash - but that's just a guess.

Rit

We didn't exactly found the reason for the below mentioned issue. But we found an alternate solution just for the sake of testing.

We have added "generate" option in the templating.cfg for the DCT, through which the xslpt is getting called.
On clicking of Generate, the images are getting displayed properly.

For Preview, we are still trying to find out the reason. In case, we didnt get anything, we might log a ticket in IWOV support.