What steps will reproduce the problem?
1. load the muc_log_http module
2. load the muc_log module
What is the expected output? What do you see instead?
Visiting http://ip:port/muc_log returns an empty page (containing no data
whatsoever), while the prosody log doesn't contain any load errors for the
muc_log_http order.
Reversing the order of the modules fixes the issue.
What version of the product are you using? On what operating system?
Prosody 0.7.0, the latest muc_log and muc_log_http modules
Original issue reported on code.google.com by dominik.honnef on 15 Apr 2011 at 9:25
Original issue reported on code.google.com by
dominik.honnef
on 15 Apr 2011 at 9:25