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
Cron updated the data. The feeds filter in Logs shows updates at the same time as cron. I think it's working :)
It was locked. I'm unlocking, then importing in background. After this, I'll try a cron run. Thanks for your help.
Logs show that feeds_cron() and feeds_log_cron() ran, but no sign of any changes to the entity fields that are imported.
I found the link above
https://git.drupalcode.org/project/feeds/-/merge_requests/203.diff
I applied the patch and there was no error. I cleared cache. I ran cron manually.
The errors are gone in Recent Logs. That part is resolved.
If I filter logs by "Feeds" it doesn't show that the feed was imported just now. While the SQL error was resolved, it still apparently didn't import.
I figured out to get a patch from your branch but I'm having trouble getting the patch applied.
Could not apply patch! Skipping. The error was: Cannot apply patch https://git.drupalcode.org/issue/feeds-3482189/-/commit/b0c52a15e36251cf...
Here's my patch:
"drupal/feeds": {
"Issue 3482189": "https://git.drupalcode.org/issue/feeds-3482189/-/commit/b0c52a15e36251cf..."
}
Full output in CLI
patch "-p1" --no-backup-if-mismatch -d "E:\wwwroot\zzz/web/modules/contrib/feeds" < "C:\Users\admin\AppData\Local\Temp\9/67167e57ec37b.patch"
patching file src/Result/HttpFetcherResult.php
patching file tests/src/Unit/Result/HttpFetcherResultTest.php
Hunk #1 FAILED at 7.
1 out of 2 hunks FAILED -- saving rejects to file tests/src/Unit/Result/HttpFetcherResultTest.php.rejpatch "-p0" --no-backup-if-mismatch -d "E:\wwwroot\zzz/web/modules/contrib/feeds" < "C:\Users\admin\AppData\Local\Temp\9/67167e57ec37b.patch"
can't find file to patch at input line 16
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From b0c52a15e36251cfa1c3529ee1d8a2bd2a78f177 Mon Sep 17 00:00:00 2001
|From: znerol <46208-znerol@users.noreply.drupalcode.org>
|Date: Mon, 14 Oct 2024 14:08:50 +0000
|Subject: [PATCH] Issue #3480545 by znerol: Fixed PHP Warning: unlink(): No
| such file or directory in HttpFetcherResult::cleanUp().
|
|---
| src/Result/HttpFetcherResult.php | 2 +-
| tests/src/Unit/Result/HttpFetcherResultTest.php | 2 ++
| 2 files changed, 3 insertions(+), 1 deletion(-)
|
|diff --git a/src/Result/HttpFetcherResult.php b/src/Result/HttpFetcherResult.php
|index fdd803ae..f9966d5c 100644
|--- a/src/Result/HttpFetcherResult.php
|+++ b/src/Result/HttpFetcherResult.php
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 29
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/tests/src/Unit/Result/HttpFetcherResultTest.php b/tests/src/Unit/Result/HttpFetcherResultTest.php
|index 1dbea793..6060cdfd 100644
|--- a/tests/src/Unit/Result/HttpFetcherResultTest.php
|+++ b/tests/src/Unit/Result/HttpFetcherResultTest.php
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignoredpatch "-p2" --no-backup-if-mismatch -d "E:\wwwroot\zzz/web/modules/contrib/feeds" < "C:\Users\admin\AppData\Local\Temp\9/67167e57ec37b.patch"
can't find file to patch at input line 16
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From b0c52a15e36251cfa1c3529ee1d8a2bd2a78f177 Mon Sep 17 00:00:00 2001
|From: znerol <46208-znerol@users.noreply.drupalcode.org>
|Date: Mon, 14 Oct 2024 14:08:50 +0000
|Subject: [PATCH] Issue #3480545 by znerol: Fixed PHP Warning: unlink(): No
| such file or directory in HttpFetcherResult::cleanUp().
|
|---
| src/Result/HttpFetcherResult.php | 2 +-
| tests/src/Unit/Result/HttpFetcherResultTest.php | 2 ++
| 2 files changed, 3 insertions(+), 1 deletion(-)
|
|diff --git a/src/Result/HttpFetcherResult.php b/src/Result/HttpFetcherResult.php
|index fdd803ae..f9966d5c 100644
|--- a/src/Result/HttpFetcherResult.php
|+++ b/src/Result/HttpFetcherResult.php
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 29
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/tests/src/Unit/Result/HttpFetcherResultTest.php b/tests/src/Unit/Result/HttpFetcherResultTest.php
|index 1dbea793..6060cdfd 100644
|--- a/tests/src/Unit/Result/HttpFetcherResultTest.php
|+++ b/tests/src/Unit/Result/HttpFetcherResultTest.php
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignoredpatch "-p4" --no-backup-if-mismatch -d "E:\wwwroot\zzz/web/modules/contrib/feeds" < "C:\Users\admin\AppData\Local\Temp\9/67167e57ec37b.patch"
can't find file to patch at input line 16
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From b0c52a15e36251cfa1c3529ee1d8a2bd2a78f177 Mon Sep 17 00:00:00 2001
|From: znerol <46208-znerol@users.noreply.drupalcode.org>
|Date: Mon, 14 Oct 2024 14:08:50 +0000
|Subject: [PATCH] Issue #3480545 by znerol: Fixed PHP Warning: unlink(): No
| such file or directory in HttpFetcherResult::cleanUp().
|
|---
| src/Result/HttpFetcherResult.php | 2 +-
| tests/src/Unit/Result/HttpFetcherResultTest.php | 2 ++
| 2 files changed, 3 insertions(+), 1 deletion(-)
|
|diff --git a/src/Result/HttpFetcherResult.php b/src/Result/HttpFetcherResult.php
|index fdd803ae..f9966d5c 100644
|--- a/src/Result/HttpFetcherResult.php
|+++ b/src/Result/HttpFetcherResult.php
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 29
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/tests/src/Unit/Result/HttpFetcherResultTest.php b/tests/src/Unit/Result/HttpFetcherResultTest.php
|index 1dbea793..6060cdfd 100644
|--- a/tests/src/Unit/Result/HttpFetcherResultTest.php
|+++ b/tests/src/Unit/Result/HttpFetcherResultTest.php
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignoredCould not apply patch! Skipping. The error was: Cannot apply patch https://git.drupalcode.org/issue/feeds-3482189/-/commit/b0c52a15e36251cf...
> post-package-install: Drupal\Composer\Plugin\Scaffold\Plugin->postPackage
> post-package-install: Laminas\ComponentInstaller\ComponentInstaller->onPostPackageInstall
Generating autoload files
54 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
> post-install-cmd: Drupal\Composer\Plugin\Scaffold\Plugin->postCmd
> post-install-cmd: Drupal\Composer\Plugin\ProjectMessage\MessagePlugin->displayPostCreateMessage
* Homepage: https://www.drupal.org/project/drupal →
* Support:
* docs: https://www.drupal.org/docs/user_guide/en/index.html →
* chat: https://www.drupal.org/node/314178 →
I will try, but honestly I'm not super familiar with the new way of doing things. I'm still in the "patch" world. I'll try to get it figured out on Google.
I did not get this to work, but perhaps the issue was somewhere in the key/value configurations. I don't think it's clear how to configure these or what it's looking for. I created my own solution with JavaScript so I'm moving on. Perhaps it's necessary (as with my own solution) to use item.key[0].valuesince fetching JSON often involves arrays. For example, in JavaScript:
option.value = item.field_start_date[0].value;
option.text = item.name[0].value;Can we simply do a composer update choices/choices?
Can you please share what I'm supposed to do if I would like to use the new merge request? Will it be part of an upcoming official release?
You made this happen for little old me? :)
Hello - I think I have the same issue. I updated the module. I tried using the machine name and mapping to ID. In Devel, the id is the same as the machine name. That didn't work. I am now going to try mapping the UUID to the UUID. Is that the proposed solution once the module is updated?
Hello, I'm running out of time due to changes in MySQL. We've had a workaround in place that is no longer working. It the only working solution to downgrade to 1.x(3.x in D10)?
Hello - what's the recommended solution or workaround for this issue currently? Which version of the module doesn't use SQL Triggers? Is it still 1.x(3.x in D10) or has there been another update?
OK thanks. The platform is Amazee.io. I don't know about its certification but they are reputable.
I will attach a full log of the deployment. Each spin-up container for staging uses a copy of the production database and git branches for code/config.
Post-Rollout is a set of actions that are configured in the lagoon YML file after:
- All images have been successfully built.
- All containers are updated with the new images.
- All containers are running have passed their readiness checks.
There were some Views that were created probably 10 years ago which have since been migrated multiple times into several versions of Drupal, including 7, 8/9, 10. They were created when RSS feeds were more of a thing. I've been seeing a lot of messages about the feed aggregator module being deprecated. I'm trying to get rid of anything related to it, even though it's been out of our system for a good while now. This includes some feed Views, which I basically just removed in local, then pushed out to a dev branch, then to production. There were no issues when pushing these out last week.
I thought maybe webform was being ignored by Config Ignore, but that's not the case.
I just want to know how to fix this issue @cilefen
I used the link to documentation provided by @solideogloria
It provided info on how to get a diff/patch which I applied
As for long-term fix, I assume it will be merged into future version of Drupal, correct?
Can someone please tell me how to implement a merge request? I'm used to patches. Is this a matter of updating Drupal itself? Thanks
Following. I have the same issue.
If anyone could supply a patch for this version of the module, I'd appreciate it. I basically want the old version of the module that worked for me with the patch that supported grouping in tabs.
Have you tested assigning the same grouping value to multiple pieces of content? I can't tell from the screenshot. All I know is I did everything you are showing and it didn't group. I selected a value to group by - shown in your second screenshot.
I believe I got it working locally. I'm not confident in how to make a patch. I basically worked around the existing code and used this patch to guide me. https://www.drupal.org/files/issues/2024-03-19/views-rows-content-grouped-by-tab-field-2948150-49.patch →
Please let me know if there are plans to add the grouping code to the module, so I can do this the right way (the Drupal way).
Honestly, I think the template needs work. I could maybe try to help but there is no sign of a
- .
https://getbootstrap.com/docs/5.2/components/navs-tabs/
I think the patches addressed this possibly. I got the grouping to work, but there it's not rendering right at all. There's not content showing because there are no list items.
In the theme.inc file, there is no $vars['tab_group'] = $view->style_plugin->options['tab_group'];
I could go on and on, but it seems obvious this grouping code was not added to the version that was recommended to me.
The toggle "Group by tab field" is missing in the View form. I manually added it, however when I toggle to turn it "on", it does nothing. I'll have to look more closely at the code, but I think the update to the module is missing the form field and maybe something to make it work.
I'm tempted to learn how to create my own patch, based on the old ones, because I need this to be working and the old patches don't work. Any suggestions appreciated!
This patch has a line that's added
https://www.drupal.org/files/issues/2022-06-10/views-rows-content-grouped-by-tab-field-2948150-40.patch →
like this, "+ $form['tab_group'] = [
+ '#type' => 'checkbox',
+ '#title' => $this->t('Group by tab field'),
+ '#default_value' => $this->options['tab_group'],
+ '#description' => $this->t('If you want to group tabs by same values.'),
+ ];"
I cannot find this in the code here: /src/Plugin/views/style/ViewsBootstrapTab.php (which is installed in beta)
I'm attaching a screenshot of what I see in the View
I started out using the "beta" version of this module, then I switched back to alpha hoping it might work. I just ran this command:
composer require 'drupal/views_bootstrap:^5.5@beta'
I cleared cache, and the problem still exists. If you don't think it's a bug, then we can change to support request.
Currently I'm running Drupal 10.3.1, PHP 8.1.x and this Version: 5.5.0-rc1, which was installed when I chose beta.
Is this the same problem I'm having?
https://www.drupal.org/project/views_bootstrap/issues/2948150
✨
Views Bootstrap Tabs cannot be grouped
RTBC
My production site currently works. We are using 5.5.0-alpha1 with Drupal 10.2.5. We have a patch "installed" using composer from the issue above.
"drupal/views_bootstrap": {
"2948150: Views Bootstrap Tabs cannot be grouped" : " https://www.drupal.org/files/issues/2024-03-19/views-rows-content-groupe... → "
}
When I updated to 10.3.1, it wouldn't let me keep this patch. I'm wondering if this patch is necessary in order for tabs to be "grouped" or aggregated. Also, why is composer saying it cannot install the patch?
Tab settings added, what would you like to see exactly?
I determined that this is an issue with my SOLR container in my local environment. I removed the SOLR container locally and the site came up. Also, I deployed the site to a new branch and I don't see any issues. I attribute this problem to Docker/Lagoon/Lando and not this module.
rraney → created an issue.
I'm considering just attempting to create my own module using this as a model.
https://jsfiddle.net/u43pj69g/
There are no errors in Console. I also don't see any kind of connection to Google in "Sources" when I inspect the page. When I inspect the Elements, I don't see any evidence of Map API code, scripts or anything. It's like the widget isn't loading into the content form.
We use a Google Places Autocomplete widget for a text field in a content type. In the content form, nothing happens when we start typing.
This issue appears to be resolved. The culprit was custom JavaScript which needed to be cleaned up. It was really hard to find the error because it was only happening on mobile. Therefore I couldn't properly inspect or use DevTools. Regardless, if this happens to someone else, I'd recommend taking a hard look at JavaScript errors and conflicts which might mess up the normal functioning, presumably through jQuery UI or some other JS mechanism.
I don't see Drupal webform 6.2.5 listed at Simplytest. The Drupal version is 10.3.1 and I don't know how to downgrade. I got the form imported and it works fine with 10.3.1 and the most recent version of this module.
The mobile devices affected include my personal Android phone and iOS phones used by end users. I have not tested on a tablet because I simply do not have one.
I'm including the YML file as an attachment.
Thanks - that appears to have worked.
"choices/choices" : {}
Hello, I tried applying the patch as part of "drupal/webform" in composer.json.
"drupal/webform": {
"3457416: choices/choices 9.0.1 is affected by polyfill.io" : " https://www.drupal.org/files/issues/2024-06-27/3457416-choices-affected-... → "
}
Should it be part of "drupal/core"? After I ran composer -v install, it gave me the error:
Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2024-06-27/3457416-choices-affected-... →
In Patches.php line 331:
[Exception]
Cannot apply patch 3457416: choices/choices 9.0.1 is affected by polyfill.io ( https://www.drupal.org/files/issues/2024-06-27/3457416-choices-affected-... → )!
I'm using Drupal 10.2.5. I just tried to apply the patch in #76. I'm getting this error:
Cannot apply patch 3392572: Deprecated function: strnatcasecmp(): Passing null to parameter #1 ($string1) of type string is deprecated in LayoutPluginManager ( https://www.drupal.org/files/issues/2024-06-10/drupal-deprecated_strnatc... →
tch)!
I was trying to replace the patch from an earlier date. https://www.drupal.org/files/issues/2023-11-01/3392572-26.patch →
What is the recommended version and course of action for this?
Has there been a resolution or change to this since 2022? I'm not certain, but we may have an issue with triggers as it relates to our hosting platform. I see a "failed testing" for most or all of the patches.
Actually, I'm intermittently seeing the badge. There are forms like this: https://www.dgcoks.gov/administration/contact
This page has BOTH enabled and there is no badge. I'd say generally the only time I see the badge is if a form element is enabled. The IDs are all correct.
Thanks but when I don't have a captcha element, but do have a captcha point, I don't see a badge
Should the form captcha v3 be working if I create a point but don't use a form widget? I'm not seeing a badge on the form pages where there is a point configured, unless I enable the widget.
I just started a brand new "site" in Google with new keys. I didn't have any issues logging in.
So you suggest unchecking on both Google and in Drupal? (despite what is says about doing one or the other)
I just uploaded the v3 settings in Admin
I wonder if I should try with new keys. That's the only thing I haven't tried.
Label
reCAP v3 Action
Machine name: recap_v3_action
Label for the reCAPTCHA v3 action.
Threshold
0.5
The threshold score value. See the scores interpretation documentation for more information.
Fallback challenge
reCAPTCHA (from module recaptcha)
Select the fallback challenge on reCAPTCHA v3 user validation fail.
I added "www" and tried logging into site. Still getting the error message, then it falls back to v2 checkbox.
I just re-enabled this in Google admin
Verify the origin of reCAPTCHA solutions
If disabled, you are required to check the hostname on your server when verifying a solution.I had just removed a staging domain from the list and saved the changes. It turns out I accidentally deleted both domains, but this was only for a minute. I know it appears that I didn't have a domain configured, but I did.
I can't send an image or file with the "Contact" feature on your profile page. I don't know how to add screenshots here. When I click the add image button, it wants an image URL.
Yes, it looks like one of the "problem" webforms has a custom template. However, one of them does not. As mentioned, we also turned off captcha on the user login form, which is not using a custom template.
I am not quite at the point where I can share dev. environments with you. We just changed our hosting platform and only have a production environment. I can share a form that's enabled with captcha via the "points" but it does not have a captcha widget.
I noticed that the only remedy appears to be removing the captcha form element from forms. There was a form that was disabled via points, but still had the captcha widget. This widget was giving users a lot of trouble.
The user login was the form that we started having issues with. This does not use a custom template.
1. Are you using a custom template for the form with a captcha?
2. Can you send me a link to the form page in PM?
Sorry I missed these questions. I will look into it shortly. I will have to enable a form with captcha in order for you to view it failing. I think I actually do have a custom page template for all webforms.
Now we are starting to get reports of people being unable to submit forms because of captcha errors. I've checked the keys many times and they are set up correctly. The badge appears on our website, so I know I have the domain set up correctly in Google. I've been asking people to provide more specific error messages, but it seems v3 is failing in forms.