I added a temporary patch for the composer.json file for review.
OPTASY → created an issue.
I created a simple patch for this, I am not sure if it's the best solution, but feel free to make any suggestions on this.
OPTASY → created an issue.
Attached a patch for the WxT Distribution composer.json file just in case.
OPTASY → created an issue.
I was able to apply the patch with no issues:
Need further testing.
I think I still see this issue on version 5.0.x:
html/themes/contrib/wxt_bootstrap/templates/views/views-view-table.html.twig: 'wb-tables',
html/themes/contrib/wxt_bootstrap/templates/views/views-view-table.html.twig:<table{{ attributes.addClass(classes).setAttribute('data-wb-tables', '{ "bPaginate" : false, "bFilter" : false, "bInfo" : false }') }}>
html/themes/contrib/wxt_bootstrap/templates/calendar/calendar-day-overlap.html.twig: <table class="wb-tables table full">
html/themes/contrib/wxt_bootstrap/templates/calendar/calendar-day.html.twig:<table class="wb-tables table full">
I'll look into adding a checkbox in the views config (/admin/structure/views/settings or perhaps at /admin/config/wxt ?) to make this sorting optional.
I tested this patch and works as expected, I was able to set the countries that are displayed in the webform address field:
Attached a patch to update the composer.json file
I had a look on this and it looks there there is an issue with a translation file for the bootstrap theme (bootstrap-8.x-3.29.fr.po), specifically at line 433:
msgstr "<div>@message</div><pre><code>@backtrace
"
There's already a patch for this: https://www.drupal.org/project/bootstrap/issues/3249470 📌 Error generated when importing translation Closed: won't fix
Attached a patch that updates the composer.json file to include the external bootstrap patch.
Attached a patch for the composer.json file, worked ok for me, kindly review.
Sure @smulvih2 , I'll submit a patch for it later today.
Attached a patch for fixing this
I also saw this warning when install Wxt 5.0.0 on PHP 8.2:
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /core/install.php?rewrite=ok&profile=wxt&langcode=en&id=1&op=do_nojs&op=do
StatusText: OK
ResponseText:
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/html/html/profiles/wxt/modules/custom/wxt_admin/src/EventSubscriber/MenuRouterRebuildSubscriber.php on line 62
{"status":true,"percentage":"63","message":"Completed 33 of 52.","label":"Installed \u003Cem class=\u0022placeholder\u0022\u003EWxT Admin\u003C\/em\u003E module."}Attached a patch to fix this
OPTASY → created an issue.
I have another issue with PHP 8.2 and the contrib module views_bootstrap: https://www.drupal.org/project/wxt/issues/3393796 →
I saw the same issue when installing WxT 5.0.0 a few days ago, let's see what I can find on my end.
Thanks a lot @sylus , a friendly reminder for the credits on this please, I don't see it in my profile :)
Thanks @smulvih2 and @joseph.olstad for your input, the patch that I provided has the content filtering options disabled for the "Full HTML" configuration, I'll have a close look and see what other plugins can be disabled.
Patch #17 did the work for me, thanks for that @sthomen !
I have a patch for this issue, this will set CkEditor 4 for the "Full HTML" format, kindly review.
I tested this and I was able to create the B5 Subtheme, I had to run this command for that
drush --include="web/themes/contrib/bootstrap5" bootstrap5:subtheme --subtheme-name="B5 subtheme"
Sadly, the drush B5 command is not available if I don't use the --include option, and I had to clear cache because the new subtheme wasn't available at /admin/appearance right after I ran the drush command.
I tested this on a 10.0.x Drupal installation and couldn't replicate this, I'll try on a D10.1.x and see
OPTASY → created an issue.
I applied the patch without issues.
Thanks, I've been using WxT v5.0.0 on PHP 8.2 for a company project, I've seen a few warnings here and there, I might submit extra issues here.
I wasn't able to replicate this issue.
It seems like this is already fixed in the 5.5.0-alpha1 release of the module https://www.drupal.org/project/views_bootstrap/releases/5.5.0-alpha1 → , not stable though.
I tested against a D10 instance and I don't see this issue myself, but I see other issues with the info.yml file.
I tested this patch on a D10/WxT 5.0.0 instance, and I can see that the RAP is displayed on the 404 page (a non-node page), and the DYF is displayed on all node pages.
I tested the patch #10 but the settings form is not being rendered and I don't see any PHP warning
Hi @smulvih2 this is the result of compiling the scss files, should I include these only? Open to any suggestions.
Attached a patch to fix that, tested on a D10 and works as expected, I can see the new metatags for the homepage.
I tested this on a D10 instance and I am getting this error here:
Drupal\Core\Entity\Query\QueryException: Entity queries must explicitly set whether the query should be access checked or not. See Drupal\Core\Entity\Query\QueryInterface::accessCheck(). in Drupal\Core\Entity\Query\Sql\Query->prepare() (line 141 of core/lib/Drupal/Core/Entity/Query/Sql/Query.php).
Drupal\Core\Entity\Query\Sql\Query->execute() (Line: 115)
simplemeta_meta_load_by_path(Array, 'en') (Line: 145)
simplemeta_get_page_meta() (Line: 71)
simplemeta_page_attachments(Array) (Line: 311)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}(Object, 'simplemeta') (Line: 388)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('page_attachments', Object) (Line: 312)
Drupal\Core\Render\MainContent\HtmlRenderer->invokePageAttachmentHooks(Array) (Line: 285)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 286)
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: 168)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 74)
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: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 692)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)I wasn't able to replicate this, how do I add the new field?
I tested this on my D10 instance and works as expected, I used the token [current-user:uid] for a link in the main menu and I got the expected link.
Patch #10 didn't work for me (attached screenshot).
Tested this on a D10 instance, works ok, README.txt file needs to be renamed to README.md.
I have a proof-of-concept patch for testing the hook_countries_alter() as mentioned by @Liam Morland, this patch just deletes "Taiwan" from the country list, and I can see that is already working in the webform that I have (attached screenshot), the list can be altered as needed, but I agree with the taxonomy approach as mentioned below.
Here's a list of GoC countries/areas of interest that I found: https://www150.statcan.gc.ca/n1/en/pub/12-608-x/12-608-x2019001-eng.pdf?...
I did see that issue myself on v4.5 and v5.0, I have a patch for the wxt_bootstrap theme that fixes this (a small css change), we should probably create this issue in the wxt_bootstrap project as well.
Tested this on WxT 5.0.0 instance, I can see that the "role=menu" attribute is gone for the footer menus.
I created a patch for this, needs to be applied in the wxt_bootstrap project, let me know what you think.
I tested the patch on a WxT 5.0.0 instance, and I don't see the extra query values after applying the patch.
Tested this and worked as expected, moving this to RTBC