Problem with field update page layout update after Upgrade from 14.8 to 14.12

Hi there,


I have not yet been able to assemble a simple test case for this issue but maybe you already know about this and are able to help me.

I load a word document which has some (self defined ( eg “{placeholder}”) placeholders in its header. I programatically change the placeholders to values.
After this, my document.getText() correctly shows all the placeholders replaced with their desired values.

If I now call doc.updatePageLayout() the text reverts to its previous state with my placeholders restored.

I was able to pinpoint this to the call of the method “updateFields” and “updatePageLayout”.

With Aspose words version 14.8 this worked as expected, with the most recent version I am running into problems.

Any advice?

Hi Scherge,

Thanks for your inquiry. It would be great if you please share following detail for investigation purposes.


  • Please attach your input Word document.
  • Please

    create a standalone/runnable simple Java application that demonstrates the code (Aspose.Words code) you used to generate
    your output document

  • Please attach the output Word file that shows the undesired behavior.
  • Please
    attach your target Word document showing the desired behavior. You can
    use Microsoft Word to create your target Word document. I will
    investigate as to how you are expecting your final document be generated
    like.

Unfortunately,
it is difficult to say what the problem is without the Document(s) and
simplified application. We need your Document(s) and simple project to
reproduce the problem. As soon as you get these pieces of information to
us we’ll start our investigation into your issue.

Hello Tahir,


having anticipated your request, I had started to try reproducing the issue with a little application.

I managed to condense it down towards a java application which will under words 14.8.0 work as I expected it and under 14.12.0 will show some undesired result.

Please find the files attached

Hi Scherge,

Thanks for sharing the detail. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-11344. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hi Tahir,


can you give any forecast whether this issue will be addressed in the near future? We’re hitting some problems which would be solved with a newer version of Aspose but we cannot use it because of the problems mentioned above.

Hi Scherge,

Thanks for your patience. The
issue WORDSNET-11344 has been resolved and its fix will be available in
Aspose.Words v15.2.0. Hopefully, next version of Aspose.Words will be available in next week. We will inform you via this forum thread as soon as the
this release is published.

Thanks for your patience.

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


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