Issue after Updating to Version 3.11.0 – Undefined array key “post_type”

  • Resolved msmitka

    (@msmitka)


    10 months, 1 week ago

    Description:
    After installing the latest update (version 3.11.0), I encountered a warning message in the admin interface. The warning is as follows:

    vbnet
    Copy code
    Warning: Undefined array key “post_type” in /var/www/html/wp-content/plugins/thirstyaffiliates/Models/Affiliate_Links_CPT.php on line 252
    Warning: Cannot modify header information – headers already sent by (output started at /var/www/html/wp-content/plugins/thirstyaffiliates/Models/Affiliate_Links_CPT.php:252) in /var/www/html/wp-admin/includes/misc.php on line 1431
    Warning: Cannot modify header information – headers already sent by (output started at /var/www/html/wp-content/plugins/thirstyaffiliates/Models/Affiliate_Links_CPT.php:252) in /var/www/html/wp-includes/functions.php on line 7049
    Warning: Cannot modify header information – headers already sent by (output started at /var/www/html/wp-content/plugins/thirstyaffiliates/Models/Affiliate_Links_CPT.php:252) in /var/www/html/wp-admin/admin-header.php on line 9
    This warning appears to be related to an undefined array key “post_type” in the file Affiliate_Links_CPT.php at line 252 within the ThirstyAffiliates plugin. Additionally, it triggers header modification issues across various files.


    Expected Behavior:
    No warning messages should be displayed in the admin interface, and the plugin should function as expected.

    Additional Information:

    WordPress Version: 6.4.2
    ThirstyAffiliates Version: 3.11.0
    PHP Version: 8.0.28
    Thank you for addressing this issue promptly. Let me know if you need any further information.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Caseproof

    (@caseproof)

    Hi @msmitka,

    The messages you are seeing are warnings, not errors, so they shouldn’t cause any issues.

    You can disable WP_DEBUG to hide the message from appearing.

    Are you having any issues with the plugin’s functionality?

    @caseproof
    We have this warning too.
    Warnings shouldn’t be ignored and disabling WP_DEBUG doesn’t solve the cause of the problem.
    When can we expect a fix here? Is there a workaround?

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.