- Issue created by @optasy
- 🇨🇦Canada optasy
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.
- 🇨🇦Canada smulvih2 Canada 🍁
@optasy for the time being we are stuck on drupal/views_bootstrap 5.3 since we need Bootstrap 3. Maybe create a ticket for 5.3 to fix this issue, and we can apply that patch in WxT.
- 🇨🇦Canada jenniferaube
Im using ddev and when changing to php 8.2 I ran into this issue as well
- 🇨🇦Canada optasy
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
- Status changed to Needs review
about 1 year ago 8:26pm 19 October 2023 - Status changed to Needs work
about 1 year ago 9:01pm 19 October 2023 - 🇨🇦Canada smulvih2 Canada 🍁
@optasy the related ticket deals with WxT PHP8.2 issue. We can use this ticket to fix the install issue with views_bootstrap, so adding your patch for views_bootstrap to composer.json for WxT.
- 🇨🇦Canada optasy
Attached a patch for the composer.json file, worked ok for me, kindly review.
- Status changed to Needs review
about 1 year ago 12:57am 20 October 2023 - Status changed to RTBC
about 1 year ago 2:53pm 20 October 2023 - 🇨🇦Canada smulvih2 Canada 🍁
I wasn't seeing this issue as my D10 sandbox was pinned to 5.0.0, but this issue only seems to happen with 5.0.x-dev. Tested the patch and it fixes the install error as expected.
- Status changed to Fixed
about 1 year ago 5:15pm 21 October 2023 Automatically closed - issue fixed for 2 weeks with no activity.