Forum Activity for @brian

maybe an issue with latest beta core

Installation and Configuration

And this one:


Means your redis server disconnected before the READ could occur - again, not a Jamroom issue.

If your site is REALLY busy, you could be running into a maxconn issue - make sure and check this out:

https://www.cyberciti.biz/faq/ip_conntrack-table-ful-dropping-packet-error/

Do some reading about how the kernel handles IP connection tracking - you may need to increase it.

maybe an issue with latest beta core

Installation and Configuration

There is no need to post any "MySQL server has gone away" errors - that's not a Jamroom issue.

maybe an issue with latest beta core

Installation and Configuration

Note that we do not develop or test on Litespeed - just an FYI.

maybe an issue with latest beta core

Installation and Configuration


No - that is dashboard panel that is provided by the User module (you can see this by clicking a panel - it will show you panels that can be displayed - users online count is under the USER module).

maybe an issue with latest beta core

Installation and Configuration

Do you have BOT sessions enabled in your Users module global config?

maybe an issue with latest beta core

Installation and Configuration

The beta core doesn't handle user sessions - that's the USER module, so I'm not sure why you are seeing this.

maybe an issue with latest beta core

Installation and Configuration

Are you using MySQL or Redis sessions?

Deletion of Smileys

Using Jamroom

What you're looking at are the controls for TinyMCE - we don't have control over that portion of the editor unfortunately.

How do I fix ERROR - MySQL Support

Using Jamroom

Support for Jamroom 4 ended in 2013.

bug in tinymc

Using Jamroom

There is a new Javascript loader that was created for Jamroom Core 6.4.1b5 and newer (also in Jamroom Core 6.5.0b1) that is designed to "bust" Chrome's aggressive caching which should avoid the issues that were seen in Core 6.4.0 when it was released with the update to TinyMCE 5, so this has been fixed.