# SOLVED: Internal server error after update Bricks and Wocommerce **URL:** \ **Category:** Bugs\ **Tags:** v1-9\ **Created:** [November 14, 2024, 1:51pm UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926 "2024-11-14T13:51:29Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![pedronx](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/p/d6d6ee/32.png) [@pedronx](https://forum.bricksbuilder.io/u/pedronx)\ **Post date:** [November 14, 2024, 1:51pm UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/1 "2024-11-14T13:51:29Z")
**Browser** : chrome 130.0.6723.119 **OS** : Windows **URL** : Link to a page that illustrates this issue **Video** : [Jam](https://jam.dev/c/8ee1d1bd-008d-4e2e-b2ae-974a84c47901) Hi, after last update of Woocommerce and Bricks, some website funkcionalities are broken. 1. I see this info in admin: " **Your theme (Bricks Child Theme) contains outdated copies of some WooCommerce template files.**" 2. when i set in woocommerce settings that shop page should point to “projekty-domow”, then wp returns an error 500 internal server error BR 3. search opiton also retrun error ---
**Author:** ![Matej](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/matej/32/20184_2.png) [@Matej](https://forum.bricksbuilder.io/u/Matej)\ **Post date:** [November 14, 2024, 2:17pm UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/2 "2024-11-14T14:17:49Z")
Hi, well, the first one has already been reported and will be fixed (and released) very soon. > [@SOLVED: WooCommerce (9.4.1) outdated template files](https://forum.bricksbuilder.io/t/wip-woocommerce-9-4-1-outdated-template-files/27847): > > Browser: Chrome 131.0.6778.70, FireFox Developer 133.0b7 (64-bit) OS: macOS 15.1 WordPress: 6.7 WooCommerce: 9.4.1 PHP: 8.3.x Bricks: 1.11.1 Hi, After update WordPress (6.7) and WooCommerce (9.4.1) to latest version I got an alert: Your theme (Bricks) contains outdated copies of some WooCommerce template files. Notice from Bricks: But don't worry. Bricks regularly updates all WooCommerce template files with each new release. If you are on the latest version and see this message, any nec… About the second one, can you check debug.log, what does it say? Thanks, Matej ---
**Author:** ![pedronx](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/p/d6d6ee/32.png) [@pedronx](https://forum.bricksbuilder.io/u/pedronx)\ **Post date:** [November 14, 2024, 2:57pm UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/3 "2024-11-14T14:57:30Z")
> [@Matej](#): > > debug.log Woocommerce eroors from **WooCommerce → Status → Logi:** 2024-11-14T07:37:56+00:00 Błąd krytyczny Uncaught TypeError: array\_map(): Argument #2 ($array) must be of type array, string given in /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-query.php:2201 2024-11-14T07:37:59+00:00 Błąd krytyczny Uncaught TypeError: Cannot access offset of type string on string in /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/query.php:2079 debug.log: [14-Nov-2024 14:56:46 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/query.php:2079 Stack trace: #0 /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/database.php(268): Bricks\Query::merge\_tax\_or\_meta\_query\_vars() #1 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-hook.php(324): Bricks\Database-\>set\_main\_archive\_query() #2 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-hook.php(348): WP\_Hook-\>apply\_filters() #3 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/plugin.php(565): WP\_Hook-\>do\_action() #4 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-query.php(1881): do\_action\_ref\_array() #5 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-query.php(3852): WP\_Query-\>get\_posts() #6 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp.php(696): WP\_Query-\>query() #7 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp.php(816): WP-\>query\_posts() #8 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/functions.php(1336): WP-\>main() #9 /home/platne/serwer248030/public\_html/budujdom.pl/wp-blog-header.php(16): wp() #10 /home/platne/serwer248030/public\_html/budujdom.pl/index.php(17): require(‘…’) #11 {main} thrown in /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/query.php on line 2079 [14-Nov-2024 14:56:47 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/query.php:2079 Stack trace: #0 /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/database.php(268): Bricks\Query::merge\_tax\_or\_meta\_query\_vars() #1 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-hook.php(324): Bricks\Database-\>set\_main\_archive\_query() #2 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-hook.php(348): WP\_Hook-\>apply\_filters() #3 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/plugin.php(565): WP\_Hook-\>do\_action() #4 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-query.php(1881): do\_action\_ref\_array() #5 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp-query.php(3852): WP\_Query-\>get\_posts() #6 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp.php(696): WP\_Query-\>query() #7 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/class-wp.php(816): WP-\>query\_posts() #8 /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/functions.php(1336): WP-\>main() #9 /home/platne/serwer248030/public\_html/budujdom.pl/wp-blog-header.php(16): wp() #10 /home/platne/serwer248030/public\_html/budujdom.pl/index.php(17): require(‘…’) #11 {main} thrown in /home/platne/serwer248030/public\_html/budujdom.pl/wp-content/themes/bricks/includes/query.php on line 2079 [14-Nov-2024 14:57:12 UTC] PHP Notice: Function \_load\_textdomain\_just\_in\_time was called **incorrectly**. Translation loading for the `duracelltomi-google-tag-manager` domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the `init` action or later. Please see [Debugging in WordPress](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/) for more information. (This message was added in version 6.7.0.) in /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/functions.php on line 6114 [14-Nov-2024 14:57:30 UTC] PHP Notice: Function \_load\_textdomain\_just\_in\_time was called **incorrectly**. Translation loading for the `duracelltomi-google-tag-manager` domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the `init` action or later. Please see [Debugging in WordPress](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/) for more information. (This message was added in version 6.7.0.) in /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/functions.php on line 6114 [14-Nov-2024 14:57:35 UTC] PHP Notice: Function \_load\_textdomain\_just\_in\_time was called **incorrectly**. Translation loading for the `duracelltomi-google-tag-manager` domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the `init` action or later. Please see [Debugging in WordPress](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/) for more information. (This message was added in version 6.7.0.) in /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/functions.php on line 6114 [14-Nov-2024 14:57:42 UTC] PHP Notice: Function \_load\_textdomain\_just\_in\_time was called **incorrectly**. Translation loading for the `duracelltomi-google-tag-manager` domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the `init` action or later. Please see [Debugging in WordPress](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/) for more information. (This message was added in version 6.7.0.) in /home/platne/serwer248030/public\_html/budujdom.pl/wp-includes/functions.php on line 6114 ---
**Author:** ![pedronx](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/p/d6d6ee/32.png) [@pedronx](https://forum.bricksbuilder.io/u/pedronx)\ **Post date:** [November 15, 2024, 9:01pm UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/4 "2024-11-15T21:01:15Z")
The problem disappear after updating Bricks to latest version. Thank You. ---
**Author:** ![Matej](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/matej/32/20184_2.png) [@Matej](https://forum.bricksbuilder.io/u/Matej)\ **Post date:** [November 17, 2024, 10:31am UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/7 "2024-11-17T10:31:14Z")
Thanks for the report. I’ll mark this topic as SOLVED 🙂 ---
**Author:** ![banban](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/b/9e8a1a/32.png) [@banban](https://forum.bricksbuilder.io/u/banban)\ **Post date:** [January 16, 2025, 7:24am UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/8 "2025-01-16T07:24:37Z")
Error was discovered in Query Monitor plugin. How to improve? \_load\_textdomain\_just\_in\_time called by mistake. Translations for bricks domain loaded too quickly PHP 8.2.26 WP 6.7.1 Bricks 1.11.1.1 ---
**Author:** ![Matej](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/matej/32/20184_2.png) [@Matej](https://forum.bricksbuilder.io/u/Matej)\ **Post date:** [January 21, 2025, 3:58pm UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/9 "2025-01-21T15:58:38Z")
Hey, sorry for late reply. Can you check debug.log, and upload the log here, so I can check it? Also, make sure that when you test, you only have Bricks installed, as it’s possible that the issue is from another plugin? Matej ---
**Author:** ![banban](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/b/9e8a1a/32.png) [@banban](https://forum.bricksbuilder.io/u/banban)\ **Post date:** [January 23, 2025, 2:24am UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/10 "2025-01-23T02:24:50Z")
Okay, I’ll check it out! Bricks does not have a template to implement BBPRESS, so using Elementor at the same time may be the problem. Preferably a partial that can be used with Elementor If there is a way to implement the code on the Bricks side, you can eliminate the need for Elementor. ---
**Author:** ![Matej](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/matej/32/20184_2.png) [@Matej](https://forum.bricksbuilder.io/u/Matej)\ **Post date:** [January 23, 2025, 9:35am UTC](https://forum.bricksbuilder.io/t/solved-internal-server-error-after-update-bricks-and-wocommerce/27926/11 "2025-01-23T09:35:39Z")
Hey, > [@banban](#): > > Bricks does not have a template to implement BBPRESS I don’t have experience with BBPRESS, so, how do you implement it generally? Why would you need a template?