Not able to read images from SharePoint Picture Library while exporting HTML to Word using Aspose.Words.Document

Aspose.Words Product Family
1

We are facing one issue while exporting HTML to Word using Aspose.Words.Document library. Our images are stored in SharePoint picture library and HTML page is using tag and the src property points to the SharePoint picture library containing images.
After converting this HTML to Word the images are not appearing in document. But if we use some other URL for images then we are successfully able to generate word document with images. Kindly share your thoughts as this is a kind of show stopper for us.
It seems that we need to provide some credentials but there is no way to provide them within the API.
Please let us know if there is a workaround.
Thanks

2

Hi
Thanks for your inquiry. There is no way to set network credentials of Document. This is known issue #1339 in your defect database. I think you can parse your HTML, create locale copies of each image in the HTML document and use local path instead URI.
Best regards.

3

That is a valid approach that we can look into. However before we jump into parsing HTML to get local copies of images, can you provide an update on the following points:

  1. It seems that there is a NetworkCredential class within Aspose.PDF. This class allows setting custom credentials (username and password). I dont see this class in Aspose.Words API. Will this functionality be added to Aspose.Words? If yes, by when?

  2. What credentials is the API using when accessing URLs? If we know the specific set of credentials than we can allow access to that particular user instead of opening up anonymous access.

Regards

4

Hi
Thanks for your request.

  1. Exactly this means issue #1339 that we should add possibility to specify users’ credentials.
  2. Aspose.Words uses anonymous user credentials (\IUSR_).
    Best regards.
5

Thanks for the response.

When can we expect a resolution on issue # 1339?
Based on when the solution will be delivered, we can decide on our workaround approach.

6

Hi
Thanks for your request. Unfortunately I can’t provide you any estimate regarding this issue at the moment.
Best regards.

7

The issues you have found earlier (filed as WORDSNET-927) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(8)

8

The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan