E_ERROR: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type

  • Resolved Thomas Maier

    (@webzunft)


    5 months, 2 weeks ago

    Hi there,

    nicely designed and handy plugin!

    I found a few bugs that I cannot reproduce reliably, like an additional empty question being added when duplicating a question and then saving the survey, but the big one I wanted to report here is one that broke an admin page:

    URL: wp-admin/admin.php?page=survey-maker-each-submission&survey=2

    WordPress-Version 6.8.2
    Theme: Twenty Twenty-Four (Version 1.1)
    Plugin: Survey Maker (Version 5.1.8.8)
    PHP-Version 8.2.26

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 554 der Datei /wp-content/plugins/survey-maker/admin/partials/submissions/survey-maker-each-submission-display.php verursacht. Fehlermeldung: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, string given in /wp-content/plugins/survey-maker/admin/partials/submissions/survey-maker-each-submission-display.php:554
    Stack trace:
    #0 /wp-content/plugins/survey-maker/admin/partials/submissions/survey-maker-each-submission-display.php(554): in_array('0', 'Vielseitige Auf...')
    …

    Basically, I cannot review a single submission in some cases. I think, this happens when I made a change to the survey and the format of the answer is different.

    Thanks,
    Thomas

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Jasmine

    (@hyenokian)

    5 months, 2 weeks ago

    Dear @webzunft,

    Thanks for the topic and kind words.

    I am sorry for the problem you are experiencing.
    I have already opened a ticket as per your request, so our Dev Team can fix the issue in the upcoming update of the plugin.
    I will let you know once the update with the fix is released.

    Until then, please contact us via this form. Our customer care specialists will provide you with the fixed zip file for the case as soon as possible.

    Thank you.

    Plugin Support Jasmine

    (@hyenokian)

    4 months, 3 weeks ago

    For other readers, we would like to inform that the given case has been already fixed in the 5.1.8.9 version of the plugin.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.