Illegal string offset ‘.tag’

  • Hi there.

    We’re using version 3.6.9

    Backups have – as usual – been running fine but last night we saw the above as a warning in our log followed by an error while uploading to Dropbox. Here’s the log:

    [INFO] BackWPup 3.6.9; A project of Inpsyde GmbH
    [INFO] WordPress 4.9.10 on https://haylingcycleride.org.uk/
    [INFO] Log Level: Normal
    [INFO] BackWPup job: Daily
    [INFO] Logfile is: backwpup_log_76ba3a_2019-05-15_01-04-12.html
    [INFO] Backup file is: 2019-05-15_01-04-12_CE7VZQYP01.zip
    [15-May-2019 01:04:12] 1. Try to backup database …
    [15-May-2019 01:04:12] Connected to database xxx on xxx.db.1and1.com
    [15-May-2019 01:04:14] Added database dump “xxx.sql” with 5.06 MB to backup file list
    [15-May-2019 01:04:14] Database backup done!
    [15-May-2019 01:04:14] 1. Trying to make a list of folders to back up …
    [15-May-2019 01:04:17] Added “wp-config.php” to backup file list
    [15-May-2019 01:04:17] 217 folders to backup.
    [15-May-2019 01:04:18] 1. Trying to generate a manifest file …
    [15-May-2019 01:04:18] Added manifest.json file with 5.22 KB to backup file list.
    [15-May-2019 01:04:18] 1. Trying to create backup archive …
    [15-May-2019 01:04:18] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [15-May-2019 01:07:57] Backup archive created.
    [15-May-2019 01:07:57] Archive size is 54.04 MB.
    [15-May-2019 01:07:57] 1878 Files with 77.18 MB in Archive.
    [15-May-2019 01:07:58] 1. Try to send backup file to Dropbox …
    [15-May-2019 01:07:59] Authenticated with Dropbox of user: Hayling Cycle Ride
    [15-May-2019 01:07:59] Uploading to Dropbox …
    [15-May-2019 01:07:59] Beginning new file upload session
    [15-May-2019 01:08:10] WARNING: Illegal string offset ‘.tag’
    [15-May-2019 01:08:10] WARNING: Illegal string offset ‘.tag’
    [15-May-2019 01:08:30] Finishing upload session with a total of 54 MB uploaded
    [15-May-2019 01:08:32] ERROR: Uploaded file size and local file size don’t match.
    [15-May-2019 01:08:33] 2. Try to send backup file to Dropbox …
    [15-May-2019 01:08:33] Authenticated with Dropbox of user: Hayling Cycle Ride
    [15-May-2019 01:08:33] Uploading to Dropbox …
    [15-May-2019 01:08:34] One old log deleted
    [15-May-2019 01:08:34] ERROR: Job has ended with errors in 262 seconds. You must resolve the errors for correct execution.

    Nothing in the error log, so not a lot to go on, I’m afraid.

    I just reran the backup successfully. The archive sizes were identical so I suspect the backup was identical too (it’s not a high turnover site).

    Let me know if I can help further.

    Thanks for a really useful plugin,

    Andy

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    Hi @andyhenderson
    Could you please give me the full screenshot of your job Files tab?
    Thank you!

    Thread Starter AndyHenderson

    (@andyhenderson)

    Sure. You can get the screen shot (split over several files) from here.

    Andy

    Plugin Support happyAnt

    (@duongcuong96)

    hi @andyhenderson
    hmm, I can’t reproduce this issue, but going to forward this to our devs, will back to you tomorrow if possible.
    Thank you!

    Plugin Support happyAnt

    (@duongcuong96)

    Hi @andyhenderson
    Please enable debug log, BackWPUp -> Settings -> Logs -> Logging Level -> Debug(not translated ), run the job again and upload the log file instead of paste it in here, since the debug log file contains much more information than you can see.
    That would really help us!
    Thank you very much!

    Thread Starter AndyHenderson

    (@andyhenderson)

    Happy to do that, but the problem hasn’t happened again so it’s very unlikely that a debug run will show the error.

    Do you still want it?

    Andy

    Plugin Support happyAnt

    (@duongcuong96)

    @andyhenderson
    thank you, hmm, but not now, please give the log file when the issue happens again.
    For now, please just let debug log enabled.
    Thank you very much!

    Thread Starter AndyHenderson

    (@andyhenderson)

    Will do.

    FWIW, I had a quick look at the code and line 756 in class-destination-dropbox-api.php looks implicated:

    throw new BackWPup_Destination_Dropbox_API_Request_Exception(
	$message,
	$code,
	null,
	isset( $output['error'] ) ? $output['error'] : null

    If $output[‘error’] is not set, the exception sets a null for the error property in the exception.

    There is just one occurrence of this exception being caught at line 471 in class-destination-dropbox-api.php.

    } catch ( BackWPup_Destination_Dropbox_API_Request_Exception $e ) {
	$error = $e->getError();

	// See if we can fix the error first
	if ( $error['.tag'] == 'incorrect_offset' ) {

    If the error property is null then PHP will, I think, raise the warning message “Illegal string offset ‘.tag’” which is what we see in the log.

    If I’m right that means the above code is masking the original error and the warning message is unhelpful. Looking at the code that immediately precedes the exception throw, I think the original issue was some kind of http error which would explain why it’s intermittent.

    My suggestion would be to replace:

    isset( $output['error'] ) ? $output['error'] : null

    with

    isset( $output['error'] ) ? $output['error'] : array(".tag" => $message)

    or similar in order to get a better diagnostic.

    Hope that’s useful,

    Andy

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Illegal string offset ‘.tag’’ is closed to new replies.