getValue() does not return all values when preprocessing

There is a cut off date in the field / formattersettings. Please check if this days value is large enough.

@johnv thank you for your reply.
There doesn't seem to be anything in the field settings that would allow me to adjust the cut-off date for office hours. See image →
I do see I can change the cut-off date for exceptions in the field widget when managing the display, but unable to set the default when just trying to get all the raw values in hook_preprocess_node.

It seems to be coming from office_hours/src/Plugin/Field/FieldFormatter/OfficeHoursFormatterBase.php line 79

     'exceptions' => [
        'restrict_exceptions_to_num_days' => 7, // Change this to a higher number can get more exceptions
        'date_format' => 'long',
        'title' => 'Exception hours',
      ],

That then gets called in web/modules/contrib/office_hours/src/OfficeHoursFormatterTrait.php line 6

// Remove excessive exception days.
$this->keepExceptionDaysInHorizon($settings['exceptions']['restrict_exceptions_to_num_days'] ?? 0);

Appreciate your help

I solved the problem. The solution will be in the following commit.

For my understanding:
"Would like to get all the values of an office hours field so I can preprocess the data before it hits the front end"
The module already provides several formatters to hand the field data to theming.
>Why do you need the virgin data? It seems you are bypassing the formatters completely?
>Can you explain what you are doing?

You use hook_preprocess_node(). There you can find the data in $variables['elements'][FIELD_NAME]['#items']
> Could you not better use hook_preprocess_field()? There you can find the data in $variables['element']['#items']
You can use office_hours_preprocess_field() as a template.

Johnv,
Sorry for the late reply. I was able to solve my problem.

Answers to your questions.
>Why do you need the virgin data? It seems you are bypassing the formatters completely?
>Can you explain what you are doing?

We needed to create a separate table on the front end for regular hours and another for exceptions and do some cleanup to the way data is presented.

There didn't seem to be an easy way to separate regular hours vs exceptions.

This is what we ended up doing to create a separate array for regular hours and exceptions. The OfficeHoursDateHelper helped a ton!

use Drupal\office_hours\OfficeHoursDateHelper;

if (isset($node)) {


  if (_field_check($node, 'field_open_hours')) {
    $open_hours_data = $node->get('field_open_hours')->getValue();
    $days_of_week = [
      0 => 'Sunday',
      1 => 'Monday',
      2 => 'Tuesday',
      3 => 'Wednesday',
      4 => 'Thursday',
      5 => 'Friday',
      6 => 'Saturday',
    ];
    $open_hours_days_of_the_week = [
      'Sunday' => [],
      'Monday' => [],
      'Tuesday' => [],
      'Wednesday' => [],
      'Thursday' => [],
      'Friday' => [],
      'Saturday' => [],
    ];
    $open_hours_exception = [];

    foreach ($open_hours_data as $item) {
      $start = OfficeHoursDateHelper::format($item['starthours'], 'Hi');
      $end = OfficeHoursDateHelper::format($item['endhours'], 'Hi');
      $day = $item['day'];
      $item['starthours'] = date("g:i A", strtotime($start));
      $item['endhours'] = date("g:i A", strtotime($end));
      if (!_is_exception_day($item)) {
        $open_hours_days_of_the_week[$days_of_week[$day]][] = $item;
      }
      else {
        $open_hours_exception[$day][] = $item;
      }
    }

    // Reg hours
    if (!empty($open_hours_days_of_the_week)) {
      $variables['location']['open_hours_days_of_the_week'] = $open_hours_days_of_the_week;
    }

    // Exceptions. Limited by the display widget "Restrict exceptions display to x days in future".
    if (!empty($open_hours_exception)) {
      $variables['location']['open_hours_exception'] = $open_hours_exception;
    }
  }
}

These issues seem to have the same request:
💬 getValue() does not return all values when preprocessing Fixed
✨ Separate list of exception days? Closed: works as designed

Thanks for the info.

Automatically closed - issue fixed for 2 weeks with no activity.