The most glaring issue I see is that you're continuing to
reference $prof inside your Associates and Assistants loops. The
first thing I would do is switch $prof to $assop and $assp
I want to take a minute to talk about some things you're doing
with Velocity -- maybe share some advice and knowledge for a quick
minute. I will post those things I'd like to share on my next
comment here in a few minutes. I am still putting them together,
but wanted to go ahead and let you know what I think the issue
I see that for some fields you're using the .value
property and for some you're using the
$_SerializerTool, which is fine. I want to suggest
that you reverse the times you choose to using those two
When you're working with a field that a user can type in
information for (text input, textarea, WYSIWYG) I would use the
$_SerializerTool then. I may be incorrect since I
can't see your Data Definition, but some examples of this are your
$chfname, $chlname, and $chphone.
The .value property can safely be used when you
know the output doesn't contain special chars, like a
/path or /link since asset names after
safe-guarded by Cascade. There really isn't any need to
.serialize() those values.
It looks like each one of your loops are pretty much exactly the
same. I would suggest using a Macro to write that HTML for you.
Basically writing a function to write the foreach loops for you and
simply passing in the list you'd like available for the loop.