Can only post 1477 bytes or less on RavenNuke Articles!

Hangin' Around Joined: Jul 20, 2006 Posts: 41

I last posted a large article on my site on the 1st of September. I know I haven't made any changes since then because I've been very busy since. No-one else has access to the site/db.
I tried to post a new article this morning, but the d***ed thing won't let me post more than 1477 bytes Exclamation

Site is at [ Only registered users can see links on this board! Get registered or login! ]

Thanks!

Site Admin Joined: Jun 04, 2004 Posts: 6433

Something had to change, of course. I'd suggest looking for file changes by date using [ Only registered users can see links on this board! Get registered or login! ] Also check the field type and size in the stories table in your database.

Posted: Mon Sep 18, 2006 9:27 am

Just happened to have the SQL load files open. The story text is in either the hometext or bodytext field and both fields are text types and therefore have approximately a 64k bytes limit (much larger than your input). So, unless there has been a change to your stories table I'd look elsewhere for the problem. My guess is that something in the text at about 1477 bytes into the story is causing the problem. You could try posting a story that really is just plain text and is longer than the 1477 bytes to confirm this.

Posted: Mon Sep 18, 2006 9:32 am

Good point, fkelly. It could be that something caused the story to be truncated. I was thinking that maybe somehow synaptyx's table got changed from a text field, either accidentally or intentionally.

Posted: Mon Sep 18, 2006 11:08 am

It could be a table change too Kguske. I was just thinking that something in the text that MYSQL or the filters don't like is more likely. Why anyone would go in there and change field types was just escaping my imagination when I wrote.

We'll just have to be in suspense till Synaptyx gets back to us Smile

Posted: Tue Sep 19, 2006 2:38 am

Thanks guys. Smile

I just tried posting over the 1477 bytes as plain text and it all works perfectly. As soon as I start putting html in there it goes nuts. Thing is, none of the code is beyond basics and there is nothing in there I haven't used a dozen times before. Hmm.

Posted: Tue Sep 19, 2006 3:46 am

This is all the code with the content (except images) removed. It posts fine. It seems to purely be the amount of text content between the tags that is causing the problem. Although it shouldn't be. This doesn't really make sense.

Code:

<table border="0" width="100%">


<tr>


<td valign="top"><h2 align="justify"></h2>


<p><i></i></p>


<p align="justify"></p>


<p align="justify"></p>


<p align="justify"></p>


<p align="justify"><a target="_blank" href="http://community.livejournal.com/discord_society/profile"></a>


      <a target="_blank" href="http://www.petitiononline.com/ffhoeris/petition.html"></a>.</p>


<p align="justify">


 <a target="_blank" href="http://www.thebeak.org/index.php/archives/80"></a>.</p>


 <hr color="#000000" size="1">


 <p align="right"><i></i>


<td valign="top">


<p align="center"><img src="http://poee.co.uk/images/enteris.jpg"><i><br>


</i></p>


<p align="center"><img src="http://poee.co.uk/images/eris_and_dysnomia.jpg"><i><br>


</i></p>


<p align="center"><img src="http://poee.co.uk/images/orbit.jpg"><i><br>


</i></td>


</tr>


</table>

Posted: Tue Sep 19, 2006 3:49 am

Just out of curiosity, check the allowed html array for the paragraph tag P as it is not allowed by default.

Posted: Tue Sep 19, 2006 4:07 am

Thanks Guardian, I checked that. I allowed the < P > tag with attributes some time ago. Smile

Posted: Tue Sep 19, 2006 4:08 am

Thanks for the follow up - it was just a stab in the dark but worth exploring.

Posted: Tue Sep 19, 2006 4:21 am

No probs, definitely worth checking.

Posted: Tue Sep 19, 2006 4:39 am

Just to clarify, are you using WYSIWYG? There is another config.php change to the allowable HTML so it knows how to treat HTML attributes. But it still shouldn't truncate the text.

Is it every text field? Maybe there is some added js that thinks that field is for something else? What other modifications or additions were made?

Posted: Tue Sep 19, 2006 5:26 am

Using WYSIWYG (fp03) to create the article, then editing out the spurious code by hand. I've done this over 170 times and it's never been a problem until now. I don't know of any js, or modifications other than the usual custom blocks, etc on the main page. If I put the article into the extended text box it kicks me out to the main page too.

Sorry guys, I'm not good with php, or mysql, so if you come up with anything technical assume I am a complete n00b.

Posted: Tue Sep 19, 2006 6:17 am

