Date field not showing up in views arguments in localized site

Same issue/setup here
Subscribing...

Same problem with:

ctools 7.x-1.x-dev 2011-Mar-19
views 7.x-3.x-dev 2011-Mar-21
date 7.x-2.x-dev 2011-Mar-21
calendar 7.x-2.x-dev 2011-Mar-21

ctools 7.x-1.0-alpha3

views 7.x-3.x-alpha1

date 7.x-2.0-alpha1

calendar 7.x-2.x-dev

I enabled the core Locale module but did not configure it at all.
I did not enable Content translation.

Suddenly, no events showed up in my calendar in any view.

My date field is called field_date. In Views, when I went to add it under arguments, it had two tickboxes for fields instead of one:
Fields: field_date (field_date) - value
Fields: field_date (field_date) - value2

I tried adding a new date field, but again it appeared twice.

I disabled the Locale module.
Now my calendar events appear in Month view only,
And underneath the eventname it says 'field_date' instead of displaying a date.

Edit: I just noticed that all the dates on the calendar were also moved back one day. It may be a Date issue.

Look at this: http://drupal.org/node/1101186
It's very similar problem...

subscribing

I think we have more than one problem here and probably more than one module is affected :

1-when using a different language from english, we can't select date fields in views contextual filter's
2-displaying a calender view that's working fine in english in another language will display errors like :

Notice : Undefined index: field_data_field_date_evenement.field_date_evenement_value_value dans calendar_build_nodes() (ligne 603 dans /var/www/ccqm/sites/all/modules/calendar/calendar.module).
Notice : Undefined index: field_data_field_date_evenement.field_date_evenement_value_value dans calendar_build_nodes() (ligne 613 dans /var/www/ccqm/sites/all/modules/calendar/calendar.module).

Also note that when switching languages, only events created for that language will be displayed (I guess that's normal behavior).

I've solved this problem with reloading language translation file for Views module with small modification #1103564: No CCK date fields in Contextual filters after local translation is installed

@gerhardbaumeister

My screenshots was exactly like yours. I have two date values (generated by Date Tools with Callendar)

Fields: Date (field_date) - value
Fields: Date (field_date) - value2

I prepared German *.po file for you, try it first ;-) My, Polish, is attached too.

Don't forget check option: Strings in the uploaded file replace existing ones, new ones are added. The plural format is updated.

It works: http://hdrsoft.pl/calendar-date :-)

@gerhardbaumeister
If you have a multi-language site, you will have have to create one event for each language. So if your site is in english and german, you will create two events at the same date/time but in different language (this make sense if you want to display events in different language otherwise how do you translate this?). On the other hand, maybe an option in the calendar or the view module to ignore language would help...

Attached patch solves this issue at the roots: date_views.module is the one responsible for this nasty bug.

Awsome! Patch #21 solves everything for me. Thanks!

Whoops, looks like I've forgotten to submit it to the _proper_ queue.

Makes sense to me.
Fixed: http://drupalcode.org/project/date.git/commit/37d8b38

I'm kinda confused.

I dont know what happened to the calendar view, but everytime i try to edit it I get a white page with error messages like:

Notice: Undefined property: date_views_argument_handler::$granularity in calendar_plugin_style->query()

and i cant edit the view.

I have desactivated and uninstalled the calendar and date views modules and still get these errors.

My modules versions:

Calendar: 7.x-2.0-alpha1
Date: 7.x-2.x-dev 2011-Apr-30
Views: 7.x-3.0-beta3
CTools: 7.x-1.0-alpha4

what am I missing here?

thanks

@a.luiz.n
Use the latest -dev versions. Some of those alphas and betas are more than a month old, and there have been lots of changes since then.

I'm using now the latest dev version of the 4 of them.
And when I try to edit the calendar view I get a white page. When I press the back button I got error messages like:

Notice: Undefined property: date_views_argument_handler::$granularity in calendar_plugin_style->query()

I have also unstalled views...

I dont know what's wrong.
At my local site it's working...
I dont know what's the difference... php version? database?

Hey, nevermind.
I exported the good views from my local site and imported in my production one.

Thanks =]

Works for me with modules versions:

Calendar: 7.x-1.0-alpha3
Date: 7.x-2.0-alpha1
Views: 7.x-3.0-alpha1
CTools: 7.x-1.0-alpha2

i attache the date_views/includes/date_views_fields.inc file. Just replace..
For good practice visit this tutorial:
http://www.drupaltherapy.com/date_d7

regards from germany..

I just want to confirm that in all the latest dev versions, this is still broken. I'd be happy to provide debug info, but I'm assuming it's a known issue given the attention it's being given...

subscribe

subscribing

Here is another version of data_views_field.inc file that worked for me. Almost the same as posted in 5/10. might be the upgrade?

Latest dev version of Date module still gives problems with "locale".
No custom CCK date fields show up in the views contextual filter Date fields(s).

The following line of code is the cause:

 if ($handler->definition['group'] == t('Content') && isset($handler->definition['field_name'])) {

If I check the value for $handler->definition['group'] is says 'Inhoud' (dutch translation for "Content") but although de "Content" string is translated a var_dump() of t('Content') still gives 'Content' as its translation.

I am not sure how to slove this issue.

I found out that "administration language" module is causing the problem. When selecting "Administration pages (admin) " as option, the date view breaks.

Not sure if this is a "date" or "adaministration language" issue.

I tried changing the method of identifying Field module fields in the field list to eliminate the dependency on the group name. In addition to problems with translations it might miss other field values that use different group names.