Deprecation notices

  • Resolved Kev Provance

    (@kprovance)


    6 months, 4 weeks ago

    When using this plugin with PHP 8.2, the following deprecation notice appears. It’s part of the “stringy” vendor library.

    Return type of Stringy\Stringy::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

    1. wp-content/plugins/wemail/vendor/danielstjules/stringy/src/Stringy.php:850
    2. Composer\Autoload\{closure}()
      wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php:427
    3. Composer\Autoload\ClassLoader->loadClass()
      wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php:427
    4. ReflectionClass->__construct()
      wp-content/plugins/wemail/vendor/danielstjules/stringy/src/StaticStringy.php:123
    5. Stringy\StaticStringy::__callStatic()
      wp-content/plugins/wemail/includes/WeMail.php:353
    6. WeDevs\WeMail\WeMail->include_core()
      wp-content/plugins/wemail/includes/WeMail.php:320
    7. WeDevs\WeMail\WeMail->init()
      wp-includes/class-wp-hook.php:324
    8. do_action('init')
      wp-settings.php:643
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Saiful Islam

    (@saifislam01)

    Hi @kprovance,

    I appreciate your diligence in bringing these issues to our attention. I understand the importance of resolving deprecated notice.

    Upon reviewing the error messages you provided, it appears that the weMail plugin is utilizing deprecated notice in various files. Rest assured, we take this matter seriously and are committed to addressing and resolving these issues promptly.

    I have forwarded the details to our development team, and they are currently investigating the codebase to identify and rectify the deprecated notice instances.

    If you have any further concerns, please feel free to reach out.

    Best regards,

    Plugin Support Al Rubyat

    (@rubyat13)

    Hi (@kprovance),

    Due to inactivity, we are marking this topic as resolved. Feel free to open a new one if you face any further issues.

    Thanks!

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