The Theme Switcher module allows you to create theme-switching rules which allow automatic selection of a theme based on Drupal 8 Conditions system.
Project link
https://www.drupal.org/project/theme_switcher
Git instructions
git clone --branch 8.x-1.x https://git.drupalcode.org/project/theme_switcher.git
PAReview checklist
https://pareview.sh/pareview/https-git.drupal.org-project-theme_switcher.git
Comments
Comment #2
amarincolas commentedComment #3
manish34jain commentedHello Amarincolas,
Please run the automated review and check the errors & warnings.
Git errors:
Review of the master branch (commit a934c50):
This automated report was generated with PAReview.sh, your friendly project application review script.
Comment #4
manish34jain commentedComment #5
avpadernoComment #6
amarincolas commentedI have fixed everything: https://pareview.sh/pareview/http-git.drupal.org-project-theme_switcher-...
Tests will be added on next release.
Comment #7
amarincolas commentedComment #8
manish34jain commentedHello Amarincolas,
When i install and add theme switcher rule after that it's showing below errors on log.
Warning: call_user_func() expects parameter 1 to be a valid callback, class 'Drupal\theme_switcher\Form\ThemeSwitcherRuleForm' does not have a method 'exist' in Drupal\Core\Render\Element\MachineName::validateMachineName() (line 267 of core\lib\Drupal\Core\Render\Element\MachineName.php)
Thanks
Comment #9
amarincolas commentedHello @manish34jain,
Thank you for your time.
The warning has been fixed.
Comment #10
KuldeepM commentedHello Amarincolas,
I have tested this module. It is not working with language & webforms conditions. It will set default active theme.
Comment #11
avpadernoThank you for your review. We don't aim to debug the code, but check what users understand in correctly using the Drupal core APIs, writing secure code, and writing code that follows the Drupal coding standards.
Comment #12
vuilThank you for the contribution!
I have not found any security related issues into the code.
Just one small suggestion (which does not come from project security) is always better to use
tryandcatchblocks, and handle possible throws and exceptions.Good job!
Comment #13
amarincolas commentedThank you for your reviews.
@KuldeepM, I have test it with several languages and it works perfectly. Can you give some steps to reproduce? However I have not yet test it with the webform module but I will (It may not make sense with certain conditions like webform).
Thanks.
Comment #14
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.
Comment #15
avpaderno