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.
Often, the query string (appending ?step={STEP_NAME} seems to be ignored. I have a few test environments and it is working in some sometimes, and not others at all. Can you give me a pointer as to what to look at, where to debug? I can send you whatever info you'd like, I am having the issue right now, but as you can tell, I can't reliably reproduce it.
Comment | File | Size | Author |
---|---|---|---|
#1 | manage fields.png | 128.4 KB | thatjustin |
#1 | request with query string.png | 80.55 KB | thatjustin |
Comments
Comment #1
thatjustin CreditAttribution: thatjustin commentedScreenshots attached.
Comment #2
thatjustin CreditAttribution: thatjustin commentedI spent more time on this issue, and I can reliably reproduce it now. Unlike other fields, if a node's body field is required, and has data, it still can't be skipped via the query string. That is why I saw it originally as sometimes, I was testing with body having data and empty, not realizing it was relevant. I'm fairly certain that the actual bug is in
_msnf_element_required($form, $element)
, perhaps it's recursive handling of$form['body'['und']
] but I couldn't find it precisely.I did test this out on a clean install of msnf 7.x-1.3, core 7.17, and reliably reproduced it so that whether or not the body field had data, if it was marked as required, it wouldn't be skipped when accessed via the query string method. (Unlike other fields that would be skipped if they had data, even if required)
I really like this module, it's exactly what I was looking for, hopefully this will save someone else some headache if they encounter this issue.
Comment #3
stBorchertSeems like the function
_msnf_element_required()
does not work for all field types.Currently body-fields and link fields (Link; reported in #1873604: Unable to skip fields of link type) are not handled correctly.
Comment #4
stBorchertPhew. I've committed a change which should fix this error. Tested with several field types (incl. link).
Comment #5
thatjustin CreditAttribution: thatjustin commentedDon't wait for me to test it, I don't know when I'll be able to get to it.
Comment #6
thatjustin CreditAttribution: thatjustin commentedDon't wait for me to test it, I don't know when I'll be able to get to it.
Comment #7
stBorchertCreated new release (7.x-1.4) that included this fix.