Forum Activity for @brian

Reports that users are accidentally getting logged in as different users?

Using Jamroom

We had one other site report this to us a bit back - I believe the problem lies in the "session sync" function in the User module, but we've never been able to actually replicate here. However, Users 2.2.0b2 has all new session sync functions, so updating to Jamroom Core 6.1.0b2 and the latest beta modules can hopefully help this.

I know it's a beta release, so if you'd like to do that let me know your site login in a ticket and I can make sure you get updated correctly.

Hope this helps!

Proxima User With Profile Name

Installation and Configuration

This is fixed in Proxima User 1.2.1 - update and you should be good.

Thanks for letting us know.

Proxima User With Profile Name

Installation and Configuration

Michael is correct - with Proxima the user name will be used as the profile name.

SSL Log In Issue

Design and Skin Customization

You can see the root problem is what I outlined earlier:

1) You have the value "https://roughneckcity.com" in your data/config/config.php file
2) you are accessing your site at https://www.roughneckcity.com - the "www" means your browser sees this as a DIFFERENT site.

You need to update your .htaccess file to FORCE your users to not go through www:

Add this right after the "RewriteEngine On" line.

jrSearch errors in Activity Log

Using Jamroom

So just to add, there is an InnoDB variable:

https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_optimize_fulltext_only

That we can check - if it exists, it means InnoDB supports a FULLTEXT index. What's weird is that your server DOES have this variable, which tells me the support has been disabled for some reason.

jrSearch errors in Activity Log

Using Jamroom


Yep - no problem. I'm hoping to find a way where it can test for the support versus just checking the version numbers (which is what it does now), so hopefully that can be worked around.

jrSearch errors in Activity Log

Using Jamroom

This is weird - your MySQL is version 5.6.34, which should support Full Text for InnoDB:

https://dev.mysql.com/doc/refman/5.6/en/fulltext-restrictions.html

So my guess is that for some unknown reason it has been disabled on your server. I will see if there is a way to change the detection check to be based on querying the DB versus a version.

SSL Log In Issue

Design and Skin Customization


Did you update your Cloudflare account so it knows your site is SSL?

jrSearch errors in Activity Log

Using Jamroom


OK - will be watching for your email.

Thanks!

SSL Log In Issue

Design and Skin Customization

Unfortunately no - this is a pretty simple setup. There is a user_password key in the User DataStore that stores the password hash - that's it. It's value does not depend on SSL or anything for that matter, which is why this doesn't make sense.

My suspicion is that the SSL settings configured in your web server are incorrect, you have some sort of caching layer enabled (such as cloudflare) or some other 3rd party Javascript that is interfering with your site and preventing it from functioning properly on SSL.
updated by @brian: 05/04/17 11:25:45AM