diablo2.io is supported by ads

Error on commenting on a topic: Data too long for column 'topic_last_post_subject' at row 1 [1406]

fredkid · 2025-04-11T16:06:18-07:00

Hi I tried to comment on topic https://diablo2.io/bug-reports/recently-sold-player-service-trade-is-deleted-when-you-mark-as-sold-another-player-service-trad…

4 replies 439 views

Description

Hi

I tried to comment on topic
bug-reports/recently-sold-player-servic ... 80937.html
this

Additional info: Both trades are similar, they had the same title "10 MM
Gold", description "Offer 5
Hel or 14
Perfect Skull [WTB]", and "meta-data" ("Players Service", "WTB" and " WTS (Rare/Crafted)" stash)

or this

Additional info: Both trades are similar, they had the same title, description, and "meta-data"

(more than once each)
and always got an error:

General Error
SQL ERROR [ mysqli ]

Data too long for column 'topic_last_post_subject' at row 1 [1406]

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists.
Please notify the board administrator or webmaster: [email protected]

Description by

fredkid

Can be used to make Runewords:

fredkid `1877`

7 months ago (pre-Resurrected)

Hi

I tried to comment on topic
bug-reports/recently-sold-player-servic ... 80937.html
this

Additional info: Both trades are similar, they had the same title "10 MM
Gold", description "Offer 5
Hel or 14
Perfect Skull [WTB]", and "meta-data" ("Players Service", "WTB" and " WTS (Rare/Crafted)" stash)

or this

Additional info: Both trades are similar, they had the same title, description, and "meta-data"

(more than once each)
and always got an error:

General Error
SQL ERROR [ mysqli ]

Data too long for column 'topic_last_post_subject' at row 1 [1406]

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists.
Please notify the board administrator or webmaster: [email protected]

Fixedby Teebling • 6 months ago•Go to post

Fixed in 1.50

Time Zone: GMT-3
Non-Ladder | Softcore | Expansion
----
Equivalence for trades:

Ist = 1 =

Token of Absolution = 20

Perfect Gems

Pul=0.25 |

Um=0.5|

Mal=0.75

Gul=1.5|

Vex=2 |

Ohm=3 |

Lo=4 |

Sur=5

Ber=9 |

Jah=12 |

Cham=3 |

Zod = 4

ShadowHeart `4915`Moderator

7 months ago (pre-Resurrected)

When you post a post reply using the full editor, there's a topic field above the usual message field, which is pre-filled with "Re: " + the topic name. It could be that the topic name is barely short enough to fit in the database field, but the reply topic name (with the "Re: " in front) is too long and Teebling has no field length check for topic name on the reply form submission?

Can you try replying in the same thread and manually shorten the reply's topic name?

At least it's a workaround (if it works)...

I'm in CET (Central European Time), so that's UTC+1 normally and UTC+2 during DST.
My profile says Ladder, but I play both Ladder and Non-Ladder.
My profile says Softcore, but I play both Softcore and Hardcore.
My Holy Grail Tracker is for Offline Hardcore.

fredkid `1877`

7 months ago (pre-Resurrected)

It worked

Removed the "Re: " from the "new title" and could submit the comment.
(The original title was already at the length limit)

ShadowHeart wrote: 7 months ago
When you post a post reply using the full editor, there's a topic field above the usual message field, which is pre-filled with "Re: " + the topic name. It could be that the topic name is barely short enough to fit in the database field, but the reply topic name (with the "Re: " in front) is too long and Teebling has no field length check for topic name on the reply form submission?

Can you try replying in the same thread and manually shorten the reply's topic name?

At least it's a workaround (if it works)...

bild.png

bild.png