You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this issue is somewhat related to this issue: #548
Basically, I have written a function that scans through a directory, identifies all docx files and then scans each for placeholders ( like ${NAME} ) in the text.
If placeholders are found, these are stored in a database table.
This works well so far, but now I noticed that the placeholders are not always delivered correctly by the getVariables() function of PhpWord\TemplateProcessor. For some docx files I get the correct placeholder names, for others I get the names surounded by a bunch of strange xml tags, like </w:t></w:r><w:r w:rsidR="004F6DA4"><w:t>ADRESSE</w:t></w:r><w:r><w:t>
That is probably the reason why I cannot use the setValue() function on these documents.
When I use the php strip_tags() function on the 'broken' tag first, the setValue() succeeds though.
Hello,
this issue is somewhat related to this issue: #548
Basically, I have written a function that scans through a directory, identifies all docx files and then scans each for placeholders ( like ${NAME} ) in the text.
If placeholders are found, these are stored in a database table.
This works well so far, but now I noticed that the placeholders are not always delivered correctly by the getVariables() function of PhpWord\TemplateProcessor. For some docx files I get the correct placeholder names, for others I get the names surounded by a bunch of strange xml tags, like
</w:t></w:r><w:r w:rsidR="004F6DA4"><w:t>ADRESSE</w:t></w:r><w:r><w:t>
That is probably the reason why I cannot use the setValue() function on these documents.
When I use the php strip_tags() function on the 'broken' tag first, the setValue() succeeds though.
Do you know of this issue?
Thank you very much,
Tom
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: