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.
Currently it doesn't return the rendered fields on the first time.
Comment | File | Size | Author |
---|---|---|---|
#14 | fix_rendered_fields_notice-1124098-14-D6.patch | 426 bytes | pdrake |
#8 | 1124098-followup.patch | 556 bytes | bojanz |
#1 | 1124098-render_fields-return.patch | 1.28 KB | dawehner |
Comments
Comment #1
dawehnerWhat about this patch.
Comment #2
dawehnerCommited to 6.x-3.x,, 7.x-3.x because it's helpful and it was useful for writing tests.
Comment #3
dawehnerUpdate status.
Comment #4
dystopianblue CreditAttribution: dystopianblue commentedThis patch is causing issues in the calendar module (see: http://drupal.org/node/1158518) when there are no results returned. I suggest adding $this->rendered_fields = array(); to line 310.
Comment #5
merlinofchaos CreditAttribution: merlinofchaos commentedPlease read what the statuses mean.
Comment #6
Steven.Pescador CreditAttribution: Steven.Pescador commentedsubscribe
Comment #7
BrightBoldsubscribe.
Comment #8
bojanz CreditAttribution: bojanz commentedJust saw this notice as well. The attached patch should do the trick.
Comment #9
dawehnerJust realized that my local php version shows strict errors but no notices. what a fail.
Thanks for providing a patch bojanz. Commited.
Comment #10
Druper CreditAttribution: Druper commentedIs it necessary to apply both patches or just #8, "1124098-followup.patch"?
Comment #11
dawehnerJust #8 but it's already in and will be in DEV at the latest tomorrow.
Comment #12
Druper CreditAttribution: Druper commentedCool, thanks.
Comment #14
pdrake CreditAttribution: pdrake commentedThe followup fix in #8 needs to be applied to 6.x-3.x-dev as well. Attached is a patch.
Comment #15
dawehnerThanks for reopening. Just committed the patch to 6.x-3.x as well.