Project

General

Profile

MUC doesn't handle 'maxchars' in join

Igor Khomenko
Added over 4 years ago

I found that MUC doesn't handle 'maxchars' in join

you can check this code https://projects.tigase.org/projects/tigase-muc/repository/revisions/master/entry/src/main/java/tigase/muc/history/AbstractJDBCHistoryProvider.java

there are no any checks for 'maxchars' in method 'getHistoryMessages'

can you fix this?


Replies (3)

(1)
Avatar?id=6098&size=32x32

Added by Bartosz Malkowski TigaseTeam over 4 years ago

No. I don't plan to add this feature.

(1)
Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam over 4 years ago

Igor, if you think this is a bug please file a bug report, if this is a new feature request, please file it as a feature request: https://projects.tigase.org/projects/tigase-muc/issues/new

In either case we will consider it for one of next releases.

Added by Martin N over 4 years ago

Yes I noticed this as well after an update from Tigase 5.0 to tigase 5.2. I know I did not get any history before when using maxchars=0 in tigase 5.0.

Anyhow for my purposes muc/history-db=none works fine.

    (1-3/3)