The xml that is generated by the updates view should provide the date in timestamp format. This is causing date errors on sites that use projects from the fserver. The fix is to change the date format in the view from "long" to a "custom" format "U", i.e. a datestamp.

Comments

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented
Status: Active » Postponed

for now, postponing all all D7 issues, as the branch seems unmaintained by the initial author. PLease suggest using D6 rather for now

rtdean93’s picture

rtdean93 CreditAttribution: rtdean93 commented

@jzornig - your fix worked. Thank you.

@EugenMayer - I understand pointing people to use D6 as a stable, but many of these D7 posts are very helpful. Can I suggest not to postpone all of these issues? I we re-opened them, more help can come on in. If we keep applying these patches, our release will only get stronger. Please know - I value your contributions and appreciate your work on FServer.

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

well, iam open for any D7 release, but for a maintained one. There is, yet, no reason to have a ghost called "D7" release, being buggy, broken while the maintainer is gone "one shot approach" (we had that one already). As you can use fserver for deploying any Drupal version, so also D7, when using fserver on D6, there is yet no critical need to port to D7 (as fserver is no part of a normal drupal installation / CMS, but rather a standalone installation).

Iam sorry, i will postpone those issue - that means, i will not work on those. But i wont close them. If you want to pick up those issues and work on them - iam glad and happy.

Iam absolutely happy with a good D7 release, i just cant work on that myself.

I hope you are fine with that?