Facing Deprecated error

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support omnisendsupport

    (@omnisendsupport)

    Hi @muzammilshaikh,

    Thank you for bringing this to our attention and for sharing your issue on the WordPress Support Forum. Reporting such cases here is incredibly valuable — not just for us to address potential issues, but also for the broader community to find solutions if they encounter similar ones.

    Please allow me to loop in the relevant team so they can investigate this further based on the details and screenshots you’ve provided. I’ll follow up with their findings as soon as possible. We appreciate your patience and will aim to get back to you at the earliest.

    In the meantime, if you have any additional details that might help, please feel free to share them.

    Plugin Support omnisendsupport

    (@omnisendsupport)

    Thank you for your patience. I’d like to provide an update regarding the issue you reported.

    After investigating, we’d like to clarify that there’s no immediate issue affecting functionality. The errors you’re seeing when activating the plugin are due to the use of some outdated PHP features. While this may appear concerning, rest assured that it does not impact the performance or security of the plugin.

    That said, we acknowledge the importance of keeping our code up to date. These oudated PHP features will be addressed in future versions, and we are planning a fix for the upcoming week.

    In the meantime, you can continue using the plugin without any concerns. If you have any questions or need further assistance, we’re always here for you – 24/7, 365 days a year.

    Plugin Support omnisendsupport

    (@omnisendsupport)

    After further investigation, we’ve determined that this issue is not directly caused by our plugin but rather stems from an internal WordPress component. Specifically, we found a related issue documented on Jetpack’s GitHub, indicating that this is a known occurrence.

    If you’d like to check out the related discussion, you can find it here: https://github.com/Automattic/jetpack/issues/37298

    Our plugin’s activation appears to trigger these errors, but it is not the root cause. Given this, we want to confirm that there’s nothing on our end that requires a fix.

    If you have any further concerns or need assistance with anything else, please feel free to let us know — we’re happy to help!

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