Bricks Forge Sentry Integration Causing 403 Errors and Data Loss in Bricks Builder

[Gborg]

Bricksforge Version: 3.1.3
WordPress Version: 6.8.2

Server Information
PHP Version: 8.2.29 (Supports 64bit values)

Web-Server: Apache

Description of the Issue / Request

Issue: Bricks Forge Sentry Integration Causing 403 Errors and Data Loss in Bricks Builder
Problem Summary:
I’m experiencing critical data loss in Bricks Builder where class IDs disappear after saving. Through debugging, I’ve identified that Bricks Forge is making failed requests to Sentry
error tracking service (returning 403 Forbidden errors), which appears to be interfering with Bricks’ AJAX save process.

Technical Details:

Browser: Chrome Version 138.0.7204.184 (Official Build) (64-bit)
Bricks Version: 1.12.5 (Latest version: 2.0.1)
Theme: Bricks Child Theme (bricks-child) v1.1
Server: Linux 6.8.0-60-generic x86_64 with Apache
Environment: Production

What’s Happening:

1. Bricks Forge is making unauthorized requests to:
   https://o109274.ingest.sentry.io/api/450653490950963…
2. These requests consistently fail with 403 (Forbidden) status
3. The failed Sentry requests appear to be interrupting Bricks Builder’s AJAX save process
4. This results in class IDs and other builder data being lost within 15 minutes of saving

Evidence:

• Browser Network tab shows repeated Sentry 403 errors when Bricks Forge is active
• When Bricks Forge is deactivated, all Sentry requests stop completely
• Class ID persistence correlates directly with Bricks Forge activation status
• No Sentry integration was manually installed - it’s being injected by Bricks Forge

Impact:
Unable to reliably save class IDs in Bricks Builder
Data loss affects client work and productivity
Makes Bricks Builder unreliable when used with Bricks Forge
How to Reproduce
Steps to Reproduce:

1. Install and activate Bricks Forge plugin on WordPress 6.8.2 with Bricks 1.12.5
2. Open Chrome browser and navigate to any page on the site
3. Open Developer Tools (F12) → Network tab
4. Refresh the page and observe failed Sentry requests with 403 status
5. Open Bricks Builder and add class IDs to any elements
6. Save the page and exit builder
7. Wait 15 minutes and return to Bricks Builder
8. Observe that class IDs have disappeared
9. Control Test: Deactivate Bricks Forge and repeat steps 2-8
10. With Bricks Forge deactivated, class IDs should persist and no Sentry errors appear

Expected Behavior:

• No unauthorized external API calls should be made
• If Sentry integration is intended, it should not fail with 403 errors
• Failed API calls should not interfere with core Bricks Builder functionality

Actual Behavior:
Continuous 403 Sentry errors in browser console
Class IDs disappear after saving in Bricks Builder
Issue resolves completely when Bricks Forge is deactivated

Let me know if there’s anything else to provide!

Pictures:

(After disabling bricksforge, it loads fine)

[manc]

Hi there

we don’t use Sentry.. any chance your site has been compromised or some other plugin is injecting calls to sentry? Long shot but maybe you tried integrating Sentry at some point and have some code left in the node editor or the legacy events panel?

Feel free to share some logins using:

if you’d like us to take a closer look

[Gborg]

Hello,
Apologies did not get a notification for this reply!

I did not nor ever used sentry but weird enough the issue went away when I disabled bricksforge. I have been checking everywhere but I can’t seem to find where this came from

for the credentials, which email should I use and what role should I provide you?

[manc]

Hi @Gborg , just tagging you to double make sure you get a notification haha.

You can use any email really since we don’t usually need to reset the password or anything but feel free to use help@bricksforge.io. As for the role we’d need admin access to be able to look around

It’s really odd since we also don’t use Sentry. Have you tried uploading a fresh downloaded copy of bricksforge?