Closed (fixed)
Project:
Bootstrap Storybook
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 May 2020 at 09:49 UTC
Updated:
30 Jul 2020 at 16:44 UTC
Jump to comment: Most recent
Comments
Comment #2
doxigo commentedI cannot reproduce this, but the point is not to use the `bootstrap_storybook` theme itself but the subtheme, did you manage to get it fixed? anyways I will go through it soon
Comment #3
doxigo commentedComment #4
giorgosk@doxigo as I mentioned above the same behaviour can be seen when creating a subtheme with the steps specified on project page
I know that we are supposed to use a custom subtheme but the point was that even before going to the subtheme the main theme has trouble starting ... but it might be just my installation not sure when I can retest this.
Comment #5
doxigo commentedOkay thanks for the update, will try to test this in different environment see if I can come up with the issue
Comment #6
ivansb@drupal.orgI can confirm the problem on D9.0.2
Comment #7
doxigo commented@ivan could you please let me know your environment and the steps you took that caused the issue? so I can trace the problem
Comment #8
ivansb@drupal.orgI got it working.
I think the steps in the Getting Started are a bit misleading since you get the idea that the generated custom theme comes already compiled (you suggest to enable it before compiling it).
While reinstalling everything from scratch I stumbled in a couple of problems:
1)
Installing bootstrap_storybook via composer fails with:
- Can only install one of: drupal/core[8.9.x-dev, 9.0.2].
- Installation request for drupal/core (locked at 9.0.2) -> satisfiable by drupal/core[9.0.2].
Installation failed, reverting ./composer.json to its original content.
2) there is a small bug in
./src/kits/default/includes/page.inc: $result = \Drupal::service('path.alias_manager')->getAliasByPath($current_path);
that should be
path_alias.manager
https://www.drupal.org/project/block_exclude_pages/issues/3126973
Comment #10
doxigo commentedThank you both for the help, there was an issue with components module dependency and its D9 compatibility on the theme which got fixed, also fixed the new `path_alias` issue, credited & commited.
I'll go through the steps on the documentation and will update accordingly as well