Twig\Error\LoaderError: Template "@organisms/list/list.twig" is not defined

@ravi-kant
Could you please provide more information on how you installed the CivicTheme: using Composer or manually?

This error usually appears when `components` directory, which is a symlink, cannot be followed by the OS or if the codebase was copied from the archive without preserving links.

Hi @alex.skrypnyk

I tried to reproduce the issue, manually i tried i am getting same error along with 1 more error.

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "civictheme_one_column" plugin does not exist. Valid plugin IDs for Drupal\Core\Layout\LayoutPluginManager are: layout_twocol_section, layout_threecol_section, layout_fourcol_section, layout_onecol, layout_twocol, layout_twocol_bricks, layout_threecol_25_50_25, layout_threecol_33_34_33, layout_builder_blank in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of /var/www/html/diet/vb1020/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

@dineshkumarbollu
could you please provide more steps to reproduce

@alex.skrypnyk

• Installed components module components^3.0@beta with composer
• Installed the civictheme with composer in Drupal 10.2.0.
• Enabled all required modules
• Now enabled and set default to civictheme
• Navigate to home page

I installed the theme manually, installed the missing modules on a clean drupal 10.2.3, turned them on and got a similar error.

For what it's worth, I was doing the same thing and got a similar error (but for @atoms/image/image.twig). Came here to post about it but then noticed that I hadn't done a drush cr since installing the theme and dependencies. That fixed it for me.

I also get this error:

• when I install the site with another theme other than CT
• created a child CT theme
• enabled this child theme
• set as default
• navigate to front page

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.

Closing as community confirmed this is resolved.