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.
These warnings popped at the same time. I was adding a project.
Warning: Missing argument 4 for storm_dependent_select_process(), called in /var/www/schoolyard/playground3/webroot/includes/form.inc on line 1766 and defined in storm_dependent_select_process() (line 939 of /var/www/schoolyard/playground3/webroot/sites/sandbox7.highlights.com/modules/storm/storm.module).
Notice: Undefined index: body in theme_stormproject_view() (line 125 of /var/www/schoolyard/playground3/webroot/sites/sandbox7.highlights.com/modules/storm/stormproject/stormproject.theme.inc).
Notice: Undefined index: body in theme_stormproject_view() (line 125 of /var/www/schoolyard/playground3/webroot/sites/sandbox7.highlights.com/modules/storm/stormproject/stormproject.theme.inc).
Comment | File | Size | Author |
---|---|---|---|
#3 | stormproject-1549820-addbodyfield-comment3.patch | 2.84 KB | esoteric1 |
Comments
Comment #1
dbt102 CreditAttribution: dbt102 commentedI just installed most recent dev release (Storm 7.x-1.x-dev tar.gz (224.04 KB) 2012-Oct-18) which went well. Went to create a project and noticed this error when create project page was displayed. Looks like this issue is still an issue...
Notice: Undefined property: stdClass::$has_body in stormproject_form() (line 634 of mysite/sites/all/modules/storm/stormproject/stormproject.module).
Warning: Missing argument 4 for storm_dependent_select_process(), called in mysite/includes/form.inc on line 1797 and defined in storm_dependent_select_process() (line 939 of /mysite/sites/all/modules/storm/storm.module).
Comment #2
esoteric1 CreditAttribution: esoteric1 commentedgoing to apply the same method used to patch this in stormorganization. It may also be an issue for stormperson as well. I'll create an issue.
Comment #3
esoteric1 CreditAttribution: esoteric1 commentedpatch for stormproject
Comment #4
juliangb CreditAttribution: juliangb commentedLooks like what we need from my first read-through.
Just a couple of trailing whitespace bits that could be sorted out.
Comment #5
esoteric1 CreditAttribution: esoteric1 commentedWould you mind explaining the whitespace issue so I can avoid it next time?
Comment #6
juliangb CreditAttribution: juliangb commentedFirstly I need to emphasise that this is really minor. Whitespace errors are just when there are spaces at the end of a line, or on empty lines. Drupal coding standards say we should avoid this, as it makes the code a bit cleaner.
I'd strongly recommend dreditor (https://drupal.org/project/dreditor), which is a browser plugin that helps make issue queues and issues on drupal.org a bit more user friendly. First of all, it will hide the fixed issues in a queue (useful when there is a lot of activity going on), secondly, a review button will appear by each patch. dreditor will highlight the code and show if there are whitespace issues.
BUT - I want to reiterate that it isn't a major point, so let's focus on the functionality above anything else!
Comment #7
juliangb CreditAttribution: juliangb commentedCommitted, thanks!