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
Is the bug applicable and reproducable to the latest version of the package and hasn't it been reported before?
Yes, it's still reproducable
What version of Laravel Excel are you using?
3.1.51
What version of Laravel are you using?
10.37
What version of PHP are you using?
8.1
Describe your issue
When importing a .xlsx file and the disk parameter is explicitly specified within the Excel::import() method, the following error is provided: Could not find zip member zip:///{filePath}.xlsx#_rels.rels
This is only happening when explicitly specifying the disk. When the disk is not specified, the package will take the default disk as specified within the docs and the import works as should. In such case, I confirm that the default disk is set as 'local'.
How can the issue be reproduced?
Refer to description.
What should be the expected behaviour?
Specifying the disk shouldn't break the import.
The text was updated successfully, but these errors were encountered:
Please share more information if you want this bug to be looked into. With "same problem", there's is literally nothing I can do to investigate. Please provide a failing unit test.
Is the bug applicable and reproducable to the latest version of the package and hasn't it been reported before?
What version of Laravel Excel are you using?
3.1.51
What version of Laravel are you using?
10.37
What version of PHP are you using?
8.1
Describe your issue
When importing a .xlsx file and the disk parameter is explicitly specified within the Excel::import() method, the following error is provided: Could not find zip member zip:///{filePath}.xlsx#_rels.rels
This is only happening when explicitly specifying the disk. When the disk is not specified, the package will take the default disk as specified within the docs and the import works as should. In such case, I confirm that the default disk is set as 'local'.
How can the issue be reproduced?
Refer to description.
What should be the expected behaviour?
Specifying the disk shouldn't break the import.
The text was updated successfully, but these errors were encountered: