Can't install the latest version of plugins

[01Kuzma]

Hi!
I'm still trying to succeed in October upgrade to Winter.
Now the problem lies in the outdated plugin versions.

As for example here is an amazing plugin for responsive images

On my October CMS the version 2.5.4 was of this plugin. In Winter's admin UI I pressed the button to look for the updates, but they were not found. Then I pressed the button "install plugin", and selected it from the list and now the much elder version - 2.3.11 is installed. Is it related to the marketplace? Config? How could the newest plugins be installed?

[mjauvin]

You need to use composer, the marketplace is not available yet. The plugins in the backend are a snapshot from when we forked OctoberCMS and are not up2date.

On the command-line, use the following to install the latest version of this plugin:

composer require offline/oc-responsiveimages-plugin

[01Kuzma]

@mjauvin thank you for the quick reply.
I've run the command, and it seems that it had an updated plugin, but in the admin area it's still 2.3.11
The php artisan plugin:list also shows the 2.3.11

[mjauvin]

The newest version reported on his repo is 2.4.7 but the updates/version.yaml file shows 2.5.5 as the latest.

Try this:

composer require offline/oc-responsiveimages-plugin@dev-develop

[01Kuzma]

Doesn't help :(
On this page the current version is displayed as 2.5.5

[mjauvin]

Try this:

composer require offline/oc-responsiveimages-plugin dev-develop

[01Kuzma]

the same 2.3.11 :(

[LukeTowers]

Run artisan migrate or artisan winter:up after running composer update.

[01Kuzma]

@LukeTowers it seems working. So, what is the correct subsequence for any possible future update?

1. Run composer require offline/oc-responsiveimages-plugin dev-develop
2. Then composer update
3. artisan migrate or artisan winter:up ?

The parameter dev-develop pulls the development branch from git's repo, if it exists with that name?

[WebVPF]

Updating packages

Before installing a new plugin, it is recommended to first update the application packages:

composer update

Installing plugins

Then the package (plugin) is installed:

composer require ....................

Then we run the migrations:

php artisan winter:up

In the future, to update the command composer update

[LukeTowers]

that's correct @01Kuzma, artisan migrate and artisan winter:up are just aliased versions of the same command.

[01Kuzma]

One more additional question: as I'm running a shared hosting, I'm unable to run composer directly on the hosting.
So, I'm running composer:update + artisan migrate locally, then reupload files to hosting.
In order to not copy everything round and round which folders could be skipped?
Only storage folder?

[bennothommo]

You can pretty much just copy just the modules, plugins, and themes directories. Those are the only folders that'll be directly affected by Composer updates.

[LukeTowers]

and the vendor folder @01Kuzma

[bennothommo]

Whoops, @LukeTowers is correct - vendor too :)