Forum Activity for @brian

brian
@brian
05/04/17 05:42:56PM
10,149 posts

Proxima User With Profile Name


Proxima

Michael is correct - with Proxima the user name will be used as the profile name.
brian
@brian
05/04/17 05:42:19PM
10,149 posts

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:
RewriteCond %{HTTP_HOST} ^www\.roughneckcity\.com [NC]
RewriteRule .? https://roughneckcity.com%{REQUEST_URI} [R=301,L]

Add this right after the "RewriteEngine On" line.
brian
@brian
05/04/17 12:15:40PM
10,149 posts

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.
brian
@brian
05/04/17 12:05:33PM
10,149 posts

jrSearch errors in Activity Log


Using Jamroom

Melih:
I will get in touch with my hosting company to see they can do anything about this.
Thank you so much Brian

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.
brian
@brian
05/04/17 12:00:34PM
10,149 posts

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.
brian
@brian
05/04/17 11:58:57AM
10,149 posts

SSL Log In Issue


Design and Skin Customization

derrickhand300:
Yes i have cloudflare enabled...??

Did you update your Cloudflare account so it knows your site is SSL?
brian
@brian
05/04/17 11:26:44AM
10,149 posts

jrSearch errors in Activity Log


Using Jamroom

Melih:
Unfortunately i am getting same error with a fresh install. I will send an email to you Brian.

OK - will be watching for your email.

Thanks!
brian
@brian
05/04/17 11:25:01AM
10,149 posts

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
brian
@brian
05/04/17 10:17:01AM
10,149 posts

jrGoogleAnalytics record hit listener


Jamroom Developers

Thanks Steve - this is one of those "this would be kind of cool to support" things I add in sometimes when I'm in the code, the idea being I may use it at a later point, so let me know how it goes.
brian
@brian
05/04/17 10:16:18AM
10,149 posts

jrSearch errors in Activity Log


Using Jamroom

Melih:
Sorry to say that but i'm still seeing the same error after update

Hmm.. tested here on MySQL 5.5.55, 5.7 and MariaDB 10.1 and am not seeing any problems. Are you sure the error is still coming through? Delete the debug log and try an integrity check. If it is still erroring I would have to get access to the system to see what is unique about your MySQL version.
  130