An issue was found where if a custom field was named something like "Destination Image", the itinerary system was not properly rendering the content in that field.  This was caused because of a conflict with other placeholders used in the itinerary system.  This issue has been fixed so that custom fields on the destination will work regardless of their name.