Skip to content

Answer submission data is never stored in (undocumented, hardcoded) optional intended(?) form field #12

@ChemiKyle

Description

@ChemiKyle

There seems to be an intended use for a cat_mh_data field (hardcoded name, must be an element of the same form containing the record_id) to be populated with survey response data and allow continued surveys to be updated here, however there are several issues with this.

if ($curl['cookies']['JSESSIONID'] == $authValues['JSESSIONID'] and $curl['info']['http_code'] == 302) {

For the $authValues array, the jsessionid key is actually all lowercase so this if block doesn't run.
If corrected, however, there must already be data present in this field in the following format:

{
  ...
    "interviews": [
      {
        "interviewID": 42,
        "signature": "foo",
        "identifier": "bar"
      }
    ]
}

This logic hasn't actually run for about 5 years, but if it's intended to be used - rather than entriely foregone in favor of the data stored in the module log - the following steps need to be taken:

  1. cat_mh_data should be made into an optional project setting as a field-list
  2. Correct the case of jsessionid
  3. The cat_mh_data field should be initialized to allow interview data to be updated in-place

Metadata

Metadata

Assignees

Labels

wontfixThis will not be worked on

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions