- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- 🇻🇳Vietnam tien.huynh
Hi Grabby,
I also got the same error on php 8.1 with "drupal/permission_spreadsheet": "2.0.0".
I created a patch ( permission_spreadsheet_error_on_xlsx_import.patch → ) that automatically fixes this bug .It's work in "drupal/permission_spreadsheet": "2.0.0" and php 8.1
- Status changed to Fixed
5 months ago 1:08pm 5 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.