Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Installing SilverStripe

Getting SilverStripe up and running on your computer and on your web server.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Using Composer to install and update modules


15 Posts   4837 Views


23 November 2012 at 3:10am Forum Moderator, 801 Posts

Filed a bug with composer:

Hm, hardcoding versions will be a royal pain in terms of release management - you'd have to remember to commit those *just* before tagging, each time. We could read/write the composer.json dynamically with the "phing tag" build command, but that sounds like a lot of work for a stopgap solution.

But more importantly, it breaks the collaboration model. We ask people to simply use "composer update --dev" to get started if they want to contribute. That won't work, since framework and cms will still be at the checked out tag.

For now, I've updated the contributing chapter:


4 October 2013 at 11:26am Community Member, 6 Posts

I am new to SilverStripe, and encounter the same problem as described by _Matt on nov 16,2012.

I do not see any information about this problem in the documentation page at Is it about to be solved ?

If not, is the method suggested in this thread the 'official' one for the moment ?

Thanks for your advice.


4 October 2013 at 12:44pm Forum Moderator, 801 Posts

Can you run a "composer selfupdate" to ensure you're on the latest version?
If you're trying to add a module, do it via "composer require -vvv <module>" and paste the output here.
Otherwise paste the specific error message you're getting on "composer install" or "composer update".


4 October 2013 at 7:49pm Community Member, 6 Posts

Ok, here is my session log.

$ ./composer.phar selfupdate
You are using the latest composer version.

$ sudo mv composer.phar /usr/bin/composer

$ cd /home/www/shingan31
$ composer require -vvv silverstripe/sqlite3 dev-master
./composer.json has been updated
Reading ./composer.json
Executing command (CWD): git describe --exact-match --tags
Executing command (CWD): git branch --no-color --no-abbrev -v
Executing command (CWD): hg branch
Loading composer repositories with package information
Writing /home/hubert/.composer/cache/repo/ into cache
Writing /home/hubert/.composer/cache/repo/ into cache
Reading /home/hubert/.composer/cache/repo/ from cache
Writing /home/hubert/.composer/cache/repo/ into cache
Reading /home/hubert/.composer/cache/repo/ from cache
Reading /home/hubert/.composer/cache/repo/$installer.json from cache
Updating dependencies (including require-dev)
Reading /home/hubert/.composer/cache/repo/$cms.json from cache
Writing /home/hubert/.composer/cache/repo/$framework.json into cache
Reading /home/hubert/.composer/cache/repo/$simple.json from cache
Reading /home/hubert/.composer/cache/repo/$sqlite3.json from cache
Reading ./composer.lock
Reading /home/hubert/.composer/cache/repo/$installers.json from cache
Reading /home/hubert/.composer/cache/repo/$baton.json from cache
Reading /home/hubert/.composer/cache/repo/$reports.json from cache
Reading /home/hubert/.composer/cache/repo/$blackcandy.json from cache
Reading /home/hubert/.composer/cache/repo/$recaptcha.json from cache
Reading /home/hubert/.composer/cache/repo/$mobile.json from cache
Reading /home/hubert/.composer/cache/repo/$spamprotection.json from cache
Your requirements could not be resolved to an installable set of packages.

Problem 1
- The requested package silverstripe/cms 1.0.0 could not be found.
Problem 2
- The requested package silverstripe/framework 1.0.0 could not be found.

Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <> for more details.

Read <> for further common problems.

Installation failed, reverting ./composer.json to its original content.


4 October 2013 at 10:24pm Forum Moderator, 801 Posts

You need to retain VCS information in the base installation in case you've done it through "composer create-project".
Composer commands don't work on archive downloads from That's a limitation by Composer, not us.
I've created a FAQ entry:


5 October 2013 at 1:03am Community Member, 6 Posts

Sorry, but I read and re-read your answer and the FAQ and I still don't understand where I was wrong (and still don't know what to do either !)
I just followed the instructions on your site for the installation of SS3 via composer. SS3 install is Ok but I can't install any module after that.
Thanks for your help


6 October 2013 at 8:13am Community Member, 6 Posts

Finally, I found out why!
I installed SilverStripe with the composer create-project command ending with the version number (3.1.0).
I shouldn't !
Perhaps the documentation should further emphasize this point to avoid for beginners like me to be blocked.