I have a document created with Document Builder which I have attached. The table of contents seems to be getting generated with the wrong page numbers. When I update with Aspose using document.UpdateFields, the numbering remains incorrect. Updating with Word, the numbers correctly realign themselves to match the actual page numbers.
I used this code with the source document and can reproduce without issue:
namespace AsposeTocSample
{
static class Program
{
static void Main()
{
new License().SetLicense("Aspose.Words.Lic");
var doc = new Document("Bug Testing.docx");
doc.UpdateFields();
doc.Save("Bug Testing Updated (Aspose).docx", new OoxmlSaveOptions { Compliance = OoxmlCompliance.Iso29500_2008_Transitional, SaveFormat = SaveFormat.Docx });
}
}
}
Can you help me to understand why the Aspose DocumentBuilder doesn’t correctly update pages?
While using the latest version of Aspose.Words i.e. 13.8.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-8991. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.
Hi Awais,
i know this post is already some month old. But i’m using Aspose Words 13.12.0.0 and facing the same issue described here. Was this bug fixed already?
I guess accessing the Issue Tracking System is not possible right?
I could upload an Example to reproduce my situation if needed.
Best Regards
Robert
Regarding WORDSNET-8991, our development team has completed the analysis of this issue and the root cause has been identified. However, the implementation of the fix of this issue has been postponed till a later date. We will post a notification in this thread as soon as this issue is resolved. We apologize for any inconvenience.
Unfortunately, there is no direct way you can track issues by yourself. But, you are welcome to ask your issue status via forum threads. We will verify the. status from our internal issue tracking system and reply you back.
Sure, please attach your input/output documents you’re getting problems with here for testing. Also, please share the source code to reproduce your issue on our end. We will investigate the issue and provide you more information.
It’s been a few months since the last update. Has there been any progress on this?
We logged two bugs 7 months ago and it’s a shame that we’ve been paying such a large sum of money to get an unacceptable level of support. The bugs were logged under the account Nikkoli.
Thanks for your inquiry. Unfortunately, WORDSNET-8991 is not resolved yet. Keeping in view the complexity of this issue, the implementation of the fix to this issue has been postponed till a later date. We have asked the ETA of this issue from our development team and will update you as soon as it is available. We apologize for your inconvenience.
Thanks for your inquiry. Unfortunately, this issue is not resolved yet. The issue actually depends on the resolution of an internal extremely complex issue (WORDSNET-832). If everything goes by plan, we are very hopeful to implement WORDSNET-832 in Aspose.Words 14.8.0 - Aug 2014 release. Therefore, WORDSNET-8991 is postponed until at least 14.8.0, our development team will review it after the first iteration of WORDSNET-832 is ready. We apologize for your inconvenience.
We cancelled our subscription because of the lack of resolution and won’t be resubscribing until this is resolved. It’s been 20 months since we reported it and I’m tired of having to use Word Interop in order to get a proper table of contents.
Thanks for your inquiry. Unfortunately, at the moment we cannot provide you any reliable estimate and this issue is not likely to be fixed in the near future because the parent issue is WORDSNET-832 is not resolved yet. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.
When will this issue be worked? I’ve had to use Word Automation for the last two years because of it. I heard January 2014, then August 2014, and nothing since.
I’d love to renew my subscription to get this fix but I refuse to update until this and my other two year old bug (495919) are fixed.
Thanks for your inquiry. It is unfortunate that the underlying issue WORDSNET-832 is still unresolved. Our product team is actively working on this issue however because the issue is very complex, we won’t be able to commit an ETA at this time. We apologize for your inconvenience.