Posts on common errors when upgrading Laravel and deep dives into new Shift features.
PHP2Shell is a critical remote code execution vulnerability affecting all PHP versions. Patch PHP now, then use it as the nudge to upgrade PHP and Laravel to the latest supported versions.
Introducing a built-in AI Review of your Shift. Providing a second pass on your upgrade, guided by Shift's detailed comments combined with AI's context.
Introducing AI skills to fully automate the entire Shift workflow.
Shifts now include copyable prompts to automate even more with AI.
Shift now supports adding a shift.yaml file to your repository, making it easy to configure webhook automation per project.
The Upgrade Checker, Tailwind Converter, and Dusk Converter Shifts have been decommissioned.
Starting in January, subscribers now receive an automated PR containing curated refactors on the first of every month.
A deep dive into automating the upgrade of Laravel config files by merging customizations and detecting ENV variables.
An explanation of the issue and potential solutions for the error after upgrading to Laravel 11: "Database file at path [database/database.sqlite] does not exist."
An explanation of the issue and potential solutions for the error after upgrading to Laravel 11: "Database file at path [database/database.sqlite] does not exist."
An explanation of the issue and potential solutions for the Composer error: "Ambiguous class resolution"
An explanation of the issue and potential solutions for the Composer error: "dependency should not contain uppercase characters"
An explanation of the issue and potential solutions for the Composer error: "Does not comply with psr-4 autoloading"
An explanation of the issue and potential solutions for the error after upgrading to Laravel 8: "Object of class `AssertableJsonString` could not be converted to string"
An explanation of the issue and potential solutions for the error after upgrading to Laravel 7: "CORS config allowed_origins should be an array"
An explanation of the issue and potential solutions for the Laravel error: "Please provide a valid cache path"
An explanation of the issue and potential solutions for the error after upgrading to Laravel 8: "Target class [bindings] does not exist"
An explanation of the issue and potential solutions for the Laravel error: "Undefined index: App\Models\User"
An explanation of the issue and potential solutions for the error after upgrading to Laravel 6: "Undefined index: controllers_base_namespace"
