Deprecation Issues In Stripe Plugin

  • Resolved nootkan

    (@nootkan)


    3 months ago

    Seeing these deprecation issues in my debug logs and was wondering if they are related to the last update or something else?
    Checkout Plugins – Stripe for WooCommerce Version 1.10.1
    PHP 8.2
    Mysql 8.0.40
    cPanel Version124.0 (build 21)
    Apache Version2.4.62
    Architecturex86_64
    Kernel Version4.18.0-477.27.2.el8_8.x86_64

    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\CaseInsensitiveArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/CaseInsensitiveArray.php on line 44
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\CaseInsensitiveArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/CaseInsensitiveArray.php on line 57
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\CaseInsensitiveArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/CaseInsensitiveArray.php on line 34
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\CaseInsensitiveArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/CaseInsensitiveArray.php on line 51
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\CaseInsensitiveArray::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/CaseInsensitiveArray.php on line 24
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\CaseInsensitiveArray::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/CaseInsensitiveArray.php on line 29
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Util\Set::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Util/Set.php on line 40
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\StripeObject::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/StripeObject.php on line 202
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\StripeObject::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/StripeObject.php on line 212
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\StripeObject::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/StripeObject.php on line 197
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\StripeObject::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/StripeObject.php on line 207
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\StripeObject::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/StripeObject.php on line 218
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\StripeObject::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/StripeObject.php on line 422
    [25-Dec-2024 03:05:44 UTC] PHP Deprecated: Return type of Stripe\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/mywebsite/public_html/wp-content/plugins/checkout-plugins-stripe-woo/lib/stripe-php/lib/Collection.php on line 119

    • This topic was modified 3 months ago by nootkan.
    • This topic was modified 3 months ago by nootkan.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Aamir

    (@aamiribsf)

    Hello?@nootkan,

    Greetings for the day!

    I wanted to inform you that the deprecation notices you’re encountering are originating from the Stripe library used in our system and are associated with PHP version. Rest assured, our development team is actively working on addressing these issues, and the necessary fixes will be included in upcoming updates.

    In the meantime, to resolve these errors, we recommend downgrading your PHP version to 8.0. If you need assistance with this process, feel free to reach out to your hosting team—they should be able to guide you through the steps.

    Thank you for your understanding. We look forward to any feedback or further questions you may have.

    Best regards,

    Thread Starter nootkan

    (@nootkan)

    Thanks for your reply, but because my logs were filling up with 10’s of thousands of deprecation warnings a day I decided to fix them myself with the help of AI.

    Reversing back to php 8.0 wasn’t an option for me.

    I await the next update to see what else is fixed or added. Thanks for the great plugin.

    • This reply was modified 3 months ago by nootkan.
    Plugin Support Aamir

    (@aamiribsf)

    Hello @nootkan,

    Thank you for your reply and for taking the initiative to resolve the deprecation warnings. We appreciate your understanding, and we’re glad to hear you’re satisfied with the plugin overall.

    We’re working on improvements and will keep you updated with the next release. If you have any further questions or need assistance, feel free to reach out.

    Best regards,

    Hi all,
    I’m having the same problem. I also can’t go back to 8.0 because my provider doesn’t support that.
    Any news when an update will be available?

    Plugin Support Sravan Bhaskaravajjula

    (@bhshravankumar)

    Hello @wolfamri,

    Our developers are currently investigating this scenario, and they will be releasing an update soon. Unfortunately, I do not have an exact ETA to share with you at the moment, but I assure you that the update will be available shortly.

    Thank you for your patience and cooperation.

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