I haven't seen that specific error before, but given the date value is in US format (e.g. "MM/dd/yyyy"), then I suspect that the target web-server isn't using the same culture? (so it can't parse the date/time format).
I'm not sure what can be done to rectify it (within Nested Content). Other than make sure that the culture of both the source/target web-servers match up?
I've restore down both environment on my local. Tried couriering it too. The same error even both environment is on my local. So might not be the culture issues. Not sure what I can do.
I might switch out the Date Time within Nested to use textstring instead.
Nested Content with Date
Hey Lee,
I've got the below when I try to courier across a date property within a nested content.
Any idea how I can resolve it?
The node in the destination is not loading when i have the date in.
Hi JLon,
I haven't seen that specific error before, but given the date value is in US format (e.g. "MM/dd/yyyy"), then I suspect that the target web-server isn't using the same culture? (so it can't parse the date/time format).
I'm not sure what can be done to rectify it (within Nested Content). Other than make sure that the culture of both the source/target web-servers match up?
Hope this helps (a little)?
Cheers,
- Lee
Thanks for replying so quick Lee.
I've restore down both environment on my local. Tried couriering it too. The same error even both environment is on my local. So might not be the culture issues. Not sure what I can do.
I might switch out the Date Time within Nested to use textstring instead.
Let me know if you figure out anything.
Appreciate all your help
I'm trying to upgrade courier as well. Just in case its the version that's causing the issues. Keep you in the loop
Thanks
Good news. It's working with the latest Courier 3.0.6. Must have been a bug from courier i believe then.
Thanks for replying so quick Lee. Helpful as always :)
Cool, happy to hear that it's working now! :-)
is working on a reply...