Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Got a WSOD and the above fatal error when saving a node.
Apparently there have been some changes in Date API.
Patch fixes the problem for me.
Comment | File | Size | Author |
---|---|---|---|
#2 | date_popup_authored-README.patch | 302 bytes | pillarsdotnet |
date_popup_authored-dateapi.patch | 713 bytes | pillarsdotnet | |
Comments
Comment #1
Mark TrappJust tested with Drupal core's latest HEAD and Date's latest HEAD and not seeing the problem. Additionally, all tests pass. There's no reason why
DateObject::createFromFormat
would stop working:DateObject
extendsDateTime
.So I have a few questions to see if we can resolve this:
Comment #2
pillarsdotnet CreditAttribution: pillarsdotnet commentedYou're right; it wasn't a Date API change. I didn't realize that createFromFormat was a DateTime method, so when I grepped for it and came up empty, I assumed that it wasn't supported anymore. Knee-jerk reaction from running bleeding-edge software.
(looking...)
Hmm... I've also been getting sporadic "Call to undefined function user_access()" so it may be an out-of-memory issue. Dunno.
You might want to mention in your REQUIREMENTS section that your module requires PHP 5.3.0 or later. I know it's recommended for Drupal 7, but it isn't required just yet.
Comment #3
Mark TrappAh, I didn't catch that
DateTime::createFromFormat
was PHP >= 5.3.0. That's reason enough for me to implement the change from your first patch: does the same thing, all tests pass, and PHP 5.2 support should be back. Patch in OP is committed.