NO BUG: Bricks builder slowing custom code in child theme

Bugs
1

We created some code for a client that manages their supplier data and populates their WooCommerce catalogue:

The code is loaded via a child theme and uses Server Side Events to work through the data (which includes many thousands of records).

The code itself creates products including:

  • The download and set up of images
  • The categorisation of the products
  • The setup / allocation of attributes and creation of variations

The original development was done on a test site using the Divi theme, but we have since moved over to Bricks as we felt it would help us create much better performing websites.

However, the processing time is drastically different when run via a Bricks child theme.

I’ve tried loading Bricks onto the original site, along with a Bricks child theme, and the processing immediately slows, indeed it doesn’t recover even if I remove Bricks, which is kind of odd.

Indeed following the removal of Bricks, we tried restoring a previous backup, which we had done many times during test, but we did not get the previous performance back.

Indeed and when trying to reactivate the Divi child theme we found ourselves redirected to /wp-admin/admin.php?page=bricks with the error - Sorry, you are not allowed to access this page.

We were then able to hit back and reactivate the Divi child theme but we do not get the previous performance back.

I plan to rebuild from scratch using Divi, just to double check, but I am really concerned about what Bricks ‘seems’ to be doing to our code’s performance, and what is left behind even when I remove the theme.

Any thoughts/feedback would be most welcome

[Please describe this bug in as much detail as possible so we can replicate & debug this bug]

2

Hello @alexpetrie,

first, welcome to the community. :partying_face:

To sum up your testing: You had a Divi website, that you moved over to Bricks. After that, you noticed a slower process time. You thought it might be Bricks, so you reverted back to Divi, even restored from an old backup (with no data from Bricks), but the performance was still slow.

I don’t see how this could be caused by Bricks, especially because it was slower with even no Bricks activated.
I don’t know how your code works, but my first thought was caching, database, or networking issue.

If there are high resource usages, maybe there is some deadlock somewhere, and you could try restarting your php container/environment, depending on the setup.

Best regards,
Matej

1 Like
3

Hi Matej,

It did not make sense to me that Bricks would be effecting our code, however, it was processing 25 records in 8 seconds when running the Divi theme, but this increased to 57 seconds for the same 25 records with Bricks Loaded.

I have just loaded our child theme onto a fresh WordPress install with the Storefront theme loaded, and the same 25 records took 5 seconds

I don’t understand why loading Bricks, and switching from Bricks left a lasting problem with the execution time, but I’m parking that for now.

I plan to try loading our child theme onto a fresh WordPress install with Bricks again, to see if that helps. I will let you know how I get on

4

Hi @alexpetrie,

thank you for your response.

Yeah, it does not make sense for this to happen, but let me know of your testing.

Best regards,
Matej

5

So I installed a fresh copy of WordPress, Bricks and WooCommerce (I also installed All-in-One WP Migration along with the Unlimited extension, as we do with all of our sites)

I then uploaded our child theme, ran the data import (which configures everything ready to start creating the catalogue), and hit import products and it seems to be running just as well – importing 25 Products in 5 seconds

I’m confused, but I guess relieved.

I can only assume something went wrong on my test setups, so plan to keep a close eye on things.

Thanks so much for responding to my post, if nothing else it forced me to retest everything from scratch (and certainly not rely on restoring backups).

Thanks (So glad it’s not a Bricks issue)

6

Hi,

thank you @alexpetrie for your response and the results of the tests. I’m glad that it’s working now fine, and that it’s not Bricks issue.

In that regard, I’ll mark the topic as no bug.

Thank you.
Matej