What is fp03? Do you mean that you use a WYSIWYG somewhere else to create the source HTML, then paste it into a textarea in Nuke?

When you say it kicks you out to the main page, that's different than truncating the content at 1477 bytes. It indicates a bad HTML tag. There is something in the HTML it doesn't like.

Posted: Tue Sep 19, 2006 6:54 am

kguske wrote:

What is fp03?

FrontPage2003.

Quote:

Do you mean that you use a WYSIWYG somewhere else to create the source HTML, then paste it into a textarea in Nuke?

Yep.

Quote:

When you say it kicks you out to the main page, that's different than truncating the content at 1477 bytes.

I don't recall saying it truncated the post, just that if I tried to post over 1477 bytes, it kicks me out. Smile

Quote:

It indicates a bad HTML tag. There is something in the HTML it doesn't like.

I'd agree with you, but for the life of me I cannot figure out what. After a bit of playing around I've discovered that. All the elements post fine on their own, code/plaintext. It's just when they are put together there is a problem.

Posted: Tue Sep 19, 2006 7:38 am

Right, this is stranger than strange. The piece I'm trying to post is a bit of drivel about Planet Eris. These two paragraphs are causing the problem. Even if I retype them I still get the same result!

Quote:

The International Astronomical Union claim that
this object, temporarily designated 2003 UB313, has caused much chaos, strife,
discord and disorder in their ranks by sparking a heated debate into what we
consider to be a planet. The object turned out to be seventy miles larger than
Pluto and gave the IAU the problem of either deciding to call them both planets,
or neither. The debate was officially ended with the decision to re-categorise
Pluto, 2003 UB313 and asteroid Ceres as "dwarf planets." The Dwarfs were pleased
to accept the newly re-designated planets into their interplanetary community
and hope to set up diamond mines in the near future.

The dwarf planet formerly known as 2003 UB313
(and unofficially nicknamed Xena by the discovery team) received the official
designation (136199) Eris, or Eris for short, from the International
Astronomical Union on 13th September 2006. The name was proposed by Mike Brown
of the discovery team and accepted almost unanimously by the Working Group for
Planetary System Nomenclature (WGPSN) and the Committee for Small Body
Nomenclature (CSBN). The name Dysnomia was given to it's moon. Dysnomia is the
Daimon spirit of lawlessness. She is the daughter of Eris, goddess of chaos and
strife, and the counterpart to Eunomia who puts an end to the anger of grievous
strife.

Posted: Tue Sep 19, 2006 7:41 am

Ahhh. I incorrectly inferred the truncation from "Can only post 1477 bytes or less."

Regarding FP2003, I'd suggest using a demo of a web-based WYSIWYG editor (e.g. [ Only registered users can see links on this board! Get registered or login! ] instead of FrontPage, if you don't want to add the WYSIWYG editor to your site (it will be preinstalled in future releases of RavenNuke).

Like MS Word, FrontPage adds a bunch of IE-specific (or FrontPage-specific) tags to the HTML, and I'm sure they aren't included in the allowable HTML, which is why you're getting kicked back to the index page. You could use FCKeditor's Paste from Word function to strip out the extraneous tags, but why not just start with a better editor?

Posted: Tue Sep 19, 2006 7:44 am

Ding, ding, ding!!!! You said the magic word: union. This is NukeSentinel trying to block union attacks a little too aggressively.

Try replacing the letter o in union with 0 (zero). Or, search the forums here for an alternative method (using the HTML entity for one or more of the letters, if I remember correctly).

Posted: Tue Sep 19, 2006 7:55 am

kguske wrote:

Ding, ding, ding!!!! You said the magic word: union. This is NukeSentinel trying to block union attacks a little too aggressively.

That's it! Very Happy

Thanks! I was ready to start beating my brain out with a hammer! Thanks kguske.

Posted: Tue Sep 19, 2006 7:57 am

Well, I wasn't using a hammer, but still beating my head against the wall... Glad you found it!

Posted: Tue Sep 19, 2006 8:08 am

I replaced the "U" in "Union" with "&#85 ;" (no space) and that solved it.

Thanks again kguske.

/wipes sweat from brow.

Get yourself a beer from my donation. Wink

Posted: Tue Sep 19, 2006 1:08 pm

Actually I believe that it's a bug in mainfile that's kicking the multiple onion word out. There is a check in mainfile that had a bug in it and that's been fixed for 2.10.

This one is not Sentinel.

I posted the fix here a few weeks ago if memory serves or you can wait for 2.10.