Closed (won't fix)
Project:
Webform
Version:
6.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Sep 2013 at 18:39 UTC
Updated:
1 Nov 2014 at 11:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
quicksketchThanks, this seems like it's a PHP 5.4 only issue, as reported here: #1760532: PHP 5.4 Warning: Illegal string offset 'month' | 'day' | 'year' in form_process_date() (line 2943 of drupal7/includes/form.inc).
I think this patch is safe, but it could probably use a comment why we're doing this. It might also cause an error in PHP 5.3 (since I don't think #value should be defined to start with), we'll need to double-check.
Comment #2
peacog commentedThe patch solves the problem for me. Thanks.
Comment #3
sonicthoughts commentedLooks good. Please consider commit to 4
Comment #4
quicksketchMarked #1760532: PHP 5.4 Warning: Illegal string offset 'month' | 'day' | 'year' in form_process_date() (line 2943 of drupal7/includes/form.inc) duplicate.
I added a comment and condition to make sure this change is safe. Not sure if this is needed in Drupal 8 or not, but moving it to be ported/reviewed.
Committed this version to 7.x-4.x.
Comment #5
fenstratCommitted to 8.x-4.x in 3e728f3. Thanks!
Given the 8.x branch isn't yet in any working condition to test this I committed this in an effort to keep the 7.x and 8.x in sync as much as possible.
Comment #7
GrantI commentedThis patch worked well for me. I'm using Drupal 7.26 and Webfrom 7.x-3.20. The file you edit is in sites>all>modules>webform>components>dates.inc
Comment #8
NaX commentedCan we also have this also committed to the 3.x branch. Upgrading to 4.x is not always desirable and the warnings also appear on the 3.x version.
Comment #10
fenstratYep fair enough. Committed and pushed to 7.x-3.x.
Comment #11
quicksketchThanks @fenstrat!
Comment #13
Jorrit commentedThe same fix also works for 6.x-3.x. Could it be pushed there as well too?
Comment #14
NaX commentedComment #15
danchadwick commentedClosing for lack of maintenance on the 6.x branch. If a maintainer for 6.x comes forward, he/she can re-open.