Open ckoppelman opened 10 years ago
As a workaround for this issue (if others come across this), I was able to create an intermediary between my data and the mfp processor that, for each needed mfp field, does something ugly like:
var newObj = {
number: oldObj.number || null,
ordinal: oldObj.ordinal || null
};
See this fiddle for an example. The summary is that if you are populating a template with an array like so:
and a template like:
then the
.mfp-ordinal
div for number = 'two' doesn't get emptied out. On the other hand, it does get emptied out for number = 'four'.