Archive feature is broken

I think the archiving feature is causing that error. Try turning it off.

Patches welcomed.

updating version

Turning off the archive worked but before I turned it off I upgraded to the beta2 version and still got that error.

subscribing

Yes, still happens in beta2, turning off "auto-archive" does seem to make the error go away.

it worked after I turned off archiving. thanks. unobtrusive UI, I liked it.

guys - there isn't any function

chatroom_chat_get_latest_msgs

anywhere in the files of this module - no wonder php gives that error.... The archiving probably works but in its begining it calls that undef func ...

the string

function chatroom_chat_get_latest_msgs

can be found here in the module's files: (recursive find done with notepad++)

[chatroom\chatroom.module]
Line 636 : $msgs = chatroom_chat_get_latest_msgs($chat_id, $user->uid);
[chatroom\updates.inc]
Line 35 : $js->msgs = chatroom_chat_get_latest_msgs($chat_id, $user->uid, $last_msg_id, $timezone, $smileys);
Line 91 : $js->msgs = chatroom_chat_get_latest_msgs($chat_id, $user->uid, $last_msg_id, $timezone, $smileys);

EDIT: @maintainer: please comment that 636th line or do sth fast - switched the issue to critical

subscribing

I just commented on duplicate #362728: Fatal error: Call to undefined function chatroom_chat_get_latest_msgs():

The calls to chatroom_chat_get_latest_msgs need to be updated with calls to chatroom_load_messages (chatroom.module, l.819), which is newer code that accomplishes the same thing.

@rsvelko: unfortunately it is not true that "archiving probably works"; beyond the calls to that removed function, there are also several table references to {chatroom_msg_archive}, which has been removed in favour of an 'archived' column in {chatroom_msg}. Those queries also need to be updated.

ouch. another case of performance killing changes to the chatroom code. i'll work on using the archived flags to get something out, then restore the archive table later.

i've committed code to the DRUPAL-6--1 branch to fix this.

please update and see if it work for you.

Automatically closed -- issue fixed for 2 weeks with no activity.