Laravel Update from 5.1 to >=5.5 [closed] - laravel

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I am trying to update my current Laravel version(5.1), but unable to update.
Can anyone please help me to update Laravel version from 5.1 to 5.5, 6.0?

Your question is not very specific. Where are your problems exactly?
In general, you need to follow the specific tasks to upgrade. Laravel has created one page for each upgrade (5.1 to 5.2, 5.2 to 5.3...)
On these pages the steps are described and also what changes has been implemented to the code.
I would upgrade version to version and have a look at the changes in the code.
Upgrade to 5.2:
https://laravel.com/docs/5.2/upgrade
to 5.3:
https://laravel.com/docs/5.3/upgrade
to 5.4:
https://laravel.com/docs/5.4/upgrade
to 5.5:
https://laravel.com/docs/5.5/upgrade
to 6:
https://laravel.com/docs/6.x/upgrade

Update your composer.json file with the desired version of laravel. Also, check if your desired version requires a specific PHP version to run it.
"require": {
"php": "^7.0",
"laravel/framework": "5.5.*",
},
Now, delete your vendor folder and composer.lock file inside your project folder.
Here is the Laravel Upgrade Guide where you can verify the functions that need to be updated at the code level. If you are upgrading, then you need to add the listed updated functions of the higher version from the guide. And if downgrading, you need to remove the updated functions from your code if you have used any from the higher version.
Then, run the following command inside your project folder:
composer install
also, you can do it with this command:
composer update --no-scripts
this will upgrade to the latest one.

Related

Why is using composer for TYPO3 production deployments discouraged? [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 days ago.
Improve this question
The official documentation for deploying TYPO3 states "The composer install command should not be run on the live environment."
Why is this? As far as I know deployer - a well received deployment tool for TYPO3 - does exactly this.
TYPO3 Recommends Composer as the Main Installation method.
but its good practice to run "composer install" on your local machine (or a CI Pipline like Github Actions) then move the downloaded code to the final destination server. and i think deployer is dooing exaclty that.
this has multiple advantages:
less dependancies on the production system. (one less software there to be exploited)
possiblity to run unit tests before deployment
add additional build steps for your deployment (like compilin sass
or javascripts)
ther is no need for credentials of private repositories on the production server

Laravel Varbox fresh installation failed [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I’ve downloaded the free version of Varbox wanting to start a new project using this platform that seems to be Laravel based, but it seems that after install I don't see the specific Laravel homepage, as I'd expect from a Laravel project.
I’ve setup a git repository with the Varbox source code, but it doesn’t seem to be a working Laravel project (eg. it doesn’t have an .env file, php artisan is not accessible).
You shouldn't attempt to use Varbox as a monolithic application.
Varbox has been designed as a Composer package which you'll have to locally require in your own Laravel projects, so that means you'll need to already have a working Laravel projects on top of which to install Varbox.
please click to see what I'm talking about
Please follow the documentation (I suggest installing it in the automatic way, as it's less time consuming): https://varbox.io/docs/1.x/installation

Duplicate script tag in blade.php file [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
I'm using PhpStorm 2019.3.1 and I see this error. How to fix this problem?
It's a bug in IDE (in one of the bundled plugins to be precise). To get rid of it you would have to disable Vue.js plugin (worked well for me, especially since I do not use Vue)...
https://youtrack.jetbrains.com/issue/WEB-42930 -- watch this ticket (star/vote/comment) to get notified on any progress.
As per #lena comment: as a workaround, you can disable Vue | Duplicate template/script tag inspection in Settings/Preferences | Editor | Inspections
P.S. This issue can be reproduced with any project with vue npm package installed.
If you do not use Vue in your projects, I guess getting rid of package.json or at very least vue entry from there should also do the trick.
UPDATE 2020-03-05:
The aforementioned ticket is now marked as fixed for 2020.1 version.

How to upgrade laravel 5.1 to 5.6? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I want to upgrade laravel on my website from 5.1 to 5.6, please tell me how it is possible?
You should follow the upgrade guides here https://laravel.com/docs/5.2/upgrade
Start with 5.2 and work your way up to 5.6 or 5.7 that was released a few days ago.
I had to upgrade a 5.1 app before and I ended up just creating a new blank Laravel 5.5 project (latest at the time) and copying over everything from the old app starting with the route folder. Don't just copy them over, make sure you move each file individually to avoid breaking something. You should definitely be prepared to spend an hour or so on it.

How can I look at my composer packages and see what is out of date? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I am using Magento 2 and I run all of my updates through Composer. I would like to see what Composer packages I have that are currently out of date. When I run composer outdated I get this:
[InvalidArgumentException]
Command "outdated" is not defined.
Is there another command I can use?
Maybe you have an old version of Composer, before the outdated command has been introduced.
As its documentation says, composer outdated is just an alias of composer show -lo. The two options of composer show mean:
-l (short of --latest): List all installed packages including their latest version.
-o (short of --outdated): Implies --latest, but this lists only packages that have a newer version available.
Or you can run composer self-update to update Composer to its latest version then run composer outdated again.
Your Composer is too old. outdated command was introduced in 1.1.0. If you're using pretty ancient 1.0.0-beta2, you may missing many features and bugfixes, you should really upgrade to the last version.
If 1.0.0-beta2 is the last version available in repository of your Linux distribution, you may try uninstalling it and download last version directly using instructions from documentation. Official repositories are often focused on stability and they're avoiding non-patch upgrades. In many cases it means that PHP packages from official repositories are pretty outdated (2 years is like ages in PHP world). You should either install such packages directly from source or use some alternative repositories with more fresh packages (like this PPA for Ubuntu).

Resources