Issue with Footer References in Aspose.Words when converting a docStream of a Document Created from OpenXML.WordProcessor

Issue Description: I have two documents in DOCX format: one representing the state of the document before processing with Aspose (referred to as beforeAspose) and one after processing with Aspose (referred to as afterAspose). Both documents are also provided in ZIP format for your reference.

Problem Details:

  • BeforeAspose Document: The footer references in this document are correctly set for each section. Specifically, the footers are as follows:
    • Section 1: Footer1, Footer2
    • Section 2: Footer3
    • Section 3: Footer4
    • Section 4: Footer5
    • And so on…
  • AfterAspose Document: After processing with Aspose, the references for what footer refers to which section appear to be incorrect. Although the footers are present, the references are all messed up.

Code Used: The only difference in the generation of these two documents is as follows:

Aspose.Words.Document aDoc = new Aspose.Words.Document(docMemoryStream);

aDoc.Save(ms, Aspose.Words.SaveFormat.Docx);

Observation: When inspecting aDoc in the debugger, it is evident that the footer references for the sections are incorrect even before saving the document. This suggests that the issue occurs during the processing by Aspose.Words’s constructor.

Attachments: I have attached both the beforeAspose and afterAspose documents in DOCX and ZIP formats for your review.

Request: Could you please investigate this issue and provide guidance on how to ensure that the footer references remain accurate after processing with Aspose.Words?

BeforeAspose.Docx (8.6 KB)

BeforeAspose.Docx (8.6 KB)

AfterAspose.zip (15.9 KB)

AfterAspose.zip (15.9 KB)

@bradkram
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-27383

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.