I am not sure. But should we consider getElementsInitializedAndFlattened in place of getElementsDecoded considering that the previously used function was getElementsFlattenedAndHasValue

CommentFileSizeAuthor
#6 2847658-6-use-flattened-elements.patch805 bytesandy_w
#2 use-2847658-2.patch652 bytesgokulnk

Comments

gokulnk created an issue. See original summary.

gokulnk’s picture

gokulnk commented
Status: Active » Needs review
Issue tags: +SprintWeekend2017
StatusFileSize
new use-2847658-2.patch652 bytes
grisendo’s picture

grisendo commented
Status: Needs review » Active

What are the advantadges of using getElementsInitializedAndFlattened instead of getElementsDecoded?

grisendo’s picture

grisendo commented
Category: Task » Feature request
Status: Active » Postponed (maintainer needs more info)
andy_w’s picture

andy_w commented

This is required in order to locate email fields which are nested within a fieldset (or any container element), currently only root level email fields are available as an option.

andy_w’s picture

andy_w commented
StatusFileSize
new 2847658-6-use-flattened-elements.patch805 bytes

Here is a patch for the latest release 8.x-5.3

andy_w’s picture

andy_w commented
Status: Postponed (maintainer needs more info) » Needs review
mbovan’s picture

mbovan commented
Status: Needs review » Reviewed & tested by the community

#6 seems correct and works for me.

mbovan’s picture

mbovan commented
Status: Reviewed & tested by the community » Fixed
Issue tags: -SprintWeekend2017

Committed. Thanks.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.