Regarding SS 4.13 upgrade, which recipe CMS we should use ?
https://packagist.org/packages/silverstripe/recipe-cms
- 4.X-dev
- 4.13.X-dev
- 4.13.0
Do you mean which composer constraint should you use? I recommend reading up about how composer works, and how to choose the correct constraint, as this is a topic that goes well beyond Silverstripe CMS - but to answer the question I think you’re asking, set your composer constraint to ^4.13 and you should be good to go.
When i upgrade SS recipe CMS with any of these version (4.13.0 or 4.13.X-dev or 4.X-dev) SS Admin panel displays 4.X-Dev all time.
Is it correct behaviour ?
It sounds like you aren’t using a suitable version constraint in your composer dependencies, but it’s hard to tell without more information.
What specifically do you mean when you say “i upgrade SS recipe CMS with any of these version”? What actions are you taking to perform the “upgrade”? Are you using composer commands? If so, what specific commands are you using? Are you editing your composer.json file manually?
What does your composer.json file look like?
I had run following command.
composer require silverstripe/recipe-cms:^4.13 -W
composer.json looks like bellow.
As i have updated SS to 4.13 but in admin panel it shows 4.X-Dev.
What output do you get when you run that require. Just because you have asked for 4.13 doesn’t mean you’re going to get it if something else in your system is preventing that version from being installed.
There are a few commands you can also use to try and help you work out what’s happening:
composer info - will tell you what’s actually installed
composer why silverstripe/recipe-cms - will give information about a specific package’s constraints
composer upgrade - will try to upgrade what is already installed to the latest versions based on your composer.json constraints
The output of the commands is really important though. It will tell you what’s going on.
As stated before i have installed recipe-cms with following command.
composer require silverstripe/recipe-cms:^4.13 -W
But when i run composer info it shows following
silverstripe/framework 4.x-dev 4dd6b2f
silverstripe/recipe-cms 4.x-dev 69aa62b
Why 4.X-dev is showing with recipe-cms 4.13 upgrade ?
I can’t tell you that… it’s something specific to your install. You need to provide more info (what does the output say when you upgrade, for example) Composer is usually pretty good at providing at least some clues about what’s going on.
please see result of installing recipe-cms ^4.13
hrathod@prddigipd-49 MINGW64 /c/workspace/WebsiteApplication (SS4.13)
$ docker-compose exec php-fpm composer require silverstripe/recipe-cms:^4.13 -W
./composer.json has been updated
Running composer update silverstripe/recipe-cms --with-all-dependencies
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Lock file operations: 0 installs, 30 updates, 0 removals
- Upgrading composer/ca-bundle (1.3.5 => 1.3.6)
- Upgrading doctrine/deprecations (v1.0.0 => v1.1.1)
- Upgrading egulias/email-validator (3.2.5 => 3.2.6)
- Upgrading embed/embed (v4.4.7 => v4.4.8)
- Upgrading guzzlehttp/guzzle (7.5.1 => 7.7.0)
- Upgrading guzzlehttp/promises (1.5.2 => 1.5.3)
- Upgrading guzzlehttp/psr7 (2.5.0 => 2.6.0)
- Upgrading league/mime-type-detection (1.11.0 => 1.13.0)
- Upgrading nikic/php-parser (v4.15.4 => v4.17.1)
- Upgrading silverstripe/admin (1.12.7 => 1.x-dev 3edcf02)
- Upgrading silverstripe/asset-admin (1.12.1 => 1.x-dev a5cb4c2)
- Upgrading silverstripe/assets (1.12.1 => 1.x-dev baa3ff6)
- Upgrading silverstripe/campaign-admin (1.12.0 => 1.x-dev 010444c)
- Upgrading silverstripe/cms (4.12.1 => 4.x-dev 97861d4)
- Upgrading silverstripe/config (1.5.1 => 1.x-dev a7ee1e5)
- Upgrading silverstripe/errorpage (1.12.0 => 1.x-dev 3252355)
- Upgrading silverstripe/framework (4.12.5 => 4.x-dev 4dd6b2f)
- Upgrading silverstripe/graphql (4.1.2 => 4.x-dev b711357)
- Upgrading silverstripe/mimevalidator (2.4.0 => 2.x-dev a97a20e)
- Upgrading silverstripe/recipe-cms (4.12.0 => 4.x-dev 69aa62b)
- Upgrading silverstripe/recipe-core (4.12.0 => 4.x-dev ea00b0e)
- Upgrading silverstripe/reports (4.12.0 => 4.x-dev 2c3f2ca)
- Upgrading silverstripe/session-manager (1.4.0 => 1.x-dev 0410706)
- Upgrading silverstripe/siteconfig (4.12.0 => 4.x-dev 37a4a0c)
- Upgrading silverstripe/versioned (1.12.1 => 1.x-dev 1b67cfd)
- Upgrading silverstripe/versioned-admin (1.12.0 => 1.x-dev e9a3921)
- Upgrading symfony/event-dispatcher (v5.4.22 => v5.4.26)
- Upgrading symfony/filesystem (v5.4.23 => v5.4.25)
- Upgrading symfony/var-exporter (v5.4.21 => v5.4.26)
- Upgrading webonyx/graphql-php (v14.11.9 => v14.11.10)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 30 updates, 0 removals
As there is no 'unzip' nor '7z' command installed zip files are being unpacked using the PHP zip extens
ion.
This may cause invalid reports of corrupted archives. Besides, any UNIX permissions (e.g. executable) d
efined in the archives will be lost.
Installing 'unzip' or '7z' (21.01+) may remediate them.
- Syncing silverstripe/versioned-admin (1.x-dev e9a3921) into cache
- Upgrading guzzlehttp/psr7 (2.5.0 => 2.6.0): Extracting archive
- Upgrading guzzlehttp/promises (1.5.2 => 1.5.3): Extracting archive
- Upgrading guzzlehttp/guzzle (7.5.1 => 7.7.0): Extracting archive
- Upgrading symfony/filesystem (v5.4.23 => v5.4.25): Extracting archive
- Upgrading symfony/var-exporter (v5.4.21 => v5.4.26): Extracting archive
- Upgrading doctrine/deprecations (v1.0.0 => v1.1.1): Extracting archive
- Upgrading egulias/email-validator (3.2.5 => 3.2.6): Extracting archive
- Upgrading silverstripe/config (1.5.1 => 1.x-dev a7ee1e5): Extracting archive
- Upgrading silverstripe/framework (4.12.5 => 4.x-dev 4dd6b2f): Extracting archive
- Upgrading league/mime-type-detection (1.11.0 => 1.13.0): Extracting archive
- Upgrading silverstripe/assets (1.12.1 => 1.x-dev baa3ff6): Extracting archive
- Upgrading nikic/php-parser (v4.15.4 => v4.17.1): Extracting archive
- Upgrading composer/ca-bundle (1.3.5 => 1.3.6): Extracting archive
- Upgrading embed/embed (v4.4.7 => v4.4.8): Extracting archive
- Upgrading silverstripe/versioned (1.12.1 => 1.x-dev 1b67cfd): Extracting archive
- Upgrading webonyx/graphql-php (v14.11.9 => v14.11.10): Extracting archive
- Upgrading symfony/event-dispatcher (v5.4.22 => v5.4.26): Extracting archive
- Upgrading silverstripe/graphql (4.1.2 => 4.x-dev b711357): Extracting archive
- Upgrading silverstripe/admin (1.12.7 => 1.x-dev 3edcf02): Extracting archive
- Upgrading silverstripe/versioned-admin (1.12.0 => 1.x-dev e9a3921): Checking out e9a392146f from ca
che
- Upgrading silverstripe/siteconfig (4.12.0 => 4.x-dev 37a4a0c): Extracting archive
- Upgrading silverstripe/reports (4.12.0 => 4.x-dev 2c3f2ca): Extracting archive
- Upgrading silverstripe/campaign-admin (1.12.0 => 1.x-dev 010444c): Extracting archive
- Upgrading silverstripe/cms (4.12.1 => 4.x-dev 97861d4): Extracting archive
- Upgrading silverstripe/asset-admin (1.12.1 => 1.x-dev a5cb4c2): Extracting archive
- Upgrading silverstripe/session-manager (1.4.0 => 1.x-dev 0410706): Extracting archive
- Upgrading silverstripe/mimevalidator (2.4.0 => 2.x-dev a97a20e): Extracting archive
- Upgrading silverstripe/recipe-core (4.12.0 => 4.x-dev ea00b0e): Extracting archive
- Upgrading silverstripe/errorpage (1.12.0 => 1.x-dev 3252355): Extracting archive
- Upgrading silverstripe/recipe-cms (4.12.0 => 4.x-dev 69aa62b): Extracting archive