Jump to:
| Project: | Subscribe |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I'm using the Job Posting module which creates it's own content-type - Job Posting. Might not be a great idea to have a module create the content-type, but I like this module and some of it's features. It has a field called "deadline" which is an int (10) unsigned.
When the subscribed site pulls the data, it's value is not the same as the published 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
I see most UTC dates in Drupal tables are just int (11). Not sure if this could be the issue in the Job Posting table.
All the other fields get mapped correctly between sites.
Except a filefield that I added to the content type. This patch fixed it however: http://drupal.org/node/938420#comment-3567242
Any suggest fixes or things to try would be appreciated. Thanks.
Comments
#1
- So I converted the field "deadline" in the job_posting table in both sites to be an int(11). This did not fix the issue.
- I also 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.
Kind of at a lost for ideas but will still search for the culprit.
Any suggestions feel free to post them.