Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
In order to try out Telescope, I decided to migrate my project from 5.6 to 5.8. Followed the instructions to migrate from 5.6 to .7 and then .7 to .8 (including copying svg files from GitHub). Everything seems to be working fine, including Telescope. However, my error pages still use the old templates. I have not published / customized them, so the ones in vendor/ are the ones being used.
I am wondering why composer update is not updating these files? To be honest, the error templates themselves aren't a huge issue (I could just copy from GitHub if it came to that), but if these files are not being updated I have to wonder what other files aren't being updated as well. Can't very well proceed with a deploy to production with that level of uncertainty.
composer.json
"require": {
...
"laravel/framework": "5.8.*",
composer.lock
...
"name": "laravel/framework",
"version": "v5.8.8",
404.blade.php
@extends('errors::minimal')
@section('title', __('Not Found'))
@section('code', '404')
@section('message', __('Not Found'))
Human may make mistake but I don't see any problem without updating the error template and i believe and appreciate their great job to update what are most important or have impact and documented it well. Anyway, If uncertain then identify/find it out and report the issue to the github or else may just stop using it or find better solutions. Peoples spent ton of hours to maintain and contribute and make it better, we just use it for free and take it as granted...
The 5.7 upgrade guide documents the new svg folder. Look for svg folder added
Not sure why it does not get merged in automatically but I guess for an existing application it does not assume it can go adding folders and potentially overwriting something in your project
The upgrade notes reference the git path to get the missing svg files
Also when updating, it's good to compare what's new in laravel also. I keep a laravel_old and a laravel_new folder so I can compare.
The framework is taken care of via the vendor folder when updating.
I use winmerge, but surely there is similar for linux. I can easily merge the files that has changed. But yet being careful not to over-ride custom code, etc.
So you need to update laravel also.
Edit: When updating get from here:
https://github.com/laravel/laravel/releases
The release page, they are stable. Update laravel first before updating the framework.
@siangboon I'm sure they have updated the error templates, it's well documented. The issue is that composer seems not to reflect those changes in my vendor directory.
@snapey Thanks for the reply. I have followed the upgrade instructions, including the part about svg files. They are in the correct folder in public/ and are not the issue. Issue is with the error blade templates in vendor/ not being updated.
@jlrdw Thanks for the info. As you say, the framework (the packages in vendor/) should be automatically updated by composer. However, it seems that, at the very least, those error templates are not being updated. From search queries I can see that are updated for everyone else as far as I could see, so I'm wondering if there could be some other issue preventing composer from upgrading to the new files.
I've already tried deleting vendor/ and running composer install instead of doing an update. I guess I'll try maybe clearing the composer cache and running install again...
I am saying you need to update laravel manually also. Not just the framework.
In fact Winmerge also shows any added files, deleted files, etc. Kind of like github, but better if just updating development and needing fine tuning.
Please or to participate in this conversation.