Upgrade from v2 to v3 but running into a problem

I've followed the instruction guide how to upgrade from version 2 to 3. But I run into this issue (see screenshot attached). Any ideas how to fix his?
No description
Solution:
Summary: - Updated filament-access-control in composer.json to "chiiya/filament-access-control": "*", - Delete composer.lock file - Delete node_modules - Delete vendor...
Jump to solution
11 Replies
awcodes
awcodes13mo ago
You need to see if they have a v3 compatible version or not. If they do, just change the version number for the plugin in composer.json and run update again.
gemini.dev
gemini.devOP13mo ago
Hi @awcodes, thanks for your answer - I'll have a look
gemini.dev
gemini.devOP13mo ago
gemini.dev
gemini.devOP13mo ago
I have then deleted composer.lock file and vendor folder.
gemini.dev
gemini.devOP13mo ago
Once I deleted it, I ran composer install. This then resulted me into the following error
No description
awcodes
awcodes13mo ago
Seems like filament itself didn’t get upgraded.
gemini.dev
gemini.devOP13mo ago
Yeah that's right, that is because I deleted my composer.json by accident and not the .lock file 😄 - and then I restored it, forgetting to update all the versions.. Just noticed the title of this thread is v4 and not v3 Upgrade from v2 to v4 but running into a problem I'm not sure I am able to alter this? Ok that has now worked. pheww
gemini.dev
gemini.devOP13mo ago
No description
awcodes
awcodes13mo ago
🎉
gemini.dev
gemini.devOP13mo ago
🙂
Solution
gemini.dev
gemini.dev13mo ago
Summary: - Updated filament-access-control in composer.json to "chiiya/filament-access-control": "*", - Delete composer.lock file - Delete node_modules - Delete vendor - Run CMD as administrator - Run composer install

Did you find this page helpful?