Skip to content

Array and string offset access syntax with curly braces is no longer supported in PHP 7.4+ #61

Description

@andrewl64

WordPress v5.7.1 | Unyson v2.7.24 | PHP v8.0.5


From PHP 7.4+ (technically it was to be deprecated in PHP 5.1), array and string offset access syntax with curly braces has been deprecated. However, the Unyson backups extension seems to still use curly braces in class-fw-ext-backups-task-type-db-export.php, class-fw-ext-backups-task-type-db-restore.php, class-fw-ext-backups-task-type-files-export.php and class-fw-ext-backups-task-type-files-restore.php.

This seems to result in an "ajax errors" warning causing the backup to fail with the following errors returned when trying to Create Full Backup/Create Content Backup:

PHP message: PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /home/example/public_html/wp-content/plugins/unyson/framework/extensions/backups/includes/module/tasks/type/class-fw-ext-backups-task-type-db-export.php on line XXX" while reading response header from upstream....

PHP message: PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /home/example/public_html/wp-content/plugins/unyson/framework/extensions/backups/includes/module/tasks/type/class-fw-ext-backups-task-type-db-restore.php on line XXX" while reading response header from upstream....

PHP message: PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /home/example/public_html/wp-content/plugins/unyson/framework/extensions/backups/includes/module/tasks/type/class-fw-ext-backups-task-type-files-export.php on line XXX" while reading response header from upstream....

PHP message: PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /home/example/public_html/wp-content/plugins/unyson/framework/extensions/backups/includes/module/tasks/type/class-fw-ext-backups-task-type-files-restore.php on line XXX" while reading response header from upstream....

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions