- 🇺🇸United States paulkittredge
Thank you for the patch! This worked great for me, on a 10.0.5 site running PHP 8.1.14 and with Views Reference Field at 8.x-2.0-beta4.
Any chance you can roll a new release for this? Or are you waiting for more feedback?
- Status changed to RTBC
over 1 year ago 11:25am 18 March 2023 - 🇮🇳India renganathan_t
:+1; RTBC
Thank you for the patch! This worked on a 10.0.5 site running PHP 8.1.17 and with Views Reference Field at 8.x-2.0-beta4. - Status changed to Fixed
over 1 year ago 6:50pm 20 March 2023 - 🇳🇱Netherlands seanB Netherlands
Commited, thanks everyone! Please help test the latest dev version.
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
about 1 year ago 6:59pm 1 May 2023 - 🇨🇭Switzerland ytsurk Switzerland
For me this exception was not visible.
The ajax call returned 400 bad request containing a full HTML page in the payload, saying:
"A client error happened" - 🇨🇦Canada dadderley Vancouver
I had this issue after upgrading from Drupal 9.5.9 to Drupal 10.0.9.
The dev release (Development version: 8.x-2.x-dev updated 20 Mar 2023 at 20:03) makes Ajax work and the error goes away.
Thanks
- 🇺🇸United States neclimdul Houston, TX
yeah, it'd be nice to have this in a release. running the committed patch fixed the problem for us as well.
- 🇺🇸United States mgbellaire
I am still having issues with this. Drupal 9 worked, but our Drupal 10 version of our filters do not work. Were there any other findings on this while working on it that may be fixed by something like configuration of this filter?
Drupal 10.0.10
Views Reference 2.0.0-beta6