I need a number of custom fields for my current development, 1 of these is effectively a base field which is used on it's own in some places, but it also extended into further custom fields.
Classic design suggests lots of small modules, however, these field types are bespoke to this project so it seems logical (in my mind) to incorporate all of these into a single project_custom_fields module. I have other non-related bespoke functionality in individual modules, but it seems overkill to have a module for each field type.
I would appreciate if anyone could explain the following for me. Drupal guides says you should run this command to update drupal core or modules with composer:
"composer update drupal/core --with-dependencies" or "composer update drupal/modulename --with-dependencies"
Can I not just run "composer update"? Why specify "drupal/core" or "drupal/modulename"? Why add "--with-dependencies"?
I do not understand the composer documentation. It says:
In Acquia dev desktop, I opened the drush console. I typed composer install and got the following error. This is the first time I used this command. Please advise.
Long ago I set up a web app for a small book publisher to manage to manage relations with bookshops. A CRM of sorts.
The app is in Drupal 6.15, ran on a version of PHP that's no longer supported, and depended on several modules that are no more.