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
I'm not sure if this is a bug or if it's just me. I required axlsx in my rails 3 project, and Package::validate method did not work giving me the enoent error saying lib/schema/#{somefile}.xsd was not a file or directory. I went into the gem in .rvm and manually added the absolute dir path to each of these xsd constants. That fixed my error and validate worked.
So I think there is a bug when setting the xsd constants to relative paths.
Also, I'm using Mac excel 2011 and the latest axlsx gem 1.0.15. Everytime I create an xls file, it needs to be repaired. I looked into an earlier bug submission #1 about this. At least for me, the bug is still persisting.
The text was updated successfully, but these errors were encountered:
Thank you very much for your message.
You are quite right that the gem should not assume that the current directory is the gem's directory.
I've made some changes for release in .16
Ill need a bit more time to test the excel repair. Would it be possible to get a copy of an un-repaired xlsx file for testing?
I'm not sure if this is a bug or if it's just me. I required axlsx in my rails 3 project, and Package::validate method did not work giving me the enoent error saying lib/schema/#{somefile}.xsd was not a file or directory. I went into the gem in .rvm and manually added the absolute dir path to each of these xsd constants. That fixed my error and validate worked.
So I think there is a bug when setting the xsd constants to relative paths.
Also, I'm using Mac excel 2011 and the latest axlsx gem 1.0.15. Everytime I create an xls file, it needs to be repaired. I looked into an earlier bug submission #1 about this. At least for me, the bug is still persisting.
The text was updated successfully, but these errors were encountered: