Title: PHP 8.1 issues? Last modified: July 14, 2022 --- # PHP 8.1 issues? * Resolved [biostim](https://wordpress.org/support/users/biostim/) * (@biostim) * [3 years, 10 months ago](https://wordpress.org/support/topic/php-8-1-issues/) * When I try PHP 8.1 I get the below issues but fine on PHP 8.0 * ``` WordPress version: 6.0.1 BackWPup version: 3.10.0 PHP version: 8.1.7 (64bit) MySQL version: 10.3.23-MariaDB-cll-lve cURL version: 7.71.0 cURL SSL version: OpenSSL/1.1.1d WP-Cron url: https://gfhfggfh.com.au/wp-cron.php Server self connect: Response Test O.K. Document root: /home/gggsu/public_html Temp folder: /home/gggsu/public_html/wp-content/uploads/backwpup-67agceg3-temp/ Log folder: /home/gggsu/public_html/wp-content/uploads/backwpup-67acgeg3-logs/ Server: Apache Operating System: Linux PHP SAPI: litespeed Current PHP user: gggsu Maximum execution time: 300 seconds BackWPup maximum script execution time: 15 seconds Alternative WP Cron: Off Disabled WP Cron: Off CHMOD Dir: 0755 Server Time: 1:38 Blog Time: 11:38 Blog Timezone: Blog Time offset: 10 hours Blog language: en-US MySQL Client encoding: utf8mb4 PHP Memory limit: 768M WP memory limit: 40M WP maximum memory limit: 768M Memory in use: 115.00 MB Loaded PHP Extensions:: Core, PDO, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, bcmath, bz2, calendar, ctype, curl, date, dba, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, hash, i360, iconv, imap, intl, json, ldap, libxml, litespeed, mbstring, mysqli, mysqlnd, odbc, openssl, pcntl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, readline, session, shmop, soap, sockets, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib ``` * Part of the log is below. [INFO] BackWPup 3.10.0; A project of Inpsyde GmbH [ INFO] WordPress 6.0 on [https://fdfdgdfgm.com.au/](https://fdfdgdfgm.com.au/)[ INFO] Log Level: Normal [INFO] BackWPup job: Weekly Backup [INFO] Logfile is: backwpup_log_ef5ed9_2022-07-10_01-01-06.html [INFO] Backup file is: backwpup_TFT2ZY6R01_2022- 07-10_01-01-06.zip [10-Jul-2022 01:01:06] 1. Try to backup database … [10-Jul- 2022 01:01:06] DEPRECATED: Return type of Symfony\Component\OptionsResolver\OptionsResolver:: offsetExists($option) should either be compatible with ArrayAccess::offsetExists( mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice [10-Jul-2022 01:01:06] DEPRECATED: Return type of Symfony\Component\OptionsResolver\OptionsResolver::offsetGet($option) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice [10-Jul-2022 01:01:06] DEPRECATED: Return type of Symfony\Component\ OptionsResolver\OptionsResolver::offsetSet($option, $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 [10-Jul-2022 01:01:06] DEPRECATED: Return type of Symfony\Component\ OptionsResolver\OptionsResolver::offsetUnset($option) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice [10-Jul-2022 01:01: 06] DEPRECATED: Return type of Symfony\Component\OptionsResolver\OptionsResolver:: count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice [10-Jul-2022 01:01: 07] DEPRECATED: substr(): Passing null to parameter #1 ($string) of type string is deprecated [10-Jul-2022 01:01:07] DEPRECATED: substr(): Passing null to parameter# 1 ($string) of type string is deprecated Viewing 2 replies - 1 through 2 (of 2 total) * [happyAnt](https://wordpress.org/support/users/duongcuong96/) * (@duongcuong96) * [3 years, 10 months ago](https://wordpress.org/support/topic/php-8-1-issues/#post-15825019) * Hello [@biostim](https://wordpress.org/support/users/biostim/) Thank you for reporting the issue, the reason for this is BackWPUp currently support PHP from 5.6 to 8.0, so we also have to support old, unsupported PHP version like 5.6. In the near future, we will require a higher, more modern PHP version like > 7.4 so this issue will not happens. Will update you when I have something new, for now, I would suggest you to downgrade the site to PHP 8.0 instead for better compatibility. * Thread Starter [biostim](https://wordpress.org/support/users/biostim/) * (@biostim) * [3 years, 10 months ago](https://wordpress.org/support/topic/php-8-1-issues/#post-15826736) * Thank you duongcuong96 Viewing 2 replies - 1 through 2 (of 2 total) The topic ‘PHP 8.1 issues?’ is closed to new replies. * ![](https://ps.w.org/backwpup/assets/icon-256x256.png?rev=3236141) * [BackWPup – WordPress Backup & Restore Plugin](https://wordpress.org/plugins/backwpup/) * [Support Threads](https://wordpress.org/support/plugin/backwpup/) * [Active Topics](https://wordpress.org/support/plugin/backwpup/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/backwpup/unresolved/) * [Reviews](https://wordpress.org/support/plugin/backwpup/reviews/) * 2 replies * 3 participants * Last reply from: [biostim](https://wordpress.org/support/users/biostim/) * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/php-8-1-issues/#post-15826736) * Status: resolved