I'm using the Job Posting module on 4 similar Drupal sites, and I am using the Publish (http://drupal.org/project/publish) and Subscribe (http://drupal.org/project/subscribe) modules to share Job Posting nodes between the sites. The Publish'ing site of the node has a View that the Subscribe'ing site connects to, to grab/map the node content.

All the fields of Job Posting content-type are shared between the sites properly but the "Deadline" field.

My issue is when the subscribed site pulls the data, it's value is not the same as the publishing site.

On the Publish site, the UTC value in the database is (for example): 1308877200
On the Subscribe site, the value it pulls is always: 14400 (which seems like a timezone offset)

I've tried a number of fixes, but I'm not sure if I'm getting any closer to isolating the problem. Things I've tried:

- Converted the field "deadline" in the job_posting table in both sites to be an 'int(11)' instead an 'int(10) unsigned' in the database to be inline with Drupal's other date fields. This did not fix the issue.
- Set the "deadline" field in the View of the Publishing site that I'm Subscribing to, to show the deadline field value as a Unix timestamp. Setting the display for the date as Custom and set to: U. This also did not fix the issue, as subscribing site still shows 14400 in the database.
- Like the above try, tried setting the Custom date format to: UZ in hopes of taking into consideration the timezone offset.

I have a feeling that it's a casting issue from the View JobPostings: 'Deadline' date field but I have no idea how to get around this. If I add my own Datetime field, there's no problem mapping the values between sites.

This problem may be related to the JobPosting module and it's support for Views or it might be in the Publish/Subscribe module.

Just looking for any suggestions on things to try? Maybe someone else had a similar issue in the past or the future and will stumble upon this.

Thanks.