[MGNLFORM-125] Don't require to disable cache unless it's a multi-step form Created: 21/Mar/12  Updated: 04/Apr/12  Resolved: 03/Apr/12

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.3
Fix Version/s: 1.3.2

Type: Improvement Priority: Major
Reporter: Anne-Marie Scheidegger Assignee: Milan Divilek
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any Magnolia CMS 4.4 - 4.4.5 environment


Issue Links:
duplicate
duplicates MGNLFORM-82 Forms should be able to render the fi... Closed
duplicates MGNLFORM-93 Forms should exclude themselves from ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

As described here http://documentation.magnolia-cms.com/modules/form.html#Disablingcache, starting with Magnolia CMS 4.4, individual form pages and the first page of a multi-step form need to be excluded from cache to prevent "session expired" errors. This has major disadvantages for people using forms in a simple Magnolia setup:
1. It doesn't work out of the box: The person setting up the Magnolia has to know about disabling the cache, which might be overlooked and not caught by rudimentary testing since the "session expired" error only occurs with IE (right?)
2. Editors have to be told not to change the names of the form pages or report their renaming, so that the caching rules can be adjusted. Of course this could be checked and adjusted by scripts, but in a simple setup that would exceed the budget available for CMS development and configuration.
Therefore, I would vote for requiring the cache-disablement only on multi-step forms, that are more complicated than a simple contact anyway.



 Comments   
Comment by Jan Haderka [ 02/Apr/12 ]

This problem occurs only on 4.4.x, no need to fix it on 4.5 branch.

Comment by Milan Divilek [ 03/Apr/12 ]

This issues is solved (MGNLFORM-82, MGNLFORM-93) for Magnolia 4.4.6 and for 4.5.x. So individual form pages and the first page of a multi-step form are excluded from cache by magnolia.

Generated at Mon Feb 12 05:37:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.