Skip to content
This repository has been archived by the owner on Apr 17, 2024. It is now read-only.

What is the proper way to update a Contenta CMS site project? #269

Closed
shrop opened this issue Mar 20, 2018 · 6 comments
Closed

What is the proper way to update a Contenta CMS site project? #269

shrop opened this issue Mar 20, 2018 · 6 comments

Comments

@shrop
Copy link
Contributor

shrop commented Mar 20, 2018

What is the proper composer command to update a Contenta CMS project? I don't see this documented but have seen the following discussed:

  • composer update contentacms/contenta_jsonapi --with-dependencies
  • COMPOSER_DISCARD_CHANGES=1 composer up --with-dependencies -o --prefer-dist

I will be exporting my own config and adding modules. Looking for general guidance around these kinds of things in context of Contenta CMS. Love to see if anyone has info on this to make sure I am on the right track. Thanks!

@e0ipso
Copy link
Member

e0ipso commented Mar 20, 2018

This is intentionally not documented here. Contenta CMS is a Fork & Go solution. There is no supported upgrade path. Use common Drupal update techniques instead.

@e0ipso e0ipso closed this as completed Mar 20, 2018
@shrop
Copy link
Contributor Author

shrop commented Jun 23, 2018

Just catching up here. Thanks for that clarification @e0ipso!

@ghost
Copy link

ghost commented Sep 17, 2018

I'm struggling trying to figure out how to update Drupal core in Contenta. So far nothing I've tried has worked so I'm stuck on 8.5.3 while 8.6.1 is most current. Any suggestions on where to look further?

@ghost
Copy link

ghost commented Sep 17, 2018

I finally figured it out. I used the Composerize module to generate a composer.json file and then updated the required version of Drupal in composer.json and everything seems to be working great.

@matgianesini
Copy link

Hello everyone! I spent a whole day trying to figure out how to update Contenta using composer, and something quite simple just worked for me:

The main question for me as a composer noob was... how can composer update drupal/core when that is not included in Contenta's composer.json file? I'm guessing the composerize module, proposed above, solves exactly that. Still, in my case I couldn't get it to work that way.

In the end it seems this was all I needed:
composer update drupal/core webflo/drupal-core-require-dev --with-dependencies

All green checks on my Contenta now. I know --with-dependencies is regarded as poor form in composer and drupal circles... but other than that, any of you know if there's anything wrong with this simple one liner?

@BrianGilbert
Copy link

@matgianesini I usually just do composer remove drupal/core and it automatically get reinstalled with the latest version because it's a dependency

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants