Skip Navigation

[Resolved] Post type saving give 403

This support ticket is created 5 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

Tagged: 

This topic contains 16 replies, has 2 voices.

Last updated by Minesh 5 years, 10 months ago.

Assisted by: Minesh.

Author
Posts
#1204319

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Well - Yes, you are right.

The thing is that I tried to save "packsuppliers" on my test install but it took almost 3 minutes to save the post type but yes, I'm able to save the CPT "packsuppliers".

Other finding is that site is really slow even on localhost, I've escalated this issue to our next level support for further debug. I'll get in touch with you as soon as I know more.

#1204378

Omg!
3 min! 🙂
I beleve its wpml thats the issue with slow site...

#1205323

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Ok - so finally me as well as the next level support able to edit the post type and save it successfully on our local server.

Regarding this statement:

The thing is that I tried to save "packsuppliers" on my test install but it took almost 3 minutes to save the post type but yes, I'm able to save the CPT "packsuppliers".

=> Now, we are able to save the post type successfully within a second as we disable the Xdebug on our server that was causing the issue. As Xdebug is generally on my test server as we need that to debug the site.

Our next level support also try to check on your insstall but could not find anything that causes the 403 page error and the conclusion is the seems to be from your server.

We need your server (apache) error logs. Could you please share that so I will pass to our next level support and they will check if that helps them.

I have set the next reply to private which means only you and I have access to it.