Custom Form returning blank - Cache Manager settings help please

(Amurray) #1

(Squiz Matrix v5.4.3.1)

Hi! We have a custom form returning blank for submitters :frowning:

Cache manager settings have been adjusted [below] for the root node and type specific.
only submits/loads error validation on /_nocache or /_recache url
at standard url it flips back to an empty form
standard f5 asks if you want to ā€œconfirm form resubmissionā€ which is weird.

So Iā€™m at a loss as Iā€™ve moved the form into several locations/designs, stripped back itā€™s function to bare bones, and mainly looking for options as to what to pursue next! 100% not nested - I assure you!

For HTTPS forced Custom Forms: do any of these other Cache Manager settings need to be explicitly defined? Or is it overkill?

Send Cacheable Header
Protocol(s)
HTTP Cache Control Level
HTTPs Cache Control Level
Accelerator Cache Expiry

\\\\\\\\\\
I read: Help! Custom form not working
and I had the same issue at first.

This form used to go straight to the Thank you bodycopy. The page now does show the form the first time you visit the page, but on successive visits it went straight to the Thank You body copy.

For forum posterity, even though it was added to the cache manger, we had discovered that there wasnā€™t further Root Node Cache Management settings in the Cache manager to make it work.

Here is what was added to correct:

  • Yes (Assets underneath this root node ARE affected)
  • Caching Status: OFF
  • Default Expiry: 0 seconds
  • Browser Cache Expiry: 0 seconds
    \\\\\\\\\\\\\

Cheers and thanks!

(Amurray) #2

Another team member has advised its just how the form is presented in the page contents bodycopy.
If you just have %form_contents% and ZERO adjustements to the bodycopy, it works.

The %form_errors% were all displaying fine showing at the start of the form, and dropping off the list as each field was attended to.

I was trying to minimse the bodycopy, and make it editable in Edit+ too, with a blend of %section_contents_xxxxx% for 5 sections, and html for a certain section I needed to flesh out itā€™s fieldā€™s design.

Any advice about using %section_contents_xxxxx% with error fields validation muchly appreciated!

(Bart Banda) #3

Hey amurray,
Not sure what your current issue is, are you saying that the cache issue is resolved and now you are trying to get inline server side errors to appear when using %section_contents_xxxxx% keywords in the page contents custom bodycopy?

(Amurray) #4

Hi Bart, yes thatā€™s right!
I know it might not be possible thoughā€¦as weā€™re trying to make sure the forms are as editable as possible for Edit+ editors, %form_contents% is the most desireable thing to use moving forward, but for expections to that rule for special cases trying to only part-customise form sections I thought could be the cleanest way.

Possibly the two issues could be tied, if itā€™s returning to a blank page with no ability to advise whatā€™s missing, even though the %form_errors% were all resolved, inline form errors are more accessible, and could reveal what might be going on.

(Bart Banda) #5

So youā€™ve got a form with multiple sections, but all sections printed on the first page of the form (the form contents page), and instead of using %form_contents% to print all form sections there, you want to individually print each form section manually using %section_contents_xxxxx%, but still on the form contents page and not within a customised bodcopy of each section?

(Amurray) #6

Thatā€™s right, Iā€™m placing it all on the main form page bodycontents,
in this form, I only need to customise one section, which was my reasoning for trying to be economical with the other sectionā€™s keywords.

AH - Customising the bodycontents of each section instead sounds like a good idea, Iā€™ll try there and see if it does the same thing. I guess I was trying to only employ what the editors could see within the confines of Edit+, but it is a good suggestion and wil try today - thanks!