-
- 101 Posts
Here is an excerpt from my log file. I've been able to remove the error messages by converting the uncached field references, only problem is that leads to all rows being emailed having the same label and data. So this is the output currently. I'm also looking for a way to just silence this warning, we've got some systems that are quite large with long forms. Every submissions grows the log file significantly, where it's grown to over 1GB in a matter of months.
[2018-05-16 10:32:13] (ERROR @ /mnt/target03/358650/763767/www.svddev.com/web/content/core/model/modx/modparser.class.php : 452) You should not call uncached elements inside cached!
Outer tag: [[$fbSelectDropdown?
&field_layout=`[[*fb_form_layout]]`
&field_name=`May we contact this employer`
&field_default=``
&field_helptext=``
&field_required=`0`
&rows=`[[$fbSelectDropdownRow?
&field_name=`May we contact this employer`
&field_option=`Please Select One`
&unique_idx=`63`
]]
[[$fbSelectDropdownRow?
&field_name=`May we contact this employer`
&field_option=`Yes`
&unique_idx=`63`
]]
[[$fbSelectDropdownRow?
&field_name=`May we contact this employer`
&field_option=`No`
&unique_idx=`63`
]]`
&unique_idx=`63`
That error means the parser is unable of processing the tag, so silencing it will not do away with problems you may not realize you have.
That said I don't immediately see the uncached tag it is worried about...
The mosquito trick is useful to avoid this sort of issue in most cases.
-
- 101 Posts
I'll fiddle with it some more, the odd situation so far has been that I can fix the error, but that breaks the form. FormBlocks is a black box to me I try not to mess with too much when it's working.
☆ A M B ☆