Basically I'm looking for a tool where you can navigate to a node/entity or give it a node id and UUID and ask the module to show how the CRUD commands would look like.
Is there anything like that?
Basically I'm looking for a tool where you can navigate to a node/entity or give it a node id and UUID and ask the module to show how the CRUD commands would look like.
Is there anything like that?
I am studying how to submit forms in the Selenium or Playright manner and when I followed a guide showing the curl equivalent of submitted forms I saw a lot of code related to the theme etc in the submission.
This is based on using the DevTools window in Chrome or Firefox and choosing the option that enables you to copy the form submission code. You can even choose to see how a curl submission looks.
Is there some other theme that would show the most minimal data, Stark, or even something more basic?
I am studying how to submit forms in the Selenium or Playright manner and when I followed a guide showing the curl equivalent of submitted forms I saw a lot of code related to the theme etc in the submission.
This is based on using the DevTools window in Chrome or Firefox and choosing the option that enables you to copy the form submission code. You can even choose to see how a curl submission looks.
Is there some other theme that would show the most minimal data, Stark, or even something more basic?
Upgrading a Drupal 10.4.x installation via composer has resulted in this bootsrap error.
LoginPHP Fatal error: Type of Drupal\shortcut_menu\ShortcutMenuLazyBuilder::$entityTypeManager must be ? Drupal\Core\Entity\EntityTypeManagerInterface (as in class Drupal\shortcut\ShortcutLazyBuilders) in /var/www/html/web/modules/contrib/shortcut_menu/src/ShortcutMenuLazyBuilder.php on line 9 drush cr, drush cc drush upgradedb:status and drush pm:uninstall all fail because of
How can I disable it?
Can I use composer to do it, or will it be better to disable it by setting the value in the system table or some other table that disables the module?
Does the latter method work for the Drupal 10+ series?
I just run this command I didn't see any drupal/core-xxxx packages in the listing.
The disk was running out of space and saw the message in the admin that I didn't have enough space, ie 1024k to upgrade Drupal core and wonder if that was why the above command didn't upgrade Drupal core as well.
I upgraded it using composer require drupal/core-recommended:11.1.10 drupal/core-composer-scaffold:11.1.10 drupal/core-project-message:11.1.10 --update-with-all-dependencies
It was as far as I could go probably it was a Drupal CMS 1.0 installation.
I've been using Drush on Drupal 7 for a long time, but having started on Drupal 11 I've gotten more used to the Composer approach and see on Drupal.org that many Drupal 7 modules can be installed through composer.
Are there any gotchas installing Drupal 7 and installing/upgrading modules with composer?
Is Composer usage on Drupal 7 mature and comparable or even better than Drush?
I am trying to upgrade a Drupal CMS 1.1.0 installation and Composer says drupal cms is locked to 1.1.0 and causes conflicts with other modules.
Below is a quotation from this link - https://www.drupal.org/project/cms/releases/2.1.0-beta1
Drupal CMS 2.1.0-beta includes a new site template, Haven, with a warm and bright design and features aimed at non-profit websites.
This release should be used for testing only and is not suitable for building websites. There is no update path for Drupal CMS.
It may be a glorious journey to upgrade from the current Drupal CMS 1.1.0 but I don't feel that adventurous.
Right now I just want to make sure I don't fall behind on security updates with all installed modules whether they are part of the Drupal CMS 1.x recipes even if I don't upgrade to 2.x.x.
If Drupal CMS 1.x is locked to particular versions of Drupal Core does that mean it will be eventually insecure and have to be abandoned, unless it offers the ability transfer the content to Drupal 2.x?
