-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CloneRow to include multiple rows #283
Comments
Hi @cyrillkalita. Feel free to fork PHPWord and make any changes to the code as required by your project. You can also request a pull request if you think your enhancement will be useful for other users. To be integrated into the |
As for me, I clone rows with XSLT. :) |
@flohmueller That is a nice table function, however, a table (or any other object) can be cloned with cloneBlock(), so there is no need for a specialized function |
@FBnil Cloning a block only allows a single replacement, so if you have a table that has multiple replacements in it then a way to iterate over the cloned tables and replace all of the different placeholders is necessary. See #1071 FYI, the additions by @flohmueller still seem to work, after replacing |
@jeffsrepoaccount Ah, yes, next version (0.15.0) will have enumeration, thus all macro's in your cloned block will have #1 or #2 (if it's the second cloned block) ... etc appended to them. This way you can setValue() without problems. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Would it be to much to suggest an update for Tempalte/cloneRow function to include the third parameter, $search_end, null by default, that would serve as the value to look up to close the row?
if null, it is then made equal to the $search and update the functions that look up closing w:tr tag by the $search_end - thus allowing cloning multiple rows at a time?
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: