Closed daltonrooney closed 3 years ago
Found this comment from @brandonkelly on another plugin with a similar issue, if it helps!
Looks like this was already fixed in 3.0.3 per this commit: ace43106d0b2b8d3ab572074341211229d172cba
I’m not seeing the deprecation error when installing 3.0.3 with Composer 1, so can verify the fix worked.
Thanks @brandonkelly, I thought I was up to date, I should have double-checked!
When running composer install, I get the following message: