Maximum call stack size exceeded

Created on 2 July 2021, over 3 years ago
Updated 17 January 2024, 10 months ago

Views Ajax History is causing a call stack size error

When loading a view that uses ajax and filters, the initial selection of a filter works and the view performs its ajax reload properly. However, subsequent filter attempts results in a Maximum call stack size exceeded error.

This results in not being able to filter a view more than once after loading a page.

The view works fine if the Views Ajax History module is disabled.

In the case of my view I have 4 exposed taxonomy term filters, and 1 exposed combine filter that uses the title and 2 text area fields.

EDIT: This is only happening on certain sites that I maintain - I think there is a conflicting module in play

Steps to reproduce

  • Create a view with exposed filters and ajax enabled
  • Load page with view and select an exposed filter. The view will ajax reload/filter properly.
  • Attempt to select another filter. View will attempt an ajax reload and throw a 'Maximum call stack size exceeded' error.
πŸ› Bug report
Status

Needs review

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States MikeyR

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024