I am trying to set up a Webform and use the Webform MySQL Views to place the contect from a filled webform into a views calendar..

Does anybody have any tips or help?

This is the error I get, 

    The calendar_style style requires a Date argument.
    The date argument date fields must be added to this query. You can exclude them if you do not want them displayed in the calendar.

Comments

calbert’s picture

calbert commented

Any updates, this would really be a huge help for me.

cafuego’s picture

cafuego commented
Version: 6.x-1.2 » 6.x-1.x-dev
Assigned: calbert » cafuego
Category: bug » feature
Priority: Major » Normal

The patch in #1211192: Submission date database field should be unix timestamp (and now in the 6.x-dev releases) do this for the submitted field. It shouldn't be overly hard to do this for user-defined fields, provided they're defined as datetime.

cafuego’s picture

cafuego commented
Version: 6.x-1.x-dev » 6.x-2.x-dev

However, lets put that in 6.x-2.x and leave 6.x-1.x well enough alone.

cafuego’s picture

cafuego commented

Sadly dates are in fact stored as text, so this will require a views handler to interpret that text as a date. Not quite as straightforward as I'd hoped.

calbert’s picture

calbert commented

Any update cafuego ? I out of my league here getting a handler to interpret the text as date.

cafuego’s picture

cafuego commented

No, I haven't looked at it in any details yet, paid work comes first ;-)

cafuego’s picture

cafuego commented

Ok, I've found out how to properly expose webform date components to date_api, so they show up as fields. That currently works for the filter. However, it also means the field is getting rendered through Drupals format_date() and is not getting turned into a timestamp first. That leaves all date components as '1970-01-01' when displayed via views currently.

It's possible that date_api needs a patch to allow a date field to have a custom views field handler, and I think the chances of that patch getting in are probably 0 :-(