Blog

Drupal form API states can support multiple values.  

E.g.

$form['field_something']['#states'] = [
  'visible' => [
    ':input[name="field_else[0][target_id]"]' => [
      ['value' => 'one'],
      ['value' => 'two'],
      ['value' => 'three'],
      ['value' => 'four'],
    ],
  ],
];

This also applies to:

• Drupal 7
• Drupal 8
• Drupal 9
• Drupal 10

It is not possible to update a checkout object via Shopiy's Admin REST API unless the custom app created the checkout object. 

Per Shopify Staff:

The checkout PUT endpoint is intended to only be used to modify checkouts that were created by that same app.

Reference: 

• https://community.shopify.com/c/graphql-basics-and/update-checkout-not-working-on-api-2023-01-checkouts/m-p/2025238/highlight/true#M5766

In composer.json add to the scripts section. See below:

"scripts": {
    "pre-install-cmd": [],
    ...
    "post-drupal-scaffold-cmd": [
        "patch -p1 < patches/my-htaccess.patch"
    ]
},

While trying to track data on draft orders and orders I wanted to use metafields.  This lead me to find out that draft orders cannot have metafields configured. 

These lead me to two options to track data.  

• Note attributes on the order
• A custom mysql database table for my app to track the data.

I've used both depending on the type of data and how store clerks needed to update the data. 

Update a UUID: 

drush config-set "config.name" uuid "a2afbb3b-d34f-42fd-bf0c-593a103aa6f4"

Also how to generate an new UUID:

drush php-eval "echo \Drupal::service('uuid')->generate();"

Notes:

• Remember to back up your database first!
• Check your config: 
  • drush config-get "config.name" uuid

I was brought on board to help recover a website that was possibly exploited by hackers, a Drupal 7 project.  What triggered the investigation?  My client was informed that their customers were receiving spam emails from the website.

After a thorough review of the project's code base and database. I found multiple exploits and backdoors.  All of the issues/exploits were within the Drupal core.  None of the contrib. or custom modules were exploited.