We are in the process of implementing Arbortext 6.0 with DITA (upgrading from previous version of Arbortext and non-DITA DTDs). We want to use a central image web server to manage our image files and reference them in the DITA topics using URLs (e.g., http://myserver.com/digitalasset/cnt070794.jpg). To do this we tried setting an image element to have href="http://myserver.com/digitalasset/cnt070794.jpg" and scope="external" but this is causing an error during the completeness check:
ERROR: Dita reference "http://myserver.com/digitalasset/cnt070794.jpg"
on image element in "Document1" does not refer to a dita/ditabase document.
This error doesn't happen if I insert the same image URL in a non-DITA document in Arbortext 6.0, so I'm assuming it's part of the enhanced DITA completeness check.
Does anyone know how to get this error to go away? Is there another attribute that we need to set besides scope?
It seems to work on my side even without setting the "scope" attribute - check the attached video.
Do you take same steps as me when trying? What 6.0 build are you using?
Thank you for responding, Dmitry. I was not able to access your video. I get "The item does not exist. It may have been deleted."
I just upgraded to Version 6.0 M030, Build R60M030-349, but this did not solve the problem. Which build are you using?
Here's an example of how I set the image element to use a URL with the scope attribute:
Here are the completeness check errors:
The reason I set the scope attribute was to get rid of a different warning about the local referencing appearing to be an external/peer reference. Setting the scope attribute made that warning go away, but then it gives an error saying the external/peer referencing doesn't exist (the second error in the example above). I'm not too worried about that because that error doesn't appear when I use a URL from a server inside the firewall. It's an odd error, though. Obviously the image exists because it's displayed in the image element in the Edit view.
Anyway, if you have any thoughts, please let me know.
Jessica, the video is now available - please, check it. It was captured on 6.0 M030. Are you still getting the error when following the same steps?
Thanks, I can see the video now. I still get the error when I follow the same steps. The only difference I notice is that it looks like you are using a URL from a Windchill server. It shouldn't make a difference, but we are not using Windchill.
Jessica, can you send the .dita file to me so I would check if the behavior is reproducible on my installation.
If I'll be able to reproduce, then, most likely, the cause is within the file (different attributes/attributes' values and/or tag structure etc).
If not, then the behaviour is installation/environment-related.
Also, have you opened a TS call?
I uploaded the file here: http://communities.ptc.com/servlet/JiveServlet/downloadBody/2479-102-1-2818/Document1.dita.zip
(Not sure if that's the correct way to send a file, so if it doesn't work, let me know.)
I did submit a support ticket on Monday. I haven't received any help from them yet.
This particular URL doesn't work for me either (http://www.oracleimg.com/us/assets/oralogo-small.gif). I did more tests and other random URLs work here - see the attached samples. I suppose, there would be more "non-working" URLs. Not sure what's the difference - this particular doesn't look any special to me.
Thank you for testing this. I tried some of the URLs in your sample and I still got completeness errors. I passed this information on to our developer and he asked if you could post your sample dita file containing the URLs that work for you. I was also wondering what your graphics path is set to in your preferences.
See the attached files, Jessica
That's really strange behaviour (or we're just missing something obvious! )
Have you got any feedback from Tech Support yet?
Here are the .dita file and the screenshot with my "graphicspath"
Thanks Dmitry. This is helpful.
I get the completeness error on all of the images in the file that you posted, so maybe there is a problem with our setup or preferences. Our developer is looking into it.
I haven't heard back from Tech Support yet. Maybe they are waiting to see if we solve the issue here .
Anyway, I appreciate all of your help. If we find a solution, I'll post it here.