My Drupal is current version 10. OS is Linux Mint.

Installed updates for both Solo and Solo Utilities via Composer..

Errors on updates:

The website encountered an unexpected error. Try again later.

Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "Drupal\solo\Hook\SoloThemeMiscHooks". in Drupal\Component\DependencyInjection\Container->get() (line 159 of core/lib/Drupal/Component/DependencyInjection/Container.php).

I had to use timeshift to recover. Tried this a few times, same result.

Comments

fherman95’s picture

fherman95 commented

fherman95 created an issue.

Broke Drupal 10 not Broke Drupla01

  • flashwebcenter committed 7e79ad32 on 1.0.x-dev 
    Drupal 10 and 11.0-11.2: stop fataling on every page (#3628961)

1.0.35...

  • flashwebcenter committed 7e79ad32 on 1.0.x 
    Drupal 10 and 11.0-11.2: stop fataling on every page (#3628961)

1.0.35...
flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented
Assigned: fherman95 » Unassigned
Status: Active » Fixed

Hello,
Thank you for reporting the issue. Please download the 1.0.36.

Best wishes,
Alaa

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

fherman95’s picture

fherman95 commented

Solo updated OK with 1.0.36.

I haven't tested solo utilities, and won't for a few days as I'm on travel for the next few days.

Thanks for the fix.

fherman95’s picture

fherman95 commented

Looks like solo utilities is also broken:

The website encountered an unexpected error. Try again later.

Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "Drupal\solo_utilities\Hook\SoloUtilitiesHooks". in Drupal\Component\DependencyInjection\Container->get() (line 159 of core/lib/Drupal/Component/DependencyInjection/Container.php).

Solo itself has been fixed.

flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented
Status: Fixed » Active
fherman95’s picture

fherman95 commented

solo utilities 1.0.8 update shows error only when website logged in (administrator level.) Does not show error to un-logged in visitor.

fherman95’s picture

fherman95 commented

solo utilities 1.0.6 works OK

flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented
Status: Active » Needs review

Hello,

Thanks for the detail. 1.0.8 adds a service, and until Drupal rebuilds its caches it still uses the old service list. Please run /update.php (or drush updb && drush cr) and the error goes away. The next release (1.0.9) makes this update safe without that step.

Best wishes,
Alaa

fherman95’s picture

fherman95 commented

I will need to wait for 1.0.9. I have multiple virtual Drupal sites, and my drush configuration has some configuration problems making it cumbersome to use (my problem.)

fherman95’s picture

fherman95 commented

I have upgraded to solo utilities 1.0.9.

Now the color schemes are gone. One site's block structure hosed.

Is it possible to downgrade to 1.0.7, or do I have to use a timeshift snapshot to recover?

fherman95’s picture

fherman95 commented

For the problem site, the theme is stuck in solo administrator mode, not just solo. That's why the block structure is hosed. I don't see a way to get just solo to be the theme when not logged in.

I just rebuilt the problem site with another theme.

flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented
Status: Needs review » Fixed

Hello,

Solo and Solo Utilities never change which theme your site uses, so no downgrade is needed. On that site:

Solo is a front-end theme, not an administration theme. Please do not use it as the admin theme; use Claro or Gin.

1. Go to Appearance (/admin/appearance). Set Solo as the "Default theme", and at the bottom of the page set
"Administration theme" to Claro or Gin.
2. Clear all caches (/admin/config/development/performance).
3. Check the site in a private browser window.

If it is still wrong, please post a screenshot of the Appearance page.

Best wishes,
Alaa

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

gruberroland’s picture

gruberroland commented

I have the same issue with Drupal 10.6.19 and Solo 1.0.37. The page design is completely broken after cache clear. Looks like no CSS is loaded.
The Apache error log shows:

Uncaught PHP Exception Error: "Class "Drupal\\solo\\SoloIncludes" not found" at /web/themes/contrib/solo/solo.theme line 24

Downgrading to 1.0.36 fixes the issue.

flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented

Hello,

Thank you for the report and the log line. I could not reproduce it: a clean Drupal 10.6.19 site with Solo 1.0.37
as the default theme renders correctly after "Clear all caches", on the first load and the next ones. So something
in your setup is different, and these details will help me find it:

1. Does this file exist on your server?
web/themes/contrib/solo/src/SoloIncludes.php
(1.0.37 added it. If Solo was updated by uploading or copying files, it may be missing.)
2. How did you install or update Solo: Composer, Drush, the Update Manager in the admin UI, or by uploading files?
3. Is Solo itself your default theme, or a sub-theme of Solo? If a sub-theme, what is its machine name?
4. How do you clear the cache: "drush cr", the Performance page, or a deploy script?
5. Does the error happen on every page, or only on the first page after the cache clear? Logged in, anonymous, or both?
6. Your PHP version, and whether OPcache or APCu is enabled (for example opcache.validate_timestamps = 0).
7. Is $settings['class_loader_auto_detect'] set in settings.php, or did you run
"composer dump-autoload" with --classmap-authoritative or --apcu?
8. The full message from Reports > Recent log messages for this error, including the backtrace if there is one.

Until we find it, staying on 1.0.36 is fine.

Best wishes,
Alaa

gruberroland’s picture

gruberroland commented

Hi Alaa,

here it is:

1. Does this file exist on your server?
web/themes/contrib/solo/src/SoloIncludes.php
(1.0.37 added it. If Solo was updated by uploading or copying files, it may be missing.)

yes, it exists

2. How did you install or update Solo: Composer, Drush, the Update Manager in the admin UI, or by uploading files?

installation was done using composer

3. Is Solo itself your default theme, or a sub-theme of Solo? If a sub-theme, what is its machine name?

the theme is Solo itself

4. How do you clear the cache: "drush cr", the Performance page, or a deploy script?

performance page and "drush cr" did not help either

5. Does the error happen on every page, or only on the first page after the cache clear? Logged in, anonymous, or both?

on all pages (including admin pages), both for logged-in and anonymous

6. Your PHP version, and whether OPcache or APCu is enabled (for example opcache.validate_timestamps = 0).

PHP 8.4.26, Opcache enabled, restart of Apache does not help

7. Is $settings['class_loader_auto_detect'] set in settings.php, or did you run
"composer dump-autoload" with --classmap-authoritative or --apcu?

class_loader_auto_detect is not set in settings.xml (commented out)

8. The full message from Reports > Recent log messages for this error, including the backtrace if there is one.

Type php
Date Thursday, October 15, 2026 - 07:27
Location http://localhost/cms/sites/default/files/js/js_8J1uMWPwhd4qYbOz3qi4h0UtG...
Referrer http://localhost/cms/admin/reports
Message Error: Class "Drupal\solo\SoloIncludes" not found in include_once() (line 24 of /usr/share/drupal10/cms/web/themes/contrib/solo/solo.theme).
Severity Error
Hostname 127.0.0.1
Operations
Backtrace

#0 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/Extension/Extension.php(153): include_once()
#1 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/Theme/ThemeInitialization.php(137): Drupal\Core\Extension\Extension->load()
#2 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/Theme/ThemeInitialization.php(74): Drupal\Core\Theme\ThemeInitialization->loadActiveTheme()
#3 /usr/share/drupal10/cms/web/core/modules/system/src/Controller/AssetControllerBase.php(157): Drupal\Core\Theme\ThemeInitialization->initTheme()
#4 [internal function]: Drupal\system\Controller\AssetControllerBase->deliver()
#5 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array()
#6 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/Render/Renderer.php(637): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->{closure:Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber::wrapControllerExecutionInRenderContext():121}()
#7 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(121): Drupal\Core\Render\Renderer->executeInRenderContext()
#8 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext()
#9 /usr/share/drupal10/cms/vendor/symfony/http-kernel/HttpKernel.php(181): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->{closure:Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber::onController():96}()
#10 /usr/share/drupal10/cms/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#11 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/Session.php(53): Symfony\Component\HttpKernel\HttpKernel->handle()
#12 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#13 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/ContentLength.php(28): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#14 /usr/share/drupal10/cms/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(116): Drupal\Core\StackMiddleware\ContentLength->handle()
#15 /usr/share/drupal10/cms/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(90): Drupal\page_cache\StackMiddleware\PageCache->pass()
#16 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle()
#17 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#18 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#19 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle()
#20 /usr/share/drupal10/cms/web/core/lib/Drupal/Core/DrupalKernel.php(741): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#21 /usr/share/drupal10/cms/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#22 {main}

Best regards
Roland

flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented

Hi Roland,

Thank you for the details and the backtrace, they found it. On Drupal 10, the request that builds the CSS/JS files loads solo.theme before Drupal can find Solo's classes, and 1.0.37 used one of those classes there. Drupal 11 and 12 are not affected.

The fix is in the 1.0.x development version: solo.theme loads its include files directly again, as 1.0.36 did. Could you try it on your site?

composer require drupal/solo:1.0.x-dev@dev
drush cr

Then load a few pages, logged in and logged out. If CSS and JS load correctly, please let me know here and I will release it as 1.0.38.

Best wishes,
Alaa

gruberroland’s picture

gruberroland commented

Hi Alaa,

thanks a lot for the fast fix! I can confirm that this change fixes the issue:

https://git.drupalcode.org/project/solo/-/commit/9bbd854a9f4240b97922518...

Best regards
Roland

flashwebcenter’s picture

flashwebcenter
he/him
Primary language English
Location Austin TX
commented

Thank you, 1.0.38 is out.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.