HomePage › Forums › Themes Support › Umimo – Furniture Store WordPress Theme › Theme Installation
- This topic has 1 reply, 2 voices, and was last updated 1 year, 2 months ago by Billy Nguyen.
-
AuthorPosts
-
February 16, 2023 at 11:29 am #31860joeySupport Expired
https://stonesy.de/produkt/intelligent-copper-watch/
We see errors in backend and frontend after installation.
Warning: Trying to access array offset on value of type bool in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/woocommerce/includes/wc-template-functions.php on line 1592
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Cookie/Jar.php on line 63
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Cookie/Jar.php on line 73
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Cookie/Jar.php on line 89
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Cookie/Jar.php on line 102
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Cookie/Jar.php on line 111
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
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 in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/Voucher/MaybeDisableGateway.php on line 27
Warning: Cannot modify header information – headers already sent by (output started at /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/Voucher/MaybeDisableGateway.php:27) in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-admin/includes/misc.php on line 1416
Warning: Cannot modify header information – headers already sent by (output started at /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/Voucher/MaybeDisableGateway.php:27) in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/functions.php on line 6865
Warning: Cannot modify header information – headers already sent by (output started at /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/Voucher/MaybeDisableGateway.php:27) in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-admin/admin-header.php on line 9
Warning: Cannot modify header information – headers already sent by (output started at /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/Voucher/MaybeDisableGateway.php:27) in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/option.php on line 1138
Warning: Cannot modify header information – headers already sent by (output started at /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-content/plugins/mollie-payments-for-woocommerce/src/Gateway/Voucher/MaybeDisableGateway.php:27) in /var/www/vhosts/stonesy.de/stonesy.de/httpdocs/wp-includes/option.php on line 1139
February 16, 2023 at 2:42 pm #31911Hi,
Some errors are caused by your Mollie-Zahlungen für WooCommerce plugin, some are related to wordpress core, need to be updated to avoid errors.
In addition, I also turned off wp debug so that the error messages do not display outside the frontend -
AuthorPosts
You must be logged in to reply to this topic.