# Website having issues on update to PHP 8.0 **URL:** \ **Category:** Application Support\ **Created:** [March 24, 2023, 11:28am UTC](https://community.kinsta.com/t/website-having-issues-on-update-to-php-8-0/2162 "2023-03-24T11:28:38Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![aghosby](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/aghosby/32/1835_2.png) [@aghosby](https://community.kinsta.com/u/aghosby)\ **Post date:** [March 24, 2023, 11:28am UTC](https://community.kinsta.com/t/website-having-issues-on-update-to-php-8-0/2162/1 "2023-03-24T11:28:38Z")
Hello, Please I have an issue with my website. > **[Baumaschinen Vermietung & Verkauf l Schimanski GmbH](https://schimanski-gmbh.de/)** > > Die Schimanski GmbH ist Ihr Experte für die Vermietung und den Verkauf von Baumaschinen in München, Hamburg und Rostock. Baumaschinen jetzt schnell mieten. The error below is shown when I try to access it. Please I need help with this as I’m not able to figure out why this happens. it works well on PHP 7.4 but that is deprecated now on DevKinsta so I need to fix this issue and do not know how else to fix it. I will appreciate the help. Thanks. * * * \*2023/03/24 11:02:39 [error] 84242#84242: _4549 FastCGI sent in stderr: "PHP message: PHP Warning: Constant DAAN\_LICENSE\_ENC\_KEY already defined in /www/schimanski\_324/public/wp-config.php on line 6PHP message: PHP Warning: Constant WP\_DEBUG already defined in /www/schimanski\_324/public/wp-config.php on line 77PHP message: PHP Warning: file\_exists(): open\_basedir restriction in effect. File(/www/schimanski\_324./restrictions.php) is not within the allowed path(s): (/www/schimanski\_324/public:/www/schimanski\_324/mysqleditor:/www/schimanski\_324/web:/www/schimanski\_324/deploy:/www/schimanski\_324/deployment:/www/schimanski\_324/deployments:/usr/share:/tmp) in /www/schimanski\_324/public/wp-content/themes/schimanski/inc/default.php on line 5PHP message: PHP Warning: Array to string conversion in /www/schimanski\_324/public/wp-content/themes/schimanski/inc/default.php on line 68PHP message: PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /www/schimanski\_324/public/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-repeater.php:605_ ---
**Author:** ![Alessandro](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/alessandro/32/2310_2.png) [@Alessandro](https://community.kinsta.com/u/Alessandro)\ **Post date:** [March 24, 2023, 12:21pm UTC](https://community.kinsta.com/t/website-having-issues-on-update-to-php-8-0/2162/2 "2023-03-24T12:21:27Z")
Hello @aghosby , As this looks to be related to a live site in Kinsta, please reach out to our support via chat or via mail at [support@kinsta.com](mailto:support@kinsta.com). From what I see in the error, it seems that the version of _advanced-custom-fields-pro_ you are using might not be compatible with PHP 8.0. Regards, Alessandro ---
**Author:** ![aghosby](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/aghosby/32/1835_2.png) [@aghosby](https://community.kinsta.com/u/aghosby)\ **Post date:** [March 24, 2023, 2:54pm UTC](https://community.kinsta.com/t/website-having-issues-on-update-to-php-8-0/2162/3 "2023-03-24T14:54:15Z")
Hello Alessandro, I thought same too that it was the advanced-custom-fields-pro plugin but I updated it to the latest version but the error still persists so that’s my major concern now. I’ve tried to fix but no way out so far and when I go to support via chat, I am redirected to the forum. Not sure how I can fix this again. Thanks. ---
**Author:** ![Alessandro](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/alessandro/32/2310_2.png) [@Alessandro](https://community.kinsta.com/u/Alessandro)\ **Post date:** [March 24, 2023, 3:54pm UTC](https://community.kinsta.com/t/website-having-issues-on-update-to-php-8-0/2162/4 "2023-03-24T15:54:07Z")
Hi, I’ve asked one of our colleagues to reach out to you via email. It seems that the wrong option was selected when the chat was opened and our bot closed the conversation after sending a message. Please reply to my colleague’s email, they will be happy to review the issue on your live site. Regards, Alessandro