Bug #12094: [Fluid] Ajax Widgets can't be used from within cachabele actions - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (6)

Benjamin Franzke
Daniel Schöne
Jerome no-lastname-given
Stefan Dürrenberger
Stefan Neufeind
Viktor Livakivskyi

Actions

Copy link

Bug #12094

closed

[Fluid] Ajax Widgets can't be used from within cachabele actions

Added by Thomas Maroschik over 13 years ago. Updated over 2 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Fluid

Target version:

Start date:

2011-01-11

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

6.2

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

Problem¶

When using a Fluid Ajax Widget on a cachable controller action, then fluid-widget-id is cached in template output. Since fluid-widget-id is bound to an individual fe_user, the fluid-widget-id won't get updated upon every request.

Sometimes you want be able to fetch cached data via Ajax.

Solution¶

Check if the stored action in Widget Context is cacheable. If yes, then save the context with AjaxWidgetContextHolder to a cache instead of the session.

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Task #92529: Remove fluid widgets

Closed

2020-10-09

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Thomas Maroschik over 13 years ago

Oops, perhaps this issue should be moved to fluid project.

Actions

Copy link

Updated by Kevin Ulrich Moschallski over 13 years ago

Hi,

+1 on this. I noticed this behaviour yesterday.

Do you have a patch for that?

Actions

Copy link

Updated by Marc Bastian Heinrichs about 13 years ago

Category set to 964

Actions

Copy link

Updated by Stefan Neufeind almost 12 years ago

@Thomas: Have you solved or worked around this issue when you discovered it (back then long time ago)?

Actions

Copy link

Updated by Ingo Pfennigstorf over 11 years ago

Status changed from New to Needs Feedback

Actions

Copy link

Updated by Anja Leichsenring over 11 years ago

Project changed from 534 to 2559
Category changed from 964 to Fluid: Widgets

Actions

Copy link

Updated by Viktor Livakivskyi over 10 years ago

Issue still exists in 6.0.
Any news regarding fix?

Actions

Copy link

Updated by Helmut Hummel about 10 years ago

Could be an option to add stateless support:

https://git.typo3.org/Packages/TYPO3.CMS.git/commitdiff/refs/heads/sandbox/helhum/fluid-ajax-widget-stateless

Actions

Copy link

Updated by Helmut Hummel about 10 years ago

Status changed from Needs Feedback to Resolved
% Done changed from 0 to 100

Applied in changeset 1629aea9afd7c11198763b0ec69d634cf7a32b63.

Actions

Copy link

#10

Updated by Marc Bastian Heinrichs about 10 years ago

Status changed from Resolved to Accepted

Actions

Copy link

#11

Updated by Benjamin Franzke almost 10 years ago

The accepted commit 1629aea9afd7c11198763b0ec69d634cf7a32b63 is not yet in master.
Whats holding this up?

Ajax Widgets are quite useless without this.
Therefore: Do you think this could be cherry-picked to 6.0/6.1 TYPO3 versions, as this really fixes a major bug?

Actions

Copy link

#12

Updated by Stefan Dürrenberger almost 10 years ago

I tested the patch on 6.2.2 and it seems to work fine except for one detail. I get a 404 if the AJAX request doesn't go to index.php. In the patch, that is addressed for UriViewHelper, but not for LinkViewHelper.

I'm not sure if there's a reason for it, but otherwise line 111 in typo3/sysext/fluid/Classes/ViewHelpers/Widget/LinkViewHelper.php should be changed to:

                return '/index.php?' . http_build_query($arguments, NULL, '&');

Actions

Copy link

#13

Updated by Stefan Dürrenberger almost 10 years ago

After some more testing we were not able to use the patch in production. The string generated from the widget context can grow too large, resulting in a URL that is longer than supported by browsers and servers (> 2kb in our tests).

Actions

Copy link

#14