maximum input text we can put in?

What do you mean by "it doesn't want to submit"? What happens when you try to? This sounds more like a backend storage problem to me, though since I don't know where the error is coming I can't tell.

Having the same problem, as far as I can see since 2.1(.1). It's a javascript problem which comes in two different flavors:

Firefox (1.0.7): too much recursion at line 23 (and sometimes a stack overflow error)
IE: stack overflow at line 23

file: /editor/js/fck_startup.js

The text I tried to save wasnt that extremely long (one A4 with some colors and tables, nothing special). One thing I tried is paste the text in the example on the fckeditor website, the same result. I did this just to verify that it wasn't my implementation of the script.

Just a quick side note: I tried using the normal form value (getXHTML) and the getHTML value, both triggered the errors mentioned above.

Please let me know if there is a fix for this problem

I am having the same problem... It seems that when I have about 1000 lines of code it works fine.. at 1500 lines of code it bombs out and does not same. Though I don't get any errors probably because I have the editor opening in a window. Has anyone found a work around for this issue... now that i know the error is

Firefox (1.0.7): too much recursion at line 23 (and sometimes a stack overflow error)
IE: stack overflow at line 23

file: /editor/js/fck_startup.js

I will see if I can have one of my friends fix it who does soem javascript programming.

J

http://businessbc.ca/test.txt

I tried your file of 2000 lines of plain text and I get the same problem. Can you post the code that you use to post the text to the db?

http://nexunet.com/~miker/richEdit.phps


http://nexunet.com/~miker/textSubmit.phps

Think it has something to do with just the asp version of the FckEditor then... because I am doing the exact same thing as far as posting. Though I am using asp and sql server 2000. but just doing a update to post the information.

It really sucks because I love the editor. About half the articles I post on my site are over this 750 - 1000 lines block I cant get around.

i can't test the asp version as we're running unix. i did a test with about 20,000 lines of plain text and i got a mysql error but no js error.

yeah well think I might just see if I can test the php version of it and see what happens. I put in a bug fix so we will see what happens. I tried testing a couple of wysiwyg editors like Cute and they have the same problem.

Just going to post everything I am finding out about this problem... I took out the editor and just did a simple textarea with a submit button method post and then did a database recordset update and I still get the same problem. A Stack overflow error!!! But I get it with about 1500 lines of code and not with 750 lines so there is something wrong with the editor. But then there also seems to be a limitation with the textarea so how... Not sure... anyway that is some more of my findings.. If anyone has any other ideas let me know.

J

OK I have a solution... Its not a great one but it works. THe problem seems to be with the Stack Size in IIS 4+ they have set the stack size to 256k which with the FCKeditor only allows for about 90,000 to 95,000 characters per textarea... This really sucks! But I found solution that will work and that is to use ASP to split your textarea's up and then just before submit compile them back together. Here is the information I found.

============================================

The limit seems to be around 95000 charaters (256 kb) and here is what Microsoft had to say:

SYMPTOMS
========

A "Stack overflow" or access violation error, or hanging of the server may occur
due to an ISAPI DLL or custom Active Server Pages (ASP) component in Internet
Information Server (IIS) 4.0. This problem does not occur when the same code and
data are used in Internet Information Server 3.0.

CAUSE
=====

The maximum stack size of a thread has been reduced from 1 MB in IIS 3.0 to 256
KB in IIS 4.0.


To go around that what I did is created a constant my example is in ASP but you could probably do something similar in javascript (on submit, call a javascript that split your textarea if it's too big):


If the hidden field is greater than 90000 characters, I just create another one by splitting it and so on
CONST lMAXLENGTH=90000
<%
'The maximum lenght for an input field is 950000 characters
if len(sTreeString)>lMAXLENGTH then
lField=round(len(sTreeString)/lMAXLENGTH,0)+1
currentPosition=1
for i=1 to lField
sTruncatedString=mid(sTreeString,currentPosition,lMAXLENGTH)
%>
<INPUT type="hidden" name="sTreeString<%=i%>" value="<%=sTruncatedString%>">
<%
currentPosition=currentPosition+lMAXLENGTH
next
%>
<INPUT type="hidden" name="lField" value="<%=lField%>">
<%else%>
<INPUT type="hidden" name="sTreeString" value="<%=sTreeString%>">
<%
end if
%>


and on the processing page, I just join it again:

if request("lField")<>"" then
for i=1 to request("lField")
sTreeString= sTreeString & request("sTreeString" & i)
next
else
sTreeString=request("sTreeString")
end if

Hope this helps out the people that want to use this editor. I have tested a ton of editors now to see which ones have this problem and they all do at least the ones written in asp. Now if you can find an Javascript only editor such as TinyMCE this won't be a problem as the javascript converts the textarea to a variable and then carries it.

If anyone has any questions. Feel free to contact me at jason.suttor@rotoamerica.com

I don't understand this solution.

your code to split the string is in asp so it is processed at the server, but then in the FCKeditor you must add another code to join all that data and split it back before posting it to the server.

Or is it just some test code to find the problem with regards to just IIS?

Also I don't understand why you say that a "javascript only" editor won't have this problem because the only asp code in FCKeditor it's just a little wrapper to create the textarea, so the problem of IIS will appear no matter the editor that you try to use (unless the editor has an asp wrapper that takes into account this problem and automatically splits and rejoins the text as needed)

First, The reason I posted just asp code is because I am using just the asp version.

Second, the code shows both the spliting of the textarea and then the parsing it back together. it is not a test script.

As to why I said a javascript only editor is because for some reason the javascript only editors I have tried have not had this limitation!! Probably because the javascript only editors I have mosly tried seem to send the post in a different way then just sending all of the textarea at the same time.

yes the problem is with IIS and its stack space but for some reason a lot of the editors I tried in this same scenario did not have this problem with the stack issue.

https://sourceforge.net/tracker/index.p ... tid=543653

We're having the same issue, did you ever resolve the problem????

Cheers,

Another one here having the same issue ...

*stack overflow at line: 22*

What could possibly be wrong?

Please advise ...

-Jeff