![]() ![]() Then, and only then (once Cog is completely uninstalled) can you safely remove it from composer and pull it from the codebase. Then you need to STOP and completely deploy these changes out through to your production environment. So, you need to make the theme changes (as described above) and delete the configuration. Remember, you cannot uninstall something from Drupal after you’ve removed it from the codebase. Second, you will eventually need to composer remove drupal/cog. So if you are actively managing configuration, I would anticipate that you will need to disable the theme in and delete any of the block config files related to cog. Configuration and Base Theme RemovalĪside from the actual theme changes, the other two things to consider have to do with Drupal configuration and the removal of the theme itself.įirst, on the configuration front, a base theme should be enabled. For me, all of my processing was directory based already, so tossing the additional files in was no big deal (they got processed without additional changes). Just make sure that all of your build tools point at your custom theme (not the base) and ensure that any processing you are running on templates, styles, etc. The final consideration in the theme itself is if you have any build tools that are interacting with Cog directly. Thankfully, the GovCon site has both (simple) visual regression and accessibility testing so once I was relatively certain I had all the right pieces in place, I just had to open the pull request and wait for some confirmation. Essentially, I just copied the files from Cog into my theme and then used Git to review the diffs. For me this ended up being just a few missing template files, which you can see in the pull request. I opted for the second option given that the theme for Govcon is pretty simplistic (and I didn’t want to have to do a ton of restyling). Move the Twig templates and Base styles from Cog that I was missing into my theme Restyle my theme and fix the broken issues Why would I, I hadn’t needed to change them! So, I had two choices: Oops!Īs I scrambled to figure out why, I realized that Cog had some Twig templates and style sheets that I hadn’t explicitly pulled into my theme. My experience in attempting this was a broken website. So, it’s easy enough to just change out the base theme setting in your custom theme from cog to something else (in this case, I would recommend changing it to stable since that is what Cog itself uses). The interesting thing about Cog (and the reason it is so easy to remove) is that it is itself a sub theme of the Drupal core stable theme. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |