FieldException error when creating an office_hours field on v8.x-1.20

@anybody i am working on this.

I (maintainer) encounter the same issue after upgrading to D11.
I installed my XAMPP stack, and noticed that the database driver is now 'sqlite', instead of 'mysql' before. That was also the only option when installing the new Drupa-11 environment. No idea why the mariaDB/mySQL was not present.

The database I created in phpMyAdmin is also still empty.

What driver are you using? Core fields can be created as before.

in D10:

/*
$databases['default']['default'] = array (
  'database' => 'd10_20230821',
  'username' => 'root',
  'password' => '',
  'prefix' => '',
  'host' => 'localhost',
  'port' => '3306',
  'isolation_level' => 'READ COMMITTED',
  'namespace' => 'Drupal\\mysql\\Driver\\Database\\mysql',
  'driver' => 'mysql',
  'autoload' => 'core/modules/mysql/src/Driver/Database/mysql/',
);

in D11:

$databases['default']['default'] = array (
  'database' => 'd11_20250110',
  'prefix' => '',
  'driver' => 'sqlite',
  'namespace' => 'Drupal\\sqlite\\Driver\\Database\\sqlite',
  'autoload' => 'core/modules/sqlite\\src\\Driver\\Database\\sqlite\\',
);

OTOH, the problem is generated by changing the ldefault widget in #3495529-8: Change default widget and formatter.

In OfficeHoursItem.php, setting the default widget back to
* default_widget = "office_hours_default",
solves the problem.
But then, a following problem occurs..tbc.

"@johnv, as per #8, I have also changed the default_widget to office_hours_default, which solves the problem."
So should i create a MR with this change.
@anybody what are your suggestions?

@anybody, the issue is that default_widget = "office_hours_exceptions", but there is no widget with the ID office_hours_exceptions. The widget ID is actually office_hours_exceptions_only, so we can change it accordingly.

We have to identify the problem in this widget.

Similar problem from another module, with a fix, related to db: https://www.drupal.org/project/iconify_field/issues/3496280

Might be helpful? I'm having the same problem.

The problem is that the new default widget uses 'artificial' field definitions, that cannot not be created properly until the new fiedl definition is saved. The following patch circumvents that problem.

Thanks for your contribution.

A new release 1.21 is now released.