uuid: - value: 09097ac1-03ea-456c-a1bd-49bdc2bb9499 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:36+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: | What problem are we trying to solve? created: - value: '2023-08-03T00:00:00+00:00' changed: - value: '2025-05-11T09:00:36+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/08/03/what-problem-are-we-trying-to-solve langcode: en body: - value: |
The Override Node Options module that I said yesterday is used on 35,000 websites isn't a complicated module.
It doesn't add a lot of features.
It solves a problem by adding additional permissions to Drupal that site administrators can assign to user roles and not need to give a more global permission like "administer nodes".
The problem being solved is allowing users to set node options, like the created date or published status, in a secure way.
If it wasn't solving a problem, it wouldn't be used on 35,000 Drupal websites.
format: full_html processed: |The Override Node Options module that I said yesterday is used on 35,000 websites isn't a complicated module.
It doesn't add a lot of features.
It solves a problem by adding additional permissions to Drupal that site administrators can assign to user roles and not need to give a more global permission like "administer nodes".
The problem being solved is allowing users to set node options, like the created date or published status, in a secure way.
If it wasn't solving a problem, it wouldn't be used on 35,000 Drupal websites.
summary: null field_daily_email_cta: { }