Views Integration for datetiem_range_timezone module

Created on 15 February 2019, about 6 years ago
Updated 31 January 2024, over 1 year ago

This module needs views integration. Existing views making use of this Datetime Range Timezone fields use the default string plugins instead of the date/time plugins making it impossible to filter (e.g. date/time relative values and offset) on this field. I will follow up with a patch to fix that.

✨ Feature request
Status

Needs work

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States jumoke

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • πŸ‡§πŸ‡ͺBelgium joevagyok
    +++ b/datetime_range_timezone.views.inc
    @@ -0,0 +1,24 @@
    +  $data = datetime_type_field_views_data_helper($field_storage, $data, 'end_value');
    

    This variable assignation is not necessary.

  • @joevagyok opened merge request.
  • Status changed to Needs work about 2 years ago
  • πŸ‡§πŸ‡ͺBelgium joevagyok

    Needs tests.

  • It works for me. Thank you very much.

  • πŸ‡§πŸ‡·Brazil henrique-liduario

    August 14th at 1:00 PM in Los Angeles corresponds to August 14th at 9:00 PM in Lisbon. I created an event with the Los Angeles timezone (August 14th at 1:00 PM). When rendering this node on the website, a user in Lisbon needs to see the event datetime as August 14th at 9:00 PM, not August 14th at 1:00 PM. Does this Drupal module automatically handle this? Does it render the information already converted in the node?

Production build 0.71.5 2024