Request failed with status code 403. - Forum | JoomShaper
Staff replied SP Page Builder

Request failed with status code 403.

Asked by Peter Klinke 3 years ago Last activity 1 year ago

when trying to   save pagebuilder 5 settings
PB5.06

21 replies

Paul Frankowski Senior Staff
3 years ago · edited

Hi Peter,

  1. Have you changed ACL for SPPB in Options ? It can be the only reason.

  2. Editor of that page has Super User, Administrator access or lower?

Error 403 = no access, no rights to do something.

For Example for Super User you should have

info_1313_2023.jpg

Peter Klinke Asked this

no, I don't change something. Acl is available an looks like your screen

Paul Frankowski Senior Staff
3 years ago · edited
  1. SInce when you have that problem? Since begining or after upgrade or .... ???
  2. You cannot save any page or only specific one?
  3. I need access to check, please create me a NEW user (Super User)
Paul Frankowski Senior Staff

BTW

IN SPPB 5.0.7 ACL should be fixed, it may solve your problem if it's releated.

Peter Klinke Asked this
  1. It happens since PB 5.0
  2. Only in settings
  3. see hidden content

5.07 is not available.

Peter Klinke Asked this

5.07 does not solve the issue

Peter Klinke Asked this

still no solution with 5.08!!

So PB 5.x is useless

Paul Frankowski Senior Staff

I cannot login anymore.

Peter Klinke Asked this
3 years ago · edited

login should work again.

which editors do you mean?
It is not possible to save the PB settings on this site.

Paul Frankowski Senior Staff

In both SPPB 5.x and SPPB 3.x you have access to front-end and back-end editor.

In SPPB 4.x it was only front-end editor.

Paul Frankowski Senior Staff

Username and password do not match or you do not have an account yet.

Anthony Grinblat

I cannot save my pages either. I get: "Request failed with status code 403"

Miguel

Hi there!
I found something that could work. It worked for me.
I have the same issue, but only in a few sites. All the rest works fine. So, i found that deactivating the ModSecurity in the hosting admin panel (cpanel) solves the issue.

Hope it helps

Log in to reply.