5.5.1 many code errors during FTP upload

  • Resolved MrPeteH

    (@mrpeteh)


    5 months, 3 weeks ago

    • The following log errors showed up during an FTP upload in a backup job. version 5.5.1
    • Brand new job set up. Upload is to my own server. PASV and TLS/SSL.
    • I see various other issues, both obvious and subtle. We can deal with those later. These appear to be killer,I realize they all say DEPRECATED, but the end result is a nonfunctional upload. BackWPup thinks the upload worked. It did not.
    • I’ll mention one rather obvious bug: while this job was active, showing a progress bar, I clicked to see the log. It showed me a log for a previous job. Somehow, job ID’s are getting quite confused. (I suggest use of a unique ID, rather than reusable count-from-1 ID’s 😉 )
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Cookie_Jar::offsetSet($key, $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
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $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
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
    [22-Oct-2025 23:45:38] DEPRECATED: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated

Viewing 1 replies (of 1 total)
  • Plugin Support Saransh

    (@saranshwpm)

    5 months, 3 weeks ago

    Hi there,

    Thanks for the detailed report. Could you please check if the same issue happens when:

    • You back up only the database, and
    • You set the backup destination to “Website Server” instead of FTP?

    This will help confirm if the issue is specific to the FTP step.

    Also, since those “deprecated” messages are PHP notices, please make sure WP_DEBUG is set to false in your wp-config.php file so they don’t interfere with the backup process.

    Let me know how it goes after trying these steps.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.

Tags