Convert Views to use GET for AJAX

Created on 15 August 2022, over 2 years ago

Updated 17 March 2023, over 1 year ago

After 📌 Allow AJAX to use GET requests Fixed the AJAX API will allow either POST or GET for AJAX requests.

Views AJAX uses the JavaScript AJAX API directly (as opposed to #ajax), and is relatively simple to convert to GET.

Discussed with @lendude and we came up with the following:

It's preferable if all AJAX-enabled views use GET for performance, since they'll all be able to make use of render caching.
Putting this in Views UI config is undesirable, it's not really a concept we want to expose to site-builders, and there is no benefit to using POST for AJAX unless to workaround a bug.
There is a non-zero chance that this will break either a contributed module, or some custom code, or a view on the site somewhere. It is unlikely anyone is explicitly relying on POST, since non-AJAX-enabled views always use GET anyway, but there could be a view with an extremely long URL and the extra bits with AJAX info could put it over the edge or similar.
Therefore, we should add a flag in $settings (like $settings['views_ajax_use_post']), account for this in the Views AJAX handling, and document it in the change record.
Then (either in this issue or a follow-up) we can deprecate the setting and remove the POST support altogether in Drupal 11

📌 Task

Status

Closed: duplicate

Version

10.1 ✨

Component

Views →

Last updated about 4 hours ago

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.

Performance
It affects performance. It is often combined with the Needs profiling tag.

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment over 1 year ago →
🇬🇧United Kingdom catch
Have merged this back into 📌 Allow AJAX to use GET requests Fixed .

Production build 0.71.5 2024