Skip to content
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

Xlsx file generated with inline strings can not be imported #46

Open
m-develops opened this issue Feb 22, 2017 · 9 comments
Open

Xlsx file generated with inline strings can not be imported #46

m-develops opened this issue Feb 22, 2017 · 9 comments

Comments

@m-develops
Copy link

I am using mk-j/PHP_XLSXWriter to generate an xlsx file.
The change that was made in the recent version of PHP_XLSXWriter was to stop using shared string, and to write all strings as inline strings. Switching to inline strings was done on purpose to reduce memory usage when writing gigantic spreadsheets.

But when i now try to import/read this script with the spreadsheet-parser it does not read any values but the nummeric values and al the other columns are shown blank/empty.
An older version of PHP_XLSXWriter using shared strings can be imported.
Can anyone explain what is going wrong and why the columns array empty in de generated array?

@xakepsoft
Copy link
Contributor

xakepsoft commented Jun 30, 2017

This has been fixed on 9 Nov 2016 already !
Update your local repository with latest changes...

@juanmi108
Copy link

We had the exact same issue. Turns out the the generated xlsx hat no SharedStrings in it. Manage to fixe it and submited a pr :) #55

@xakepsoft
Copy link
Contributor

Could you provide problematic xlsx file ?

@juanmi108
Copy link

sure,
Product Lagerdata_6_11_2018 (1).xlsx
here is an example

@xakepsoft
Copy link
Contributor

very strange, this file reads perfectly without any problems...

@juanmi108
Copy link

Strange, I was using the latest release 1.2.2 if it helps

@xakepsoft
Copy link
Contributor

I used 1.2.0 , works flawlessly.

Could you try 1.2.0 ?

@juanmi108
Copy link

Yes it works on 1.2.0

@stof
Copy link
Contributor

stof commented Feb 27, 2019

It seems like #43 (released in 1.2.3) is related to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants