I can confirm it is not the formatter, when I edit the node again after saving the date is updated to the next day and continues to be updated to the next day upon each save but it is within a window 3 hours before midnight. This isn't an issue with core's date field so I don't believe it's related to a timezone configuration issue.
I am considering whether a previously closed issue might be a clue as to what is happening here:
https://www.drupal.org/project/double_field/issues/3067119 →
I would note that this is also an issue with using `drush generate field` to make a compound field. However, the issue presents itself as updating the date to the previous date on save in that case.
Some things to consider.
The real challenge seems to be determining if block_content entities need to remain coupled with block plugins.
Based on the information shared:
- Caching is tightly coupled between block_content and block plugins
- Block plugin discovery is tied to block_content creation
- Block plugins are not configurable to conditionally attach entities. There is a unique relationship with block_content and block plugins.
In response to the caching issue, do we already have an example of double-render caching for the same content in Drupal core? If so then I think the argument is invalid.
In response to the block plugin challenges, I see this as an opportunity to make the block system more configurable and dynamic for scalability and flexibility. If we make a block plugin that can conditionally attach a block_content entity (or others for that matter) then I see that increases its usefulness and meets the existing expectation. This removes the need for block discovery to be triggered on block_content creation.
This not only impacts views and references but also impacts using twig_tweak to print a block_content entity in a template. I see all of these as valid use cases and I think the increasing usage of the block_content_template module shows that it should be evaluated.
Tested and merged into 8.x-1.x-dev.
vector_ray → made their first commit to this issue’s fork.
Tested and merged into 8.x-1.x-dev
Tested and merged into 8.x-1.x-dev branch
vector_ray → created an issue.
Thank you for flagging. I've added to note to the description noting that this module is not compatible with other modules that provide similar functionality.
This seems to be a general support question about TWIG and unrelated to what this module provides.
Here is a link to documentation of working with TWIG https://twig.symfony.com/doc/3.x/. I hope that helps.
laura.gates → credited vector_ray → .
Tested! this resolved the deprecated function issue for PHP 8.2