[
http://jira.magnolia-cms.com/browse/MGNLSTK-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Melcher updated MGNLSTK-819:
-----------------------------------
Labels: forms (was: )
Affects Version/s: 1.4.5
1.4.1
(was: 1.4.2)
Environment: Linux, demopublic.magnolia-cms.com (was: Windows (XP),
Linux (Debian 5))
Description:
Hi everyone!
Could it be that this still isn't quite working?
I was trying to work around this issue on 4.4.1 by a cachePolicy setting.
Didn't work, so I compared this with demopublic.magnolia-cms.org on 4.4.5:
Getting session expired errors as well, couldn't submit the form a single time
there.
What would be a correct setting for excluding certain name patterns from
caching? This is what I was trying:
in
config:/modules/cache/config/configurations/default/cachePolicy/voters/urls/excludes
I have added:
forms-en/
-- class: info.magnolia.voting.voters.URIPatternVoter
-- pattern: .*form.html.*
forms-de/
-- class: info.magnolia.voting.voters.URIPatternVoter
-- pattern: .*formular.html.*
level: 4
So, what could be the problem here?
Thanks in advance
Martin
was:
Dear Sirs,
The contact form of the public instance of Magnolia 4.4.2 doesn't work: it
gives (randomly) a "session expired" error. This is critical for production
because if the contact form doesn't work properly customers can't contact us.
My observations:
Connect to the public instance (not authoring) of online demo of
magnolia-cms.com. Go to the contact form. Don't fill any field, it's not
necessary. Just click the Submit button. The first times maybe you get the
normal error messages about empty fields. Ok, this is fine. But try again from
different windows, different sessions, different computers. Soon the contact
form will be broken and you will start to get the "session expired" error. If
you enter the fields (email, subject, etc) of the contact form the result is
the same.
I have tested a lot of things of the servers. Nothing fixed it.
After several hours, I disabled caching system of public instance (just by
putting enabled=false in /configuration/server/filters) and flushed the
caches.... and wow, it worked again! but at the price of a very sloooowww
website.
I migrated to 4.4.2 from 4.3.6 only to get multilingual contact forms. And this
migration broke the contact form in the mentioned way! It seems that 4.4.2
manages contact form in a different way. If cache is enabled, contact form
stops working after several attempts from different windows/sessions/computers.
So, now, I need first a workaround to disable cache only for the contact page.
Maybe this way a get again a fast website and a contact form that works. Which
is the way to achieve that? I have read the bypass configuration option, but
don't have much documentation to know how to use it.
Please confirm if this observations are right and provide a fast workaround to
solve this.
Thanks,
David G.
> CLONE -Contact Form still doesn't work (Magnolia 4.4.1 - 4.4.5)
> ---------------------------------------------------------------
>
> Key: MGNLSTK-819
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-819
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
> Affects Versions: 1.4.1, 1.4.5
> Environment: Linux, demopublic.magnolia-cms.com
> Reporter: Martin Melcher
> Assignee: Philipp Bärfuss
> Priority: Critical
>
> Hi everyone!
> Could it be that this still isn't quite working?
> I was trying to work around this issue on 4.4.1 by a cachePolicy setting.
> Didn't work, so I compared this with demopublic.magnolia-cms.org on 4.4.5:
> Getting session expired errors as well, couldn't submit the form a single
> time there.
> What would be a correct setting for excluding certain name patterns from
> caching? This is what I was trying:
> in
> config:/modules/cache/config/configurations/default/cachePolicy/voters/urls/excludes
> I have added:
> forms-en/
> -- class: info.magnolia.voting.voters.URIPatternVoter
> -- pattern: .*form.html.*
> forms-de/
> -- class: info.magnolia.voting.voters.URIPatternVoter
> -- pattern: .*formular.html.*
> level: 4
> So, what could be the problem here?
> Thanks in advance
> Martin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
