NO BUG: Admin.php error after updating to 1.9.5

After I update to latest version of bricks broken down lots of things in admin site, and cant edit any page with admin account.

Hi @simplecreative,

Could you please share temporary admin access to help@bricksbuilder.io with a link to this forum thread so we can investigate this?

Also is this a staging or production site?

Yes! It is just an “playground” site, so its not problem. :slight_smile:

I sent it now to the mail. :wink: Thanks
You will see, I turned off all of plugins, maybe its a compatiblity error but no.
I have only think, the problem maybe(???) with the WC 8.5 version?

Ah, I see :slight_smile:

Could you please try downgrading to WC 8.4.0 which is currently the official stable version: WooCommerce – WordPress plugin | WordPress.org

Screenshot 2024-01-12 at 16.39.16

WC 8.5 was rolled back: WooCommerce 8.5.0 Released — Develop with Woo

Let me know whether the issue persists.

No, i cant! :smiley:
I can only acces to my server side file manager. And I cant upload manually the 8.4 WC because it cant see. :smiley:

I will try now with 8.3.1

1 Like

Ok, I’ waiting for my hosting provider. I can edit or modify the Modsec, because I dont have permission for it.
I uploaded and overwritten the original (8.5) woocommerce plugin (to 8.3.1) in server side file manager, but the 403 error is stay here with me. :slight_smile:

Thank you for sharing access. When I logged in I was able to edit Bricks pages on your site on my end. Can you maybe try clearing your cache?

Yes! Called my hosting provider and change the options in Modsec. So now you can see again all of website.

I rolled-back to V8.4 Woocommerce, and now working everything good.

So, maybe the problem was V8.5 Woo with 1.9.5 Bricks. :wink:

Thanks for you time and support!

Awesome great to hear it’s solved :slight_smile:

1 Like

Hi charaf! (and bricks family)

Just for you information. The latest woocommerce (v8. 5.1) is same server error like was 8.5 to me. (modsec firewall)

1 Like

Hi @simplecreative,

Oh, that’s unfortunate :frowning: I hope they get to fix it in the next version. Thanks for sharing this with others.