WPIntell

Source evidence

API returns 403 (Forbidden)

BlockMeister – Block Pattern Builder · support · 2022-08-08T10:27:00+00:00

BlockMeister – Block Pattern Builder plugin evidence original source source API
mixedsentiment
mediumseverity
0.84relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
kierancalv resolved
Hi Again Been trying to use the plugin with complex blocks like Gutenslider or stackable blocks. When you try to save any of these blocks the API returns 403 (Forbidden) or the block saves, but has no content. Tested on vanilla theme with no other plugins I am unable to reproduce this. I did a test on a new stock install with BlockMeister and only the two plugins you mentioned active. I was able to create and save/update/publish a block pattern with a mix of blocks of both Kadence as Gutenslider. 403 errors or often caused by errors in a network (like CDN’s e.g. Cloudflare?) or an incorrect server setup / wrong access rights, … I did a quick search on Google and found e.g. this article: https://wordpress.stackexchange.com/questions/291211/403-forbidden-with-gutenberg Maybe that applies to your situation too? Hi Guys Thanks for the reply. I don’t; think that info applies t this case really as all other plugins are working fine. I will run some tests though and see. NOTE: I did not mention Kadence however. I am using Stackable where the issue may lie. Hi Guys I figured it out thanks to your info. WordFence was uninstalled but there was the file wordfence-waf.php in the route and this was flagging the XLR request from the plugin Thanks for your help 🙂 Glad to hear that you were able to figure out what was causing the issue 🙂

Comments

4 shown
BlockMeister 2022-08-08T11:29:00+00:00

I am unable to reproduce this. I did a test on a new stock install with BlockMeister and only the two plugins you mentioned active. I was able to create and save/update/publish a block pattern with a mix of blocks of both Kadence as Gutenslider. 403 errors or often caused by errors in a network (like CDN’s e.g. Cloudflare?) or an incorrect server setup / wrong access rights, … I did a quick search on Google and found e.g. this article: https://wordpress.stackexchange.com/questions/291211/403-forbidden-with-gutenberg Maybe that applies to your situation too?

kierancalv 2022-08-08T13:12:00+00:00

Hi Guys Thanks for the reply. I don’t; think that info applies t this case really as all other plugins are working fine. I will run some tests though and see. NOTE: I did not mention Kadence however. I am using Stackable where the issue may lie.

kierancalv 2022-08-08T13:45:00+00:00

Hi Guys I figured it out thanks to your info. WordFence was uninstalled but there was the file wordfence-waf.php in the route and this was flagging the XLR request from the plugin Thanks for your help 🙂

BlockMeister 2022-08-08T16:50:00+00:00

Glad to hear that you were able to figure out what was causing the issue 🙂