221
Whew! I actually had to send for a new password to be able to post a reply.. It would tell me I'm logged in, then tell me I am not allowed to reply...
(This is similar to the issue with XIM I'm trying to comment on)
I too just this morning had to uninstall the latest XIM version as registered users were getting lockups after logging in.
There were also permission alerts when they would try to directly access other areas on the site.
The reason I recommended the Ajax chat was that XIM specifically speaking, isn't a "chat" module like the OP requested.. It's an Instant Messenger..
Here are my system specs:
XOOPS Version XOOPS 2.4.5
PHP Version 5.2.17
mySQL Version 5.1.52
Server API cgi-fcgi
OS Linux
safe_mode Off
register_globals Off
magic_quotes_gpc Off
allow_url_fopen Off
fsockopen On
post_max_size 64M
max_input_time 60
output_buffering
max_execution_time 30
memory_limit 128M
file_uploads On
upload_max_filesize 64M
I have no clue as to how long this was a problem as it worked perfectly for admin users who basically were the only ones using it. Regular users just reported it.
Any wisdom to be had is appreciated.
Debug mode showed nothing regarding XIM, just a couple of deprecations in other modules that aren't having issues.
(This is similar to the issue with XIM I'm trying to comment on)
I too just this morning had to uninstall the latest XIM version as registered users were getting lockups after logging in.
There were also permission alerts when they would try to directly access other areas on the site.
The reason I recommended the Ajax chat was that XIM specifically speaking, isn't a "chat" module like the OP requested.. It's an Instant Messenger..
Here are my system specs:
XOOPS Version XOOPS 2.4.5
PHP Version 5.2.17
mySQL Version 5.1.52
Server API cgi-fcgi
OS Linux
safe_mode Off
register_globals Off
magic_quotes_gpc Off
allow_url_fopen Off
fsockopen On
post_max_size 64M
max_input_time 60
output_buffering
max_execution_time 30
memory_limit 128M
file_uploads On
upload_max_filesize 64M
I have no clue as to how long this was a problem as it worked perfectly for admin users who basically were the only ones using it. Regular users just reported it.
Any wisdom to be had is appreciated.
Debug mode showed nothing regarding XIM, just a couple of deprecations in other modules that aren't having issues.
The more I know, the more I know that I really didn't wanna know.
