PHP deprecated messages in the log

  • Resolved Vahan

    (@vahan889)


    4 months, 2 weeks ago

    hi Team,

    I checked my debug.log and see lots of these messages there:

    PHP Deprecated: Return type of Forminator_Addon_Container::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 /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 24
    PHP Deprecated: Return type of Forminator_Addon_Container::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 /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 35
    PHP Deprecated: Return type of Forminator_Addon_Container::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 /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 49
    PHP Deprecated: Return type of Forminator_Addon_Container::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 /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 56
    PHP Deprecated: Return type of Forminator_Addon_Container::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 70
    PHP Deprecated: Return type of Forminator_Addon_Container::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 132
    PHP Deprecated: Return type of Forminator_Addon_Container::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 143
    PHP Deprecated: Return type of Forminator_Addon_Container::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 154
    PHP Deprecated: Return type of Forminator_Addon_Container::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 166
    PHP Deprecated: Return type of Forminator_Addon_Container::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /…/wp-content/plugins/forminator/library/addon/class-addon-container.php on line 177

    Please check. I’m using PHP: 8.1, WP: 6.3.2, the plugin 1.15.12. It makes too hard to check other logs also.

    Thanks in advance,
    Vahan

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @vahan889

    I hope you’re well today!

    Please note that the 1.15.12 version of the plugin is very outdated. Current version is 1.32.

    The issue that you noticed was a known bug and is already fixed since 1.23.x version.

    You’d need to update the plugin.

    Note: with such a huge version jump, I’d rather suggest updating gradually ( 1.15.12 -> 1.16 -> 1.19 -> 1.21 -> 1.24.1 -> 1.26 -> current) through a few major releases to avoid other issues due to new features and data format changes meanwhile. You can try updating directly to current version instead but please make sure to have a full backup of the site at hand just in case.

    Kind regards,
    Adam

    Thread Starter Vahan

    (@vahan889)

    Hi Adam.

    Thanks for the details. By the way, I just didn’t see an update option for this plugin and thought it was the latest version.

    So thanks for letting me know.

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