Hi everyone!
I am getting a problem while trying to add content via the editor. The editor doesn't want to submit the content when it's to long. Is there a maximum size defined as regards the input text??
Regards,
Loic
I am getting a problem while trying to add content via the editor. The editor doesn't want to submit the content when it's to long. Is there a maximum size defined as regards the input text??
Regards,
Loic
RE: maximum input text we can put in?
RE: maximum input text we can put in?
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
RE: maximum input text we can put in?
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
RE: maximum input text we can put in?
i am able to paste in 2000 lines of plain text and save to db and then open again in the latest version of FCK in ie 6 and firefox 1.07 with no problems. it's a little slow but works fine.
here's a link to the txt file:
http://businessbc.ca/test.txt
RE: maximum input text we can put in?
RE: maximum input text we can put in?
this loads the editor
http://nexunet.com/~miker/richEdit.phps
this saves to db
http://nexunet.com/~miker/textSubmit.phps
RE: maximum input text we can put in?
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.
RE: maximum input text we can put in?
RE: maximum input text we can put in?
RE: maximum input text we can put in?
J
RE: maximum input text we can put in?
============================================
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
RE: maximum input text we can put in?
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)
RE: maximum input text we can put in?
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.
RE: maximum input text we can put in?
I still can't undestand how your solution could be directly applied as it doesn't make sense to me.
You first split your code in several hidden inputs, so the client side (where FCKeditor runs) gest several inputs, You don't show any javascript code that rejoins them to feed them to FCKeditor, so you would end up editting only one of those sections.
am I wrong?
Are you able to edit the full original text in a single FCKeditor instance?
What happens if you paste a verly large amount of text inside FCKeditor?
How is it splitted before sending it back to the server.
I see that at the server side you join the hidden inputs that you generated in ASP, but FCKeditor won't populate them, it would update just one of them and the rest would remain untouched.
On the other side I've found this bug report that was automatically closed as the reporter didn't provide a full content to test the problem:
https://sourceforge.net/tracker/index.p ... tid=543653
This is a javascript error at the client side, but the description of the MS error would be a server side error, very different one.
Which kind of error do you get?
RE: maximum input text we can put in?
Cheers,
RE: maximum input text we can put in?
*stack overflow at line: 22*
What could possibly be wrong?
Please advise ...
-Jeff