I am reporting a bug in version 2.2 that affects a standard WordPress installation using WPML. My site is behind a Cloudflare Proxy, and the default language is German.
Since updating to Bricks 2.2, attempting to edit specific pages (for example, a page with the slug /dev2/) via ?bricks=run triggers a 302 redirect from the German version to the English translation. If the redirect is not executed, the builder fails with an “Invalid post type” error instead.
This issue is completely resolved by rolling back to Bricks 2.1.4, which works perfectly with the exact same server, WPML, and Cloudflare configuration. It appears that version 2.2 has introduced a bug in how it validates page URLs or Nonces behind a proxy, leading WPML to incorrectly trigger a language redirect during the builder’s loading process.
Please let me know if you need system information or staging access to investigate why version 2.2 is failing to resolve these page paths correctly while 2.1.4 has no issues. I hope you can help me with this.
Hi Anton,
Thanks so much for your report, and welcome to the forum!
Yes, that’d be great. Please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.
thank you for the offer to investigate! In the meantime, I have already been in contact with support and received a patched .zip version that completely resolved the issue.
This confirms that it was indeed a bug in version 2.2 regarding the path/URL resolution in my specific environment. I am currently waiting for a more technical explanation of what exactly caused the conflict so I can share the solution here for the community.
I’ll update this thread once I have those details. For now, the login credentials are no longer needed.
I have an update from support. It turns out the issue wasn’t directly related to Cloudflare, but is actually a bug in version 2.2 caused by a patch code from the 2.2-rc version. The patched .zip version I received fixed the 302 redirects and the invalid post type errors immediately. Support confirmed that this fix will be included in the next stable release. Since the patch works perfectly, no further investigation is needed.
Thanks for the help, I hope this information is useful for others facing similar issues.