![]() ![]() ![]() ![]() I can contact them but they're in Europe and I'm not, so the lag time in responses is sometimes 24+ hours. And it seems that once you start down the Composer road, there's no way back. I'm only doing composer because it seems Drupal is now forcing this (and it's the only way to install some modules like entity_print). The documentation they have is fairly sparse and doesn't cover using Composer. I started doing that last night, but it was so damned slow I figured I'd try to install a full version this morning then just upgrade Drupal, which they tell me I should be able to do. That's tedious because some have a lot of fields, and in order to work with their stylesheets, you'd need things to be properly named (machine names). You can install it as a straight theme over a vanilla drupal install, but you lose the content types and need to make them from scratch. Well, they give it to you in case you want to use their pre-defined content types. " composer remove drupal/core-project-message" " * Remove the plugin that prints this message:", " * Get involved with the Drupal community:", ![]() " from the drupal/legacy-project template! ", " Congratulations, you’ve installed the Drupal codebase ", In the composer.json file, though is this, under "require": ": Within the Drupal admin pages, the recommended version is 8.9.1 - does composer not pay attention to that? Updating dependencies (including require-dev) Loading composer repositories with package information In any case, I now have all my modules up to date using composer, and want to update core.Ĭomposer update drupal/core-recommended -with-dependencies I have very little experience with Composer (though so far I've grown to really hate it, but that's another story). The theme developer tells me there is no issue with upgrading core to 8.9.1. It has composer.json files so I would assume it's ready to be upgraded with composer. It comes with Drupal Core 8.8.4, and that's how it was installed (imported their db file, installed the theme/core package, and loaded up the site). I was running the commands from the wrong place.\*Īpologies for wasting everyone's time, but thanks for pointing me in the right direction! This is what happens when you work with three terminal windows at the same time: one for running commands, one with an editor and one for poking around in a directory. it wasn't updating to 8.9.1 because I was editing the right composer.json file, but in the wrong folder. lo and behold - a bunch of drupal core folders and files were there that shouldn't have been. It was u/alphex's question below that tipped me off "Where did you get "core" for this D8 project?" - I started digging around in the web root, and that's when I realized I was calling composer from one level up, in the web root's parent directory. So it turns out that I was running composer from one directory up. If you wish to post something of that nature we suggest you check out 's paid services job board Our Friends Friday: Useful things to know - Things you wish you had known earlier about Drupal.Thursday: Development questions & discussion - Coding questions go here.Wednesday: Contrib modules chat - Talk about recently tried modules, recommendations, warnings, etc.Tuesday: Triumphant Tuesday - post recent Drupal successes and site launches.Monday: Beginner questions - no question is too easy.Would you or someone you know make for an interesting Drupal AMA? Message the mods. When would you like to start? Let us know!.Mike Gifford (Accessibility Core Maintainer Drupal 8) – Click Here.The place for news, articles and discussion regarding one of the top open source (GPL) CMS platforms: Drupal. Check out the sidebar for our AMA schedule, or view our past AMA's. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |