- Issue created by @vishalkhode
- Status changed to Closed: won't fix
about 2 years ago 9:26pm 23 February 2023 - Status changed to Fixed
about 2 years ago 9:28pm 23 February 2023 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Pushed a composer.json limit to 3.x branch
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
about 2 years ago 7:00pm 13 March 2023 - 🇮🇳India vishalkhode
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
@vishalkhode yes, by design. Please stay on v2 if you are using php 7.4
- Status changed to Active
about 2 years ago 4:27am 16 March 2023 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
@mstrelan pointed out that it would be possible to update to 3.0.0 on php 7.4, run the updates, but then put your site in a broken state.
So I think we should add php 7.4 support back in 3.0.2 and remove it in 3.1.0
- 🇮🇳India vishalkhode
Hi @arowlan
Yes, this would be really helpful.So I think we should add php 7.4 support back in 3.0.2 and remove it in 3.1.0
- @vishalkhode-0 opened merge request.
- Status changed to Needs review
about 2 years ago 6:33pm 18 March 2023 - 🇮🇳India vishalkhode
Hi @larowlan
I've fixed it and created an MR !16. Please see.
cc: @mstrelan -
larowlan →
committed e3cfcf17 on 3.x authored by
vishalkhode →
Issue #3344077 by vishalkhode, larowlan: ParseError: syntax error,...
-
larowlan →
committed e3cfcf17 on 3.x authored by
vishalkhode →
- Status changed to Fixed
about 2 years ago 11:24pm 21 March 2023 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Cutting 3.0.1 which will support PHP 7.4 and 3.0.2 which won't
Automatically closed - issue fixed for 2 weeks with no activity.