Home › Forums › WoodMart support forum › Fatal error: Uncaught Error: Unsupported operand types: string
Fatal error: Uncaught Error: Unsupported operand types: string
- This topic has 10 replies, 2 voices, and was last updated 1 year, 9 months ago by Artem Temos.
-
AuthorPosts
-
March 13, 2023 at 12:01 pm #450659
Cioppi88ParticipantAfter Elementor update my customo layout archive template are destroyed.
Please take a look to the error log:Uncaught Error: Call to undefined function is_shop() in /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-content/themes/woodmart/inc/integrations/woocommerce/template-tags.php:297
Stack trace:
#0 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-includes/class-wp-hook.php(308): woodmart_woo_wrapper_start()
#1 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#2 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-content/themes/woodmart/single-woodmart_layout.php(20): do_action()
#4 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-includes/template-loader.php(106): include(‘/home/885114.cl…’)
#5 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/wp-blog-header.php(19): require_once(‘/home/885114.cl…’)
#6 /home/885114.cloudwaysapps.com/mwagefnprm/public_html/index.php(17): require(‘/home/885114.cl…’)
#7 {main}
thrownThis happens using layout builder on specific archive
- This topic was modified 1 year, 9 months ago by Cioppi88.
March 13, 2023 at 12:34 pm #450668
Cioppi88ParticipantThe problem is related to php 8.0.
Can you test template with new php version?
I solved downgrading version to 7.4March 13, 2023 at 3:44 pm #450734
Artem TemosKeymasterHello,
Please, upgrade PHP to the latest version you need and disable all 3rd party plugins temporarily so we can check this problem.
Kind Regards
March 13, 2023 at 7:14 pm #450810
Cioppi88ParticipantIt’s a production website and I can estroy the site again.
Can you test on your hand?March 14, 2023 at 10:04 am #450942
Artem TemosKeymasterHello,
Yes, we tested our theme with PHP 8.0 and 8.1 and didn’t see this error. Maybe it happens because of certain configurations on your website. That is why we need to check it on your end.
Kind Regards
March 14, 2023 at 12:15 pm #450980
Cioppi88ParticipantStep to reproduce the issue on your hand.
1- Create a product Attribute and enable option “as archive”
2- Create a Layout Template for this specific attribute
3- upload the template attached in order to test my layout
4- go to this archive and you’ll see fatal error caused from php 8March 14, 2023 at 1:09 pm #450996
Artem TemosKeymasterHello,
We tested this with our predefined layouts and it works well. Check our screenshots
https://gyazo.com/e3ae1f741907285022d57eee3cd1cae6
https://gyazo.com/e1d82820dc80e170dab90d195d693671
https://gyazo.com/3022edca0ac5b68425d12a5cc3828e04
https://gyazo.com/c86949511a417c1f59fbb997bd1b51b6Kind Regards
March 14, 2023 at 1:46 pm #451024
Cioppi88ParticipantTry to use your elementor widget to show grid of product and select your attribute to filter product query
March 14, 2023 at 3:24 pm #451067
Artem TemosKeymasterYou don’t need to set a filter for the product archive element. Products will be filtered automatically based on the attribute page you visited.
March 14, 2023 at 3:50 pm #451083
Cioppi88ParticipantYou are right but I give you more context.
I customize this attribute in order to be hierarchical, then I have more than one product widget with different queries based on child attributes.March 15, 2023 at 10:50 am #451282
Artem TemosKeymasterDo you mean that you create different layouts per your attribute term? Anyway, we need to see this on your website in order to understand what this problem is caused by.
Kind Regards
-
AuthorPosts
- You must be logged in to create new topics. Login / Register