thisisalistairsaccount → created an issue. See original summary → .
Updated references from Drupal 9 to Drupal 10 - some of the search engines and AI tools were using this as a reference to suggest Drupal 9 was still supported
thisisalistairsaccount → created an issue.
thisisalistairsaccount → created an issue.
thisisalistairsaccount → created an issue.
thisisalistairsaccount → created an issue.
Confirming that the issue is resolved as described in #10 and #12 that clearing the cache, such as drush cr after enabling the theme resolves the issue.
This issue occurs and clearing the cache works in both the base and any child theme resolves the issue.
thisisalistairsaccount → created an issue.
Hoping if things are all good here that we could get this into a future release for the module? This would be beneficial for some people we're working with and would love to see it included :)
Thanks @ressa it's very much appreciated and will help us make difference
Moving this to the Project ownership queue for hopefully progressing ownership with Security.txt - https://www.drupal.org/project/securitytxt →
Moving this to the Project ownership queue for hopefully progressing ownership with Security.txt - https://www.drupal.org/project/securitytxt →
Moving this to the Project ownership queue for hopefully progressing ownership with Custom Permissions - https://www.drupal.org/project/config_perms →
The content under "Install Cypress in your project" doesn't necessarily open as clearly as it could be. It currently reads as: "It is recommended to install Cypress in a sub-folder, since a lot of files and folders will be generated." but only later down the steps indicates it should be a subfolder of a site you are working on.
Proposing the changes to the section reflect:
Install Cypress in your project
It is recommended to install Cypress in a sub-folder from the root of your Drupal project, since a lot of files and folders will be generated. In this example the folder is called "test", but you can call it anything. It is assumed that all commands are run after creating and entering the test folder:
$ mkdir test
$ cd test
Run the following commands in your created folder to initialize a Node project package.json file with default values, install Cypress as a dependency, and open Cypress.
Under heading 'Create an .info.yml file' there was a previous comment indicating a change to infer theme's rather than themes. I'm proposing a further change as in most instances you would being with making a folder for the theme, followed by creating the info file:
Create a folder for your theme in the root of your /themes folder. The folder name is the machine name, and the info file name is machine_name.info.yml. Create the .info.yml file within your theme folder. For the rest of this page, we'll create a theme whose human-readable name is "Fluffiness" and machine name is "fluffiness", so the folder is named "fluffiness/" and the .info.yml file is named "fluffiness/fluffiness.info.yml". If the file is present with the minimum required properties (name, type, base theme and core/core_version_requirement) your theme will be visible on your website at Manage > Appearance (http://example.com/admin/appearance).
Looks as though this now needs to be moved to the Project Ownership queue as per step 6 at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →
My account currently doesn't have access to update this issue but I'd like to get this progressed. Custom Permissions is an important component that we use on GovCMS sites and additional maintainers and the ability to progress this module would be great :)
Looks as though this now needs to be moved to the Project Ownership queue as per step 6 at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →
My account currently doesn't have access to update this issue but I'd like to get this progressed. Security.txt is an important component that we use on GovCMS sites and additional maintainers and the ability to progress this module would be great :)
Looks as though this now needs to be moved to the Project Ownership queue as per step 6 at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →
My account currently doesn't have access to update this issue but I'd like to get this progressed. Security.txt is an important component that we use on GovCMS sites and additional maintainers and the ability to progress this module would be great :)