403 error on save in elementor

Hi @sermalefico,

Thanks for reporting the issue. A 403 error typically indicates that the server is actively blocking access, usually due to permissions, security rules, or misconfigurations. Here are a few things you can check:

Check File/Folder Permissions, you can verify this via FTP or your hosting file manager, usually 755 for folders and 644 for files.

Inspect the .htaccess file, as a misconfigured .htaccess file in your WordPress folder might be causing this. Try renaming it .htaccess_backup and regenerate a fresh one via WordPress Settings > Permalinks.

Clear Browser Cache: Old browser data can sometimes trigger errors. Clear your cache or try a different browser.

Disable Firewall Temporarily: If you are using a plugin such as Wordfence, you can try disabling it temporarily.

You can also try to enable the WP_DEBUG in your wp-confing file, to check error logs for specific clues about the 403 error.

If the issue persists, I’d recommend contacting your hosting provider. Share the exact time of the error and the affected URL, they can usually pinpoint the cause in their logs.

Let me know what you find or if you need help with any of the above steps.

Best,
Dara

Hi @sermalefico,

Glad to hear you resolved the 403 error. Regarding the new pagination issue on your local site, I would a bit more info, as this could involve either the post widget or filter widget pagination. Could you clarify:

-Which widget is affected? Is it the BPFWE post widget or is it from the pagination generated by the filter widget?
-Is this happening on an archive, single page, or another CPT, and what query type was in use?
-Backend/frontend: is the issue only happen in the Elementor backend, or does it also occur on the frontend as well?

If it’s backend-specific, can you share any extra URL parameters you notice when the error occurs. This issue may happen in the backend due to URL arguments added by Elementor, but usually works fine on the live site/frontend. To test, you can check if the pagination works on the frontend, you can also try to manually remove the arguments from the URL.

Another cause for this could be a slug conflict. For example, a page named “product” and an archive slug /product/.

Let me know if you have more details, so I can help you narrow down this issue.

Best,
Dara

Hi @sermalefico,

Thanks a lot for your detailed report and the screen recording, that really helped pinpoint the problem.

After reviewing everything, I can confirm that the pagination issue you’re experiencing is related to the way the post widget handles the same-domain pagination. I use wp_safe_remote_get() to get the page content instead of the jQuery $.get(). This works well under normal conditions, but can fail silently if the request is being blocked.

This could be the case if:

• The site is behind a “Coming Soon” or “Under Construction” mode
• HTTP Basic Auth or maintenance plugins are active
• Redirects or IP restrictions are in place

Could you please try temporarily disabling anything that could potentially block access to the website (coming soon plugin, password protection, etc.), including custom functions/.htaccess rules, and then check if pagination works again?

Optionally, you could try modify the AJAX file under /inc/classes/class-bpfwe-ajax.php and replace the request block with a modified version, from line 600 to 606:

$response = wp_safe_remote_get(
	$page_url,
	[
		'cookies'     => $cookies,
		'timeout'     => 30,
		'redirection' => 3,
		'blocking'    => true,
		'headers'     => [
			'User-Agent'    => 'Mozilla/5.0 (WordPress AJAX Fetch)',
			'Cache-Control' => 'no-cache',
		],
	]
);

This version adds a custom User-Agent, allows redirects, and uses a longer timeout.

Let me know if this work for you.

Best,
Dara

Hi @sermalefico,

You’re absolutely right, in hindsight, my original pagination approach was definitely overcooked. With the filter in place, the solution was simple and will be included in the next version.

Thanks for your insightful feedback and suggestions.

Regards,
Dara