Hi Couchies!

I have a problem with ckeditor. when i add a clonable page, that have richtext, and save it, it will bring me to 403 page. It only hapn if i have a image inside ckeditor, if it only plain text, it result ok. Any trick to solve this? Thx.

[KK]

Hi,

Please run a search through this forum for the term 'suhosin' - you'll get several threads reporting similar issues. I think the reason for your case is also the same as explained there.

Hope it helps,

Hi,

Please run a search through this forum for the term 'suhosin' - you'll get several threads reporting similar issues. I think the reason for your case is also the same as explained there.

Hope it helps,

Thx for the answer KK.
I already check my php version, and yes, it was suhosin enabled. I already uncheck the suhosin, but i stil got the same 403 page, when save a page with image on ckeditor. Any sugestion?

Capture.PNG (44.73 KiB) Viewed 3707 times

[KK]

It has to be something server side - have you restarted your web server after disabling suhosin?
The change won't take effect otherwise.

It has to be something server side - have you restarted your web server after disabling suhosin?
The change won't take effect otherwise.

Sorry for late reply KK. I have a bad problem with internet connection this month.

As like you said to restart the webserver, i did. You can see it on attachment, its suhosin disabled, if enabled it will shown like : "Suhosin v0.9.35,%20 Copyright (c) 2007-2014, by SektionEins GmbH bla bla bla....,"

I still recieved 403 after hit save button on my clonable page at ckeditor.

Capture.PNG (21.83 KiB) Viewed 3684 times

[KK]

As I said, GoingMarryAsap, the reason is somewhere before the request reaches Couch.
Not sure if I'll be able to help but you can PM me the access creds (FTP+Couch) and I'll take a look at the problem myself.

Thanks.

As I said, GoingMarryAsap, the reason is somewhere before the request reaches Couch.
Not sure if I'll be able to help but you can PM me the access creds (FTP+Couch) and I'll take a look at the problem myself.

Thanks.

PM sent KK. Thx

[KK]

Thanks @GoingMarryAsap,

I tested the problematic template (as informed by you) by adding images to CKEditor of existing pages as well as creating a new page (it is still there in unpublished state) and couldn't get the 403 error. The pages saved perfectly every time.

Is there any particular image you are trying to save that triggers the error?
If not then please try using a different browser - perhaps some addon in your browser is messing up the posting process (I remember encountering this once).

Let me know how it goes.

Thanks @GoingMarryAsap,

I tested the problematic template (as informed by you) by adding images to CKEditor of existing pages as well as creating a new page (it is still there in unpublished state) and couldn't get the 403 error. The pages saved perfectly every time.

Is there any particular image you are trying to save that triggers the error?
If not then please try using a different browser - perhaps some addon in your browser is messing up the posting process (I remember encountering this once).

Let me know how it goes.

Thx KK. Already try with 3 different browsers, and empty cache. Already try with the same image that you use to test page, even with new uploaded image. I try to revert back the upload dir to default couch upload dir, and upload new image on it, but it still result 403. It will saved, if i create new news without any image on ckeditor, and save it, and then edit it to insert image. One more strange thing, i have another ckeditor that handle my homepage, its saved with image on ckeditor. Maybe this problem only hapn with clonable page?

Thx KK.

[KK]

That is very strange @GoingMarryAsap.

As you saw for yourself, I had no problem in creating pages with images in CKEditor.
I tried yet again and could save (with images) the test page you created without a hitch.

So, my problem is that I am unable to recreate the error you are experiencing and so have no way of knowing what could be causing it

I can only shoot arrows in the dark. My new try would be to suggest that you try accessing your server through a proxy server and see if you still get the error.