Hello Imran,
Any info on the progress of the issues SAASWORDS-69 and SAASWORDS-80? We would like to test the system by converting the to those issues related documents.
Hello Imran,
Any info on the progress of the issues SAASWORDS-69 and SAASWORDS-80? We would like to test the system by converting the to those issues related documents.
Hi Richard,
Thank you for your inquiry. I'm sorry to share with you that these issues are not yet resolved. These issues are pending for analysis. We have asked the responsible developer to take a look at your issue shortly. We will keep you informed and let you know once it is fixed and available for public use.
Regards,
Imran Rafique
Support Developer, Saaspose
Support Team
http://www.saaspose.com
Great news! We have been debugging the most important issue we were facing, namely that there appear extra pages in the .pdf after the conversion from .docx. We managed to made our issue reproducible, so in fact this means we located the issue. The file in the attachment can be used to reproduce the conversion bug.
The bug has something to do with headings in combination with page-breaks. We think that if a page ends with a page-break, it still is possible to add empty heading formatting after that page-break on the same page. Converting results into an entirely empty page, since the conversion process thinks this “page-break / header”-combination do has some content. By clicking the pilcrow-icon in Word, the “show all” mode activates, which clarifies the location of the header in relation to the page-break.
We hope you guys are able to fix this problem, since a correct page-count and amount of pages is crucial to our business 
Hi Imran,
We again had a customer which wasn’t able to complete the order process. The conversion .docx > .pdf again created a fatal error, resulting in no document. Please take a look at the document in the attachments in order to reproduce the error. We already tried to upload the document without the first page and the attachments, but still the error occured. In other words, the error occurs in the middle part of the document.
As you can imagine, we are quite suprised about the fact that Saaspose generates so many fatal errors. We are willing to help with the debugging, but please keep us informed about the debugging progress.
From my colleague I’ve heard that the problems were solved and the fix was available live. Up till now I’m still able to reproduce the bug, so is the fix already live yet?
Hi Richard,
Hello, I managed to logon the Aspose community.
The forum is terribly slow, sometimes when I’m lucky it reacts within 4 seconds but very often the pageload is > 30 sec
The documents I posted over here on Zendesk are supposed to be confidential, but does the import in the Aspose forum mean that they are visible for all other users?
How can I know that a reaction has been posted to my issues? There is no separate cloud category, do I get emails when someone reacted?
richard@scribbr.nl:
1. The forum is terribly slow, sometimes when I'm lucky it reacts within 4 seconds but very often the pageload is > 30 sec
richard@scribbr.nl:
2. The documents I posted over here on Zendesk are supposed to be confidential, but does the import in the Aspose forum mean that they are visible for all other users?
richard@scribbr.nl:
3. How can I know that a reaction has been posted to my issues? There is no separate cloud category, do I get emails when someone reacted?
Hi Imran,
Hi Richard,
Thanks for your inquiry.
Currently, we are in the process of integrating the latest codebase with the live Aspose for Cloud (a.k.a Saaspose) service. I have asked the responsible developer to take quick action. All the issues have been resolved either completely or partially. Please see the current issues and comments in the following table:
| ID | Issue ID | Comment |
|---|---|---|
| 1 | SAASWORDS-66 | Resolved in the latest code base. |
| 2 | SAASWORDS-75 | Resolved in the latest code base. |
| 3 | SAASWORDS-69 | The exception is fixed, however, there is still a problem with rendering the Pie chart on the 29th page. It relates to DML Charts rendering, which is a recent feature. We are actively adding new functionality to chart rendering over the last few releases. But chart rendering has many features to support. |
| 4 | SAASWORDS-79 | Resolved in the latest code base. |
| 5 | SAASWORDS-80 | The exception is fixed, however, there is another problem with data table rendering. It also relates to DML Charts. |
richard@scribbr.nl:
I will try to manage the “terrible” pageload and will inform you guys if it occurs again.
Sure, we are looking forward to fixing such problems. Please let me know in case of further assistance or questions.
@Richard - I noticed your comments on our Facebook page about your issues still being present. I’ve asked Support to prioritize things to ensure we get you a solid response ASAP.
Hi Billy,
Hi guys, that it is not integrated in the cloud service yet declares a lot
Hi Richard,
Hi Richard,
Thank you for your patience.
We have good news for you — all the reported issues have been resolved and integrated with our live cloud service. You can now use Aspose.Words for Cloud API.
Please see the current statuses and comments in the following table:
| # | Issue ID | Comment |
|---|---|---|
| 1 | SAASWORDS-66 | Integrated with cloud service. |
| 2 | SAASWORDS-75 | Integrated with cloud service. |
| 3 | SAASWORDS-69 | The exception is fixed and integrated with cloud service. However, there is still a problem with rendering the Pie chart as I shared earlier. We already have logged an issue to fix this problem in our code base as WORDSNET-7245. |
| 4 | SAASWORDS-79 | Integrated with cloud service. |
| 5 | SAASWORDS-80 | The exception is fixed and integrated with cloud service. However, there is another problem with data table rendering. It also relates to DML Charts. We already have logged an issue to fix this problem in our code base as WORDSNET-6943. |
This thread has also been linked to WORDSNET-7245 and WORDSNET-6943. You will be notified as soon as these issues are resolved and available for public use.
The issues you have found earlier (filed as WORDSNET-7245) have been fixed in this .NET update and this Java update.
Uploading the file “33324+error.docx” (see previous page of this post) succesfully completes the conversion
for your inquiry. I have tested the scenario and have not found any issue while converting Docx to Pdf at my end. Could you please try again to convert your
document to Pdf?