Theme "at_tools" missing

In both Adaptivetheme (5.2) ( https://www.drupal.org/project/adaptivetheme → ) and in AT Tool 2.0 ( https://www.drupal.org/project/at_tool → ) there is confusion about reference to "at_tool" and "at_tools" .
In my Rapid PHP 2022 I chose to search for ALL occurrences of "at_tools" to replace them with "at_tool". (YES, a very ugly method, but it worked!)
After first running "Flush all caches" and then update.php, it now seems that the problems are solved for this time.

In fact this issue should be solved in the module https://www.drupal.org/project/at_tool → .

In the module "at_tool", you should should modify the file "at_tool.module" and change the line # 23 from
$variables['#attached']['library'][] = 'at_tools/appearance_settings'; to
$variables['#attached']['library'][] = 'at_tool/appearance_settings';

I know, there are still some other mistakes in the code where the word "at_tools" should be changed to "at_tool" but this solution here is needed for the error mentioned in this issue.

Just as told in #2

I did what in point #2 but I have 2 errors in the referrer ./admin/appearence

User warning: The following theme is missing in the file system: at_tools in Drupal\Core\Extension\ExtensionPathResolver->getPathname() (line 63 of /Users/xstage/Sites/ECA10dev/web/core/lib/Drupal/Core/Extension/ExtensionPathResolver.php)

Deprecated function: dirname(): Passing null to parameter #1 ($path) of type string is deprecated in Drupal\Core\Extension\ExtensionPathResolver->getPath() (line 85 of /Users/xstage/Sites/ECA10dev/web/core/lib/Drupal/Core/Extension/ExtensionPathResolver.php).

And in the list of themes, the Adaptivetheme subtheme has the message telling that I can't install it:
Requires: stable (missing)
This theme requires the at_core base theme to work properly.

Does anyone know how to fix this problem?

I created a patch based on EricVL's comment.

Thanks a lot, it works

As senzaesclusiva Comment #5 I had the same problem solved to change in at_core.info.yml (themes/contrib/adaptivetheme/at_core)

base theme: stable9
dependencies:
  - stable9:stable9

But still after applying #3 EricVL have the error massage, when I click to AT Theme Generator in appearance. In FTP there is no modules/contrib/at_tool/at_theme_generator Form directory:

<em>The website encountered an unexpected error. Try again later.

InvalidArgumentException: Class "\Drupal\at_theme_generator\Form\GeneratorForm" does not exist. in Drupal\Core\DependencyInjection\ClassResolver->getInstanceFromDefinition() (line 24 of core/lib/Drupal/Core/DependencyInjection/ClassResolver.php).

Drupal\Core\Controller\HtmlFormController->getFormObject(Object, '\Drupal\at_theme_generator\Form\GeneratorForm') (Line: 58)
Drupal\Core\Controller\FormController->getContentResult(Object, Object)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 627)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)</em>

Know someone where can be problem?
Thankyou

I am not able to enable stable9. I am using stabel (D8). How can I enable stable9?
at_core is in themes\contrib\adaptivetheme\

Stable (D8) was deprecated module. I uninstaled it.
In core theme folder in stable9.info.yml change hidden: true to hidden: false. Than you can see it in UI apearence. Clear cache.
Do I need to install Stable 9 theme? I dont think so.

Have you change "at_tool" and "at_tools" in another files? Whitch one?

IMHO there are 2 issues here:
- the fact that "at_tools" is not renamed to "at_tool" because the new developers started to make a new module based on "at_tools" and called it "at_tool" but didn't renamed all occurences of "at_tools" and
- the fact that the theme is wronly based on the original D8 theme "stable" and not on the new D10 theme "stable9".
I still had the old (replacement of) the "stable" theme in my configuration when I tested the patch in #6 and it worked nicelly.
The fact that the D10 version of this module should work when it is bases on "stable9" is NOT tested here.
So maybe these 2 issues should be splitted now.
Just my idea
Greetings

Please. What versions of theme, AT tool and drupal are you using?
I have:
AdaptiveTheme - 8.x-5.2
AT Tool 2.0 - 2.0.4
Drupal - 10.2.3
PHP - 8.2.15

@voloda86
I"m using the same versions but I added the replacement of stable too.
composer require "drupal/classy":"^1.0"
This module is dependent on drupal/stable and both modules will be installed. Probably, you don't need classy but this is my situation.
Then you can install drupal/adaptivetheme because this module is dependent on drupal/stable.

So at_tool is dependent on adaptivetheme wich is dependent on stable.

I started a new issue:

https://www.drupal.org/project/at_tool/issues/3424876 →

This is going to be in a new release today, thanks for looking into it.

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