Update from 10.2.7 to 10.3.0 claro theme error InvalidArgumentException

Created on 23 June 2024, 3 months ago
Updated 7 August 2024, about 1 month ago

Problem/Motivation

Update from 10.2.7 to 10.3.0 with error message as

The website encountered an unexpected error. Try again later.

InvalidArgumentException: The callable definition provided "[Drupal\claro\ClaroPreRender,tablePositionSticky]" is not a valid callable. in Drupal\Core\Utility\CallableResolver->getCallableFromDefinition() (line 69 of core/lib/Drupal/Core/Utility/CallableResolver.php).
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 432)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 248)
Drupal\Core\Render\Renderer->render(Array) (Line: 475)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 55)
__TwigTemplate_a3164d23252000faf92139dbdc6c86e5->doDisplay(Array, Array) (Line: 360)
Twig\Template->yield(Array) (Line: 335)
Twig\Template->render(Array) (Line: 38)
Twig\TemplateWrapper->render(Array) (Line: 33)
twig_render_template('core/modules/update/templates/update-report.html.twig', Array) (Line: 348)
Drupal\Core\Theme\ThemeManager->render('update_report', Array) (Line: 491)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 248)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 231)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 186)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 53)
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: 57)
Drupal\advban\AdvbanMiddleware->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->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: 741)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

Please help.

Thank you very much.

๐Ÿ’ฌ Support request
Status

Active

Version

10.3 โœจ

Component
Claroย  โ†’

Last updated 1 day ago

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States geles

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @geles
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States geles

    switch to other theme, not claro, the problem was avoided, not resolved.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States geles
  • ๐Ÿ‡จ๐Ÿ‡ฆCanada jerrutl

    I know this isn't specific to the Claro theme, but I applied this change from the Gin theme: https://git.drupalcode.org/project/gin/-/merge_requests/416/diffs

    And it fixed this error. Hope that helps!

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States Kasey_MK

    I think this error went away for me after running database updates and clearing caches.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States geles

    jerrutl

    Thank you so much! The change works!

  • Status changed to Closed: outdated 2 months ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States cilefen
  • Status changed to Needs review 2 months ago
  • ๐Ÿ‡ง๐Ÿ‡ทBrazil astutonet Sao Paulo, SP

    This issue persists in version 10.3.0. Updating the database and clearing the cache didn't help.

    Problem verified in local version. I didn't update the production version so as not to run the risk of having the site down until the issue is fixed.

  • Status changed to Active 2 months ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States cilefen

    There isnโ€™t code to review.

  • ๐Ÿ‡ง๐Ÿ‡ทBrazil astutonet Sao Paulo, SP

    I performed the update test on two projects: an empty website and an older one, with the local version of a website that is in production.

    Actually, in the version with an empty database, just do the update, run "update.php" and clear the cache. The website will continue to operate.

    However, I note that in more complex versions, these measures did not work. After the update, it is not possible to access any page on the website, as it is offline. This should not happen, as not everyone knows how to restore a website.

    However, on the older site, it is still possible to run 'update.php', but it will not even be possible to clear the cache via the user interface, as the site will be down.

  • ๐Ÿ‡ธ๐Ÿ‡ณSenegal diaodiallo

    I had this issue when updating 10.2.6 to 10.3.1 and fixed by just cleaning cache. Thanks to @Kasey_MK for the idea.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States cilefen
Production build 0.71.5 2024