-
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
ziparchive error when phpword templateprocessor called #657
Comments
When checked files with is_readable(), it is readable, but get above error. |
As I know you can only use .docx format for temaplate files. |
Hi, did you find a solution, I try to read the file from an file abstraction layer which returns sadly doesn't work at all, now I tried to create a temporary file for processing, but still doesn't work:( Thanks |
Has anyone made .DOC file work on templateprocessor? |
Still didn't find a solution for |
I'm facing the same issue. I have a DOC file. It is readable as well. I got I tried to loading format change as well with MsDoc. but still not woking. Can you please support to here :) |
This happended to me, the problem was due to the line endings in the doc file. My server runs on linux, my doc file was saved with LF line ending, but pulling the repo changed the line endings to CRLF.
The problem disappeared. You can check the line endings of your file using
If lines end with M$ you have CRLF line endings. |
Hi,
I am trying to replace some content in a word file, using following code.
But it gives following errrors.
Warning: ZipArchive::getFromName(): Invalid or unitialized Zip object in /home2/xxx/public_html/xxx/FL/xxx/sc/includes/PhpWord/Shared/ZipArchive.php on line 198
Warning: ZipArchive::getFromName(): Invalid or unitialized Zip object in /home2/xxx/public_html/xxx/FL/xxx/sc/includes/PhpWord/Shared/ZipArchive.php on line 201
The file path is correct and also the solution needs to support both *.doc and *.docx formats.
It will be a great help if you can support me on this.
Thank you.
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: