We are testing upgrading Aspose.words from 13.2 to 15.5, and we are using a particular letter template to test. After upgrading to 15.5, some tags which are defined in footer are not displaying properly in the generated letter. We have used the same tags in the body of the documents and they are working fine. Also in our testing process we noticed that if we have only these tags in footer and no other places still working fine. So the issue appears when we have those tags in both in body and the footer.
Thanks for your inquiry. Please upgrade to the latest version of Aspose.Words for .NET i.e. 18.6 and see how it goes on your end?
In case the problem still remains, please ZIP and attach the following resources here for testing:
- Your input Word document
- Aspose.Words 18.6 generated output document showing the undesired behavior
- Aspose.Words 13.2 generated output (expected) document showing the correct results
- Please create a standalone simplified console application (source code without compilation errors) that helps us to reproduce your specific problem on our end and attach it here for testing.
As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.
Actually we are seeing this issue when upgrading Aspose.words for JAVA from 13.2 to 15.5.
I have provided some of the information regarding the expected behavior , undesired behavior and the input document. Regarding the application, not sure how to go through that, but I did some investigation and figured
out that this issue is happening when we have similar MERGEFIELD in both the body and the footer of the document. when the documentbuilder process the document after finding the first start tag in the footer it will skip the footer and continue processing the body with the same start tag in the body, in this way the Endtag in the footer never be visited and it will be remained unprocessed.
upgradingfrom13.2to15.5.zip (35.9 KB)
We need piece of source code to reproduce the problem on our end. Can you please also create a standalone simplified console application (source code without compilation errors) that helps us to reproduce your specific problem on our end and attach it here for testing? Thanks for your cooperation.