Seeing this related issue. The button here is "empty". It needs some sort of label for accessibility.
<nav class="tbm tbm-main tbm-arrows" id="tbm-main" data-breakpoint="1199" aria-label="main navigation" data-initialized="true">
Empty button
<button class="tbm-button" type="button">
What It Means
A button is empty or has no value text.
Why It Matters
When navigating to a button, descriptive text must be presented to screen reader users to indicate the function of the button.
How to Fix It
Place text content within the element or give the element a value attribute.
I'm seeing a couple of related issues with the Megamenu module for Drupal 10.
1. In a dropdown "level 1" submenu, such as:
<span class="tbm-link level-1 no-link tbm-toggle" tabindex="0" aria-expanded="false">
Explore
</span>This is reportedly a misuse of aria attributes, according to WCAG 2.1 AA, SC 4.1.2.
To fix: ARIA attribute is not allowed: aria-expanded="false"
2. The level 1 "list" used in megamenu is missing the "aria-haspopup" attribute:
<li class="tbm-item level-1 tbm-item--has-dropdown" aria-level="1">
This also deals with SC 4.1.2.
To fix: Add aria-haspopup="true" to menu items with dropdowns. Ensure the menu element with aria-haspopup is focusable and can activate the popup.
Hello, is there a way to test this locally? I'm not confident with forking the branch. Is there a .diff file produced in the repo?
If anyone in Slack wants to jump on a huddle with me, I'd be happy to try to contribute to this issue. I just don't know exactly how to contribute. I may be in need of more mentorship.
git@git.drupal.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Hello Randy - I figured out how to get push access above. I also noticed this provided instructions on how to add and fetch. I'm currently attempting to use DrupalForge. When I run this command, it says I don't have access. git fetch drupal-3444906. Also, I didn't get an email from git.drupalcode.org to confirm the account but there was one saying I've been given access to https://git.drupalcode.org/issue/drupal-3444906. I can't click the button there.
I created an issue fork on a random issue. I also can't click on the button "Fork" but I have access. I was able to add and fetch that one. Currently waiting for that one to load into Drupal Forge.
Hello, I'm trying to use this to learn how to fork, merge, contribute. When I go to git.drupalcode.org, the "fork" button is disabled. Is that disabled intentionally? Perhaps because this was meant to be a temporary fork for DrupalCon only?
If you can get devel and devel entity updates installed (I'm having trouble in D11), you can run 'drush entup'. That's what's always worked for me when seeing this.
I was in the wrong codebase, sorry.
Regarding installation, I had no issues. The module is installed. I checked recent logs for anything related to the module. I see this warning:
Schema information for module views_url_alias was missing from the database. You should manually review the module updates and your database to check if any updates have been skipped up to, and including, views_url_alias_update_8000().
This may have been before I updated the database.
I'm seeing a Views UI error. Not sure if it's related.
Error: Call to a member function getPluginDefinition() on null in Drupal\views_ui\ViewListBuilder->getDisplaysList() (line 259 of /app/web/core/modules/views_ui/src/ViewListBuilder.php).
As for the View, I'm following along with your example. I created a view with all content that is Published. I added a relationship to "Content URL Alias". I added an exposed filter using "Contains" for the Alias: URL Alias field. When I put anything in the search input, nothing appears.
@alison Did you look at the views_url_alias table manually? (I don't know how else you would). I'm going to see if I can find a .readme or any documentation on how to use this module.
I have a bad habit of creating issues, then later on I don't remember the context of the issue. I'm looking for the view or what I might have been doing at the time. I'll report back one way or another with an answer.
I found something interesting, however.
It appears that whatever the wildcard represents cannot contain at least a hyphen (-). For example,
If I do this...
From: /depts/voting-and-elections/polling-places/*
To: /county-clerk/voting-and-elections/where-to-vote
This string won't work...
/depts/voting-and-elections/polling-places/precinct-2
But this one will
/depts/voting-and-elections/polling-places/2025 (no hyphen in the wildcard string)
Is this a known issue or something that won't be resolvable? Of course, it would need to be verified. I'm concerned that anything having any valid URL punctuation like hypen - or / backward slash will not be resolvable using wildcards.
I tried MR97. I added as a patch, ran composer and so forth. I tried doing something like this:
From: /county-news/*
To: /news/*
It is not working for me. Is this the correct usage of a wildcard?
richardgaunt → credited rraney → .
I added as a patch, cleared cache, but it's still there. Is this part of the main alpha release?
Pierre will be creating an issue for Civic Theme. I'm not finding any issues with the modules that Civic Theme requires. You can close :)
This appears to be due to a conflict with Civic Theme or one of its dependencies. I don't think it's inherently an issue with this module, but it would take some testing.
rraney@itjlelap31:~/sandboxcms$ lando composer require 'drupal/ui_patterns:^2.0'
./composer.json has been updated
Running composer update drupal/ui_patterns
Loading composer repositories with package information
Updating dependencies
Lock file operations: 3 installs, 0 updates, 0 removals
- Locking drupal/ui_patterns (2.0.5)
- Locking justinrainbow/json-schema (6.4.2)
- Locking marc-mabe/php-enum (v4.7.1)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 3 installs, 0 updates, 0 removals
- Downloading marc-mabe/php-enum (v4.7.1)
- Downloading justinrainbow/json-schema (6.4.2)
- Downloading drupal/ui_patterns (2.0.5)
- Installing marc-mabe/php-enum (v4.7.1): Extracting archive
- Installing justinrainbow/json-schema (6.4.2): Extracting archive
- Installing drupal/ui_patterns (2.0.5): Extracting archive
Generating optimized autoload files
55 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
I just confirmed doing the composer require command for this module, then clearing cache caused this issue. Prior to this step, the site was working fine.
Also prior to this step, I installed the Civic Theme. Perhaps there is a conflict.
---
okay thank you
I tried removing this module using 'composer remove'. I cleared cache and the error is still there, so now I have some doubt about this module being the cause. It happened right after I required it, so I'm at a loss.
Thank you. I searched for field_group in issues, but didn't see that one. I guess we can close as duplicate.
Is this the version with the change? https://www.drupal.org/project/ui_suite_uswds/releases/4.0.x-dev →
I have the patch installed. I'm now seeing this when I run composer update or install.
drupal/block_class has modified files:
M src/Service/BlockClassHelperService.php
Discard changes [y,n,v,d,s,?]? n
Install of symfony/string failed
Install of symfony/polyfill-php81 failed
Install of symfony/serializer failed
Install of symfony/routing failed
Install of symfony/http-foundation failed
Install of symfony/mime failed
Install of symfony/mailer failed
Install of symfony/var-dumper failed
Install of laminas/laminas-escaper failed
Install of laminas/laminas-feed failed
To reproduce (as this was closed due to inability to reproduce):
Drupal 10
Create a block that holds a webform
Install Layout Paragraphs
Create a paragraph that can hold a block
On a page using Layout paragraphs, add a block paragraph which holds the webform block
Save the page
This should reproduce the issue
I have this issue exactly as Rob has laid it out. I use Layout Paragraphs. The issue happens when I have a block paragraph that holds a webform.
There are at least two big issues with Gin that have forced me to switch to Claro. I wish the best parts of both would merge into a dream theme :). This may be a Gin issue and not Layout Paragraphs, as you mentioned.
Thanks, we can close if that's the recommendation. It seems like we'd be making this change only to please security scans. The reason they suggest no autocomplete seems to do more with credit card fields, etc. Since browsers ignore password, it seems pointless to change this field. Thanks
I just found this, so I'll test it out
https://www.drupal.org/project/no_autocomplete →
Added a related issue because I think autocomplete should be set to "off" for security reasons, or at least the option to change it somewhere.
https://www.drupal.org/project/drupal/issues/3522461#comment-16094484
✨
User login form password field not set with autocomplete attribute
Active
What's wrong with the current value is explained. It is a potential security risk as outlined. I dropped a bunch of verbiage from a security audit. I'm asking for the ability to change this attribute to "off" for security reasons, one way or another. If it's not going to be agreed upon as an implementation, then perhaps you could close it with a suggestion on how I might hack around this. Thanks
I'm still seeing this issue in Drupal 10 with Gin Admin Theme 8.x-3.0. I will attach screenshots if I can. If I open DevTools, this is the style that's causing it.
table.sticky-header thead {
position: sticky;
z-index: 500;
top: var(--drupal-displace-offset-top, 0);
}
This is a core CSS setting in sticky-header.module.css. Should I open or try to find an issue in Core?
/core/misc/components/sticky-header.module.css?sugbrg
If I uncheck the position setting, it fixes the issue.
I have some form of this issue on Windows Server with Drupal 10 and Bootstrap Barrio theme. I wasn't having issues with 777. The errors have to do with the "system" not being able to make a directory in the sites/default/files/php/twig folder and also renaming a file. The patch works. I'm curious if a remedy will be made in SDC, Bootstrap theme or core.
I guess the error is a duplicate but not what's triggering it.
I'm seeing this every time I save the Block Layout page.
The website encountered an unexpected error. Try again later.
TypeError: array_merge(): Argument #1 must be of type array, string given in array_merge() (line 202 of modules/contrib/block_class/src/Service/BlockClassHelperService.php).
It's going to be hard to troubleshoot because I never had the issue locally. Only in internet staging and production. I can confirm this when I get an opportunity, but local worked fine for me before I used the patch. I'm not if that's because I have aggregation only in production, or what.
I have never used git bisect. I would have to learn how. It looks a bit involved. I have so many commits, I don't know how I would find the one that caused this issue.
This appears to have caused issues with my build, similar to the post above, but with custom.css.
https://www.drupal.org/project/webform/issues/3503436
🐛
Webform custom CSS not applied unless ALL anonymous traffic allowed to create submissions
Active
The issue you linked definitely seems related and the change made appears to be this. https://www.drupal.org/i/3389539 →
I may try the patch from the other issue and downgrading to 6.2.2. I'm wondering what changed related to this after 6.2.2.
I tried to add more information about CDN, but I don't know exactly what's meant by "setup". I'll go ahead and provide the header info.
Server hostname
www.oursite.gov
Remote Client
Remote address
198.248.x.x
Remote hostname
N/A
Remote country code
🇺🇸 US
User agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0
Request
Timestamp
Jan 30, 12:00:57 PM CST
Method
GET
Scheme
https
Server name
www.oursite.gov
Protocol
HTTP/3
Path
/webform/css/community_partner_budget_request/custom.css
URI
/webform/css/community_partner_budget_request/custom.css
Full URL
https://www.oursite.gov/webform/css/community_partner_budget_request/cus...
TLS protocol
TLSv1.3
TLS cipher
TLS_AES_256_GCM_SHA384
Request Headers
Accept
text/css, */*;q=0.1
Accept-Encoding
br
Accept-Language
en-US, en;q=0.9
Asn
2495
Cdn-Loop
Fastly, Fastly, Fastly
Client-Ja3
dd3b06fc126532d749914464b162dea5
Country-Code
US
Fastly-Client
1
Fastly-Client-Ip
198.248.172.2
Fastly-Ff
shtNug6M3Q8p1zl8HcxqZvd1TrCuVsvNDTlUiVeUfsI=!MCI!cache-mci680067-MCI, shtNug6M3Q8p1zl8HcxqZvd1TrCuVsvNDTlUiVeUfsI=!MCI!cache-mci680025-MCI, shtNug6M3Q8p1zl8HcxqZvd1TrCuVsvNDTlUiVeUfsI=!IAD!cache-iad-kiad7000037-IAD
Fastly-Orig-Accept-Encoding
br
Fastly-Request-Id
ec4425ce594349e5197c79a7
Fastly-Ssl
1
Host
www.oursite.gov
Priority
u=0
Proxy-Type
?
Proxy_desc
?
Referer
https://www.oursite.gov/webform/community_partner_budget_request/test
Sec-Ch-Ua
"Not A(Brand";v="8", "Chromium";v="132", "Microsoft Edge";v="132"
Sec-Ch-Ua-Mobile
?0
Sec-Ch-Ua-Platform
"Windows"
Sec-Fetch-Dest
style
Sec-Fetch-Mode
no-cors
Sec-Fetch-Site
same-origin
True-Client-Ip
198.248.x.x
User-Agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0
X-Forwarded-For
198.248.x.x, 140.248.x.x
X-Forwarded-Host
www.oursite.gov, www.oursite.gov
X-Forwarded-Server
cache-mci680067-MCI, cache-iad-kiad7000037-IAD
X-Original-Url
/webform/css/community_partner_budget_request/custom.css?sqwxhn&sqwxhn
X-Pass
redacted
X-Sigsci-Edgemodule
vcl 2.7.0
X-Sigsci-Requestid
72ddd02f096749259b3b00000000002e
X-Static-Asset
1
X-Timer
S1738260057.095938, VS0, VS0
X-Varnish
4228963453
X-Waf-Block
0
X-Waf-Block-Id
0
Response
Agent response
200
HTTP response code
403
HTTP response size
67.2KB
Total duration
34 ms
Response Headers
Accept-Ranges
bytes
Cache-Control
must-revalidate, no-cache, private
Connection
keep-alive
Content-Language
en
Content-Length
68790
Content-Type
text/html; charset=UTF-8
Date
Thu, 30 Jan 2025 18:00:57 GMT
Expires
Sun, 19 Nov 1978 05:00:00 GMT
Fastly-Debug-Digest
086eaeafac7087f2cf4efc1ddc4f03eae76eed9253be9387627d7ca797f3158f
Fastly-Debug-Path
(D cache-iad-kiad7000121-IAD 1738260057) (F cache-iad-kiad7000121-IAD 1738260057)
Fastly-Debug-Ttl
(M cache-iad-kiad7000121-IAD - - -)
Fastly-Drupal-Html
YES
Surrogate-Control
must-revalidate, no-cache, private, stale-while-revalidate=14400, stale-if-error=604800
Surrogate-Key
redacted
Via
1.1 varnish
X-Cache
MISS
X-Cache-Hits
0
X-Content-Type-Options
nosniff
X-Drupal-Cache
HIT
X-Frame-Options
SAMEORIGIN
X-Lagoon
amazeeio-us2>ingress-nginx>oursite-main:nginx>nginx-54567467c8-vvthv
X-Served-By
cache-iad-kiad7000121-IAD
X-Timer
S1738260057.095938,VS0,VS0,VS0,VE33
Signals
Allowed Request
Detector: 66840a0f7953bb438c16672f - View rule
HTTP 403 403
Detector: HTTPErrorRule
rraney → created an issue.
I'm having this issue. The duplicate Media items keep coming back. I can temporarily fix by clearing cache. I changed the Media Library view name from "Media" to "Media Library". If it happens again, I am guessing this view might be added to the content menu as "Media Library".
Understandable! I just wanted some clarification because it said it was merged and fixed. I am not as knowledgeable as I should be about the whole process.
Am I correct that a patch is currently the only solution to this issue? Is there a maintainer following this?
That sounds very familiar. I may have even had to do an entity update using Devel.
Hello, I have Drupal CMS (D11) installed locally. I was hoping to fire up this theme/design system. I've attempted to apply the patch by installing cweagans, adding to composer.json and running composer install.
I tried running this command:
drush ev "require_once dirname(\Drupal::getContainer()->get('theme_handler')->rebuildThemeData()['civictheme']->getPathname()) . '/theme-settings.provision.inc'; civictheme_enable_modules();"
It's giving me a long list of errors. Long story short, is the theme ready for Drupal CMS?
I'm sorry I can't offer a solution, but I'm almost certain I had an issue with a different module that interacts with webform. It appears this is what was found by @flyke. I didn't want to ghost this issue, but I think I did some updates on modules and the issue just went away.
I just applied the diff as a patch in my system. Did composer install/update --lock. I cleared cache. I'm still seeing the message reported here.
Will there be a resolution for this? I'm seeing this issue
Me too. Following
This worked. All I needed to do was get the correct module installed. I couldn't tell which version it was because it doesn't tell me in Drupal. Sorry and thanks.
I just realized there is a dropdown where you have to select to group, so I guess the dev. version DOES work. Please let me know when this will be released.
I would say this is not fixed.
I have the dev. version installed locally and I'm not getting the grouping option. I'll upload screenshots.
I just realized that the dev. version doesn't have the grouping that I need, as I went through in the related issue. #3464548: Bootstrap Tabs not aggregating or grouping. There currently doesn't seem to be a way around this.
OK just a little reset here.
Locally, this version didn't work for me: composer require drupal/views_bootstrap:5.5.x-dev#4c6057e3b8c47ea88d8fd0427141fbf1463b9ed8
I reinstalled the dev. version: composer require 'drupal/views_bootstrap:5.5.x-dev@dev'
Locally, I can see settings but as I stated, I turned off CSS aggregation. I turned ON CSS AdvAgg, cleared cache and I can still access settings, so maybe there isn't a conflict.
I am pushing out the module update again to staging to see if it's working there.
I turned OFF advanced CSS and JS aggregation and now I can access settings for Accordion and Tabs in my local environment.
I absolutely have to have this turned on in production, however, because of caching issues with my CDN.
Any idea why there would be a conflict with the advagg module?
AI insights for this error in console:
Explanation
The error message indicates a problem within the Views Bootstrap module (specifically the ViewsBootstrapAccordion style) on your Drupal website. Let's break down the key parts:
TypeError: Cannot access offset of type string on string: This is the core issue. PHP is trying to treat a string like an array and access a specific element (offset) of it. Strings in PHP are not arrays; they are sequences of characters. This indicates a coding error within the ViewsBootstrapAccordion style plugin.
in Drupal\\views_bootstrap\\Plugin\\views\\style\\ViewsBootstrapAccordion->buildOptionsForm() (line 79 ...): This pinpoints the location of the error within the module's code. Line 79 of ViewsBootstrapAccordion.php contains the faulty code.
The website encountered an unexpected error. Try again later.: This is Drupal's generic error message, which is not helpful for debugging.
HTTP Result Code: 500: This is an Internal Server Error, meaning the server encountered a problem while processing the request. The specific problem is the PHP error mentioned above.
Path: /admin/structure/views/ajax/display/document_block_view/block_43/style_options: This is crucial. It shows the URL where the error occurred. This path suggests you were likely configuring a View, specifically a "document_block_view" (View ID) with block ID "43", and interacting with the style options for the Views Bootstrap Accordion style.
How to Fix It:
Update Views Bootstrap: The most likely solution is that the module is outdated and contains a bug. Go to /admin/modules in your Drupal site, find the Views Bootstrap module, and check for updates. Update it to the latest stable version.
Check for Conflicting Modules: Other modules might interfere with Views Bootstrap. Try temporarily disabling other recently installed modules, especially those that modify Views or forms, to see if the problem resolves.
Examine the Code (Advanced): If updating and disabling modules don't work, you'll need to examine the code directly.
Find the file: Locate modules/contrib/views_bootstrap/src/Plugin/views/style/ViewsBootstrapAccordion.php on your server.
Inspect line 79: Carefully review line 79. You'll likely find a line of code that tries to access a specific part of a string using array-like syntax (e.g., $myString[0], $myString['key']).
Identify the variable: Determine which variable is causing the issue. The error message should provide hints.
Correct the code: Fix the code to treat the variable correctly as a string, possibly using string functions like strpos(), substr(), or explode() depending on what you intend to achieve. If you're unsure, consult the module's documentation or seek help in Drupal forums.
Clear caches: After making changes, clear all Drupal caches (both the page cache and the render cache).
Enable Debug Mode (if safe): If you have access to PHP's error logging, you may want to enable debugging in Drupal (or configure your webserver to show PHP errors) for more detailed error messages. Be extremely cautious when enabling debug mode on a production site as it can expose sensitive information.
Drupal Forums/Issue Queue: Search the Drupal.org project page for the Views Bootstrap module for similar issues or file a new bug report if you can't find a solution. Providing details from the error message and your setup will help others assist you.
Important Considerations:
Backup: Before making any code changes, always create a backup of your website files and database.
Permissions: Ensure you have the necessary file permissions to edit the module files.
Testing: Test changes thoroughly on a development or staging environment before applying them to your production site.
By systematically working through these steps, you should be able to identify and resolve the error. The most likely solution, however, is to simply update the Views Bootstrap module.
I just installed the newest version of this module and I'm still having issues with getting to Accordion and Tabs settings.
I got a lot of Ajax errors while doing this last test. Is it possible this is an Ajax issue? Does the popup rely on Ajax?
POST https://www.dgcoks.gov/admin/structure/views/ajax/display/document_block... 500 (Internal Server Error)
An AJAX HTTP error occurred.\nHTTP Result Code: 500\nDebugging information follows.\nPath: /admin/structure/views/ajax/display/document_block_view/block_43/style\nStatusText: error\nResponseText: The website encountered an unexpected error. Try again later.TypeError: Cannot access offset of type string on string in Drupal\\views_bootstrap\\Plugin\\views\\style\\ViewsBootstrapAccordion->buildOptionsForm() (line 79 of modules/contrib/views_bootstrap/src/Plugin/views/style/ViewsBootstrapAccordion.php).
I actually installed an older version of the module which was working for me. I'm still seeing the issue in my dev. environment so I imagine there is some sort of conflict. Can anyone think of a starting point for determining what might be causing a conflict, if that's what this is?
Barrio Bootstrap 5 - 5.5.17
Bootstrap 5.1.3
In order to get the tabs working how I need them to work with grouping, which release should I be using? I thought I would try an actual release if it's been resolved.
I corrected the Drupal version to 10.3.10.
Here is the Backtrace from an error
TypeError: Drupal\Core\Cache\CacheableMetadata::createFromRenderArray(): Argument #1 ($build) must be of type array, null given, called in /app/web/modules/contrib/viewsreference/src/Plugin/Field/FieldFormatter/ViewsReferenceFieldFormatter.php on line 165 in Drupal\Core\Cache\CacheableMetadata::createFromRenderArray() (line 149 of /app/web/core/lib/Drupal/Core/Cache/CacheableMetadata.php).
#0 /app/web/modules/contrib/viewsreference/src/Plugin/Field/FieldFormatter/ViewsReferenceFieldFormatter.php(165): Drupal\Core\Cache\CacheableMetadata::createFromRenderArray()
#1 /app/web/core/lib/Drupal/Core/Field/FormatterBase.php(91): Drupal\viewsreference\Plugin\Field\FieldFormatter\ViewsReferenceFieldFormatter->viewElements()
#2 /app/web/core/lib/Drupal/Core/Entity/Entity/EntityViewDisplay.php(268): Drupal\Core\Field\FormatterBase->view()
#3 /app/web/core/modules/layout_builder/src/Entity/LayoutBuilderEntityViewDisplay.php(282): Drupal\Core\Entity\Entity\EntityViewDisplay->buildMultiple()
#4 /app/web/core/lib/Drupal/Core/Entity/EntityViewBuilder.php(340): Drupal\layout_builder\Entity\LayoutBuilderEntityViewDisplay->buildMultiple()
#5 /app/web/core/lib/Drupal/Core/Entity/EntityViewBuilder.php(282): Drupal\Core\Entity\EntityViewBuilder->buildComponents()
#6 /app/web/modules/contrib/paragraphs/src/ParagraphViewBuilder.php(19): Drupal\Core\Entity\EntityViewBuilder->buildMultiple()
#7 /app/web/core/lib/Drupal/Core/Entity/EntityViewBuilder.php(239): Drupal\paragraphs\ParagraphViewBuilder->buildMultiple()
#8 [internal function]: Drupal\Core\Entity\EntityViewBuilder->build()
#9 /app/web/core/lib/Drupal/Core/Security/DoTrustedCallbackTrait.php(113): call_user_func_array()
#10 /app/web/core/lib/Drupal/Core/Render/Renderer.php(870): Drupal\Core\Render\Renderer->doTrustedCallback()
#11 /app/web/core/lib/Drupal/Core/Render/Renderer.php(432): Drupal\Core\Render\Renderer->doCallback()
#12 /app/web/core/lib/Drupal/Core/Render/Renderer.php(504): Drupal\Core\Render\Renderer->doRender()
#13 /app/web/core/lib/Drupal/Core/Render/Renderer.php(248): Drupal\Core\Render\Renderer->doRender()
#14 /app/web/core/lib/Drupal/Core/Template/TwigExtension.php(484): Drupal\Core\Render\Renderer->render()
#15 /app/web/sites/default/files/php/twig/675ca5b60d0c5_bootstrap-columns-2.html._rLtqgDQWh_BfgfmV3oknlQNTs/qiPqTkk_NA5fkVNZ2q-9OQ2Hh5nrR0-NrgWCsjLyA1w.php(71): Drupal\Core\Template\TwigExtension->escapeFilter()
#16 /app/vendor/twig/twig/src/Template.php(393): __TwigTemplate_f7b3c47eb2d3fd5a36d693fee41afb15->doDisplay()
#17 /app/vendor/twig/twig/src/Template.php(349): Twig\Template->yield()
#18 /app/vendor/twig/twig/src/Template.php(364): Twig\Template->display()
#19 /app/vendor/twig/twig/src/TemplateWrapper.php(35): Twig\Template->render()
#20 /app/web/core/themes/engines/twig/twig.engine(33): Twig\TemplateWrapper->render()
#21 /app/web/core/lib/Drupal/Core/Theme/ThemeManager.php(348): twig_render_template()
#22 /app/web/core/lib/Drupal/Core/Render/Renderer.php(491): Drupal\Core\Theme\ThemeManager->render()
#23 /app/web/core/lib/Drupal/Core/Render/Renderer.php(504): Drupal\Core\Render\Renderer->doRender()
#24 /app/web/core/lib/Drupal/Core/Render/Renderer.php(248): Drupal\Core\Render\Renderer->doRender()
#25 /app/web/core/lib/Drupal/Core/Template/TwigExtension.php(484): Drupal\Core\Render\Renderer->render()
#26 /app/web/sites/default/files/php/twig/675ca5b60d0c5_paragraph--mbp-layout.htm_9QWw_u5V_OP1SvySuCq8rC89g/RpSUElcYpBpLWonnnjln_Z48uKZ8FXCpeQR0YcNrkzk.php(97): Drupal\Core\Template\TwigExtension->escapeFilter()
#27 /app/vendor/twig/twig/src/Template.php(437): __TwigTemplate_b68d5bdc73e23b3b601d345f37639ad8->block_content()
#28 /app/web/sites/default/files/php/twig/675ca5b60d0c5_paragraph--mbp-layout.htm_9QWw_u5V_OP1SvySuCq8rC89g/RpSUElcYpBpLWonnnjln_Z48uKZ8FXCpeQR0YcNrkzk.php(80): Twig\Template->yieldBlock()
#29 /app/vendor/twig/twig/src/Template.php(437): __TwigTemplate_b68d5bdc73e23b3b601d345f37639ad8->block_paragraph()
#30 /app/web/sites/default/files/php/twig/675ca5b60d0c5_paragraph--mbp-layout.htm_9QWw_u5V_OP1SvySuCq8rC89g/RpSUElcYpBpLWonnnjln_Z48uKZ8FXCpeQR0YcNrkzk.php(51): Twig\Template->yieldBlock()
#31 /app/vendor/twig/twig/src/Template.php(393): __TwigTemplate_b68d5bdc73e23b3b601d345f37639ad8->doDisplay()
#32 /app/vendor/twig/twig/src/Template.php(349): Twig\Template->yield()
#33 /app/vendor/twig/twig/src/Template.php(364): Twig\Template->display()
#34 /app/vendor/twig/twig/src/TemplateWrapper.php(35): Twig\Template->render()
#35 /app/web/core/themes/engines/twig/twig.engine(33): Twig\TemplateWrapper->render()
#36 /app/web/core/lib/Drupal/Core/Theme/ThemeManager.php(348): twig_render_template()
#37 /app/web/core/lib/Drupal/Core/Render/Renderer.php(491): Drupal\Core\Theme\ThemeManager->render()
#38 /app/web/core/lib/Drupal/Core/Render/Renderer.php(248): Drupal\Core\Render\Renderer->doRender()
#39 /app/web/core/lib/Drupal/Core/Template/TwigExtension.php(484): Drupal\Core\Render\Renderer->render()
#40 /app/web/sites/default/files/php/twig/675ca5b60d0c5_field.html.twig_Zu2PxDrCRklxz1XOlrxTqfXA_/7VTjMeS8Fn28on20voWgc8ELROj15vigmV6xnPj_cRw.php(72): Drupal\Core\Template\TwigExtension->escapeFilter()
#41 /app/vendor/twig/twig/src/Template.php(393): __TwigTemplate_461cae6846b1c62afeb9e51b1d7a31c6->doDisplay()
#42 /app/vendor/twig/twig/src/Template.php(349): Twig\Template->yield()
#43 /app/vendor/twig/twig/src/Template.php(364): Twig\Template->display()
#44 /app/vendor/twig/twig/src/TemplateWrapper.php(35): Twig\Template->render()
#45 /app/web/core/themes/engines/twig/twig.engine(33): Twig\TemplateWrapper->render()
#46 /app/web/core/lib/Drupal/Core/Theme/ThemeManager.php(348): twig_render_template()
#47 /app/web/core/lib/Drupal/Core/Render/Renderer.php(491): Drupal\Core\Theme\ThemeManager->render()
#48 /app/web/core/lib/Drupal/Core/Render/Renderer.php(504): Drupal\Core\Render\Renderer->doRender()
#49 /app/web/core/lib/Drupal/Core/Render/Renderer.php(248): Drupal\Core\Render\Renderer->doRender()
#50 /app/web/core/lib/Drupal/Core/Template/TwigExtension.php(484): Drupal\Core\Render\Renderer->render()
#51 /app/web/sites/default/files/php/twig/675ca5b60d0c5_node.html.twig_Ji9iOUzYeAsy0_AAJ2UqrO2GS/hIfLsAuSfHnhniH9Uqcp_2YHY3dG0edFoFCQfocaTik.php(112): Drupal\Core\Template\TwigExtension->escapeFilter()
#52 /app/vendor/twig/twig/src/Template.php(393): __TwigTemplate_64bb0a9ece40e4d9ca4347478fc83295->doDisplay()
#53 /app/vendor/twig/twig/src/Template.php(349): Twig\Template->yield()
#54 /app/vendor/twig/twig/src/Template.php(364): Twig\Template->display()
#55 /app/vendor/twig/twig/src/TemplateWrapper.php(35): Twig\Template->render()
#56 /app/web/core/themes/engines/twig/twig.engine(33): Twig\TemplateWrapper->render()
#57 /app/web/core/lib/Drupal/Core/Theme/ThemeManager.php(348): twig_render_template()
#58 /app/web/core/lib/Drupal/Core/Render/Renderer.php(491): Drupal\Core\Theme\ThemeManager->render()
#59 /app/web/core/lib/Drupal/Core/Render/Renderer.php(248): Drupal\Core\Render\Renderer->doRender()
#60 /app/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(238): Drupal\Core\Render\Renderer->render()
#61 /app/web/core/lib/Drupal/Core/Render/Renderer.php(638): Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}()
#62 /app/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(231): Drupal\Core\Render\Renderer->executeInRenderContext()
#63 /app/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(128): Drupal\Core\Render\MainContent\HtmlRenderer->prepare()
#64 /app/web/core/lib/Drupal/Core/EventSubscriber/MainContentViewSubscriber.php(90): Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse()
#65 [internal function]: Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray()
#66 /app/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(111): call_user_func()
#67 /app/vendor/symfony/http-kernel/HttpKernel.php(186): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch()
#68 /app/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#69 /app/web/core/lib/Drupal/Core/StackMiddleware/Session.php(53): Symfony\Component\HttpKernel\HttpKernel->handle()
#70 /app/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#71 /app/web/core/lib/Drupal/Core/StackMiddleware/ContentLength.php(28): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#72 /app/web/core/modules/big_pipe/src/StackMiddleware/ContentLength.php(32): Drupal\Core\StackMiddleware\ContentLength->handle()
#73 /app/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\big_pipe\StackMiddleware\ContentLength->handle()
#74 /app/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#75 /app/web/core/modules/ban/src/BanMiddleware.php(50): Drupal\page_cache\StackMiddleware\PageCache->handle()
#76 /app/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\ban\BanMiddleware->handle()
#77 /app/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#78 /app/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#79 /app/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle()
#80 /app/web/core/lib/Drupal/Core/DrupalKernel.php(741): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#81 /app/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#82 {main}
Which version should I be using in order to get the functionality in the related issue?
I added a related issue. It seems I was advised to use the dev. version. The issue I've shared was supposed to be resolved. It may have been but I'm unable to access Settings for Bootstrap Tabs in this version (apparently it's dev).
I'm taking the drastic approach of altering the menu-columns.twig file. I changed the class manually on line 13 and it resolves my issue temporarily until there's another update. It would be nice for the maintainers to take this into consideration.
I am having this same issue. I can't seem to find a good template to change the classes. I also have menus that should not have the flex-row class and the update broke my menus.
OK thanks. I guess I need to look into running it more often.
I'm actually having a problem with the scheduled import and cron. When I schedule the feed then run cron, it is incomplete. When I run the feed manually, it takes a lot longer but it's complete.
Any idea why the cron import isn't doing a complete feed import?
I added the diff as a composer patch. I installed and ran a data view export. I did not get the error. This appears to be working. Thanks