Forum Activity for @brian

brian
@brian
01/30/16 09:23:09AM
10,149 posts

bug (i think) report imzage cache still not clearing correctly


Installation and Configuration

I've got an update in the next version of the Image Core module that should help - I've moved the cache clearing to a queue worker. Most likely what is happening here is that the process is timing out (30 seconds) before it can remove all the needed cache images. Moving this to a queue worker will let it fully remove the entire cache without worrying about it timing out.
brian
@brian
01/30/16 09:21:45AM
10,149 posts

Youtube error


Using Jamroom

MySQL does not support emoji unicode - the next version of the core will strip it out so you shouldn't see this error.
brian
@brian
01/30/16 09:20:28AM
10,149 posts

Mutual Follow "Friends" button - plus Message


Design and Skin Customization

This is pretty much already supported by Jamroom:

- You can easily view WHICH profiles you are following (as a user) by clicking on the "Profiles you Follow" option in the user menu

- You can easily see which USERS are following your active profile by clicking on the "followers" profile menu option.

One of the issues here is that Jamroom is not a 1 to 1 system (1 user to 1 profile) - it can be 1 user to multiple profiles, or multiple profiles to 1 user. Users follow profiles - not users.

This is why the users that follow a profile are shown in the PROFILE menu, while profiles a user follows is shown in the USER menu.

The one thing we could do here is have some type of indicator on the profile followers page whether or not the viewing user (if they are the profile owner) is following that user's profile. Would need to be handled via JS though, and not in a template, since the followers page is cached and on a profile with multiple users this would be a problem.
updated by @brian: 01/30/16 09:20:54AM
brian
@brian
01/30/16 09:16:49AM
10,149 posts

Designing a profile form for profiles in Quota X, and a different form for profiles in Quota Y


Using Jamroom

The form designer is a feature provided by the Jamroom Core - it is not a module. Modules can then "register" a form to be customizable via the form designer.

You can select WHAT quotas see WHICH specific fields. I would suggest spending some time playing around in the form designer and see what it can do - it's very flexible.
brian
@brian
01/30/16 09:14:20AM
10,149 posts

Should a profile's 'Latest Activity->ALL' go to the Timeline page?


Using Jamroom

Only the profile owner will see the timeline activity for users they follow - anyone else viewing the profile will only see the activity entries for the profile - not the followers.
brian
@brian
01/27/16 08:56:24AM
10,149 posts

Aparna Module: from dev server to live server


Using Jamroom

Checking this out it looks like you have to have a dev account here on Jamroom.net to get the developer prefix - let me check this out and see if this can be enabled without needing a dev account.
brian
@brian
01/27/16 08:54:49AM
10,149 posts

Considering Buying Cloud


Using Jamroom

Yes - S3 is included. I will get that update and out of beta.

Hope this helps!
brian
@brian
01/27/16 08:54:24AM
10,149 posts

conc and cont fields on import


Genosis

Would it be possible to get a GEDCOM file from you for testing? In developing Genosis I've found that almost all software has slight differences in format (even though they shouldn't) and/or have custom fields. If not, I will try to replicate it here and see what's up. If you have a GEDCOM, send it to brian [at] jamroom [dot] net and I can run it through an import here on my dev system and see what's up.

Hope this helps!
brian
@brian
01/27/16 08:52:31AM
10,149 posts

Server Configuration Help


Installation and Configuration

That's way too much for the key_buffer - key_buffer is only used by MyISAM tables - JR uses InnoDB for the majority of the large tables - try this:

[mysqld]
default-storage-engine=MyISAM
innodb_file_per_table=1
key_buffer_size         = 512M
max_allowed_packet      = 64M
table_cache             = 1536
table_definition_cache  = 1536
open_files_limit        = 50240
tmp_table_size          = 512M
max_heap_table_size     = 256M
sort_buffer_size        = 4M
read_buffer_size        = 4M
read_rnd_buffer_size    = 1M
max_connections         = 200
innodb_buffer_pool_size = 8G
innodb_flush_method     = O_DIRECT
innodb_flush_log_at_trx_commit = 0
ft_min_word_len         = 3
ft_stopword_file        =

50240 is VERY large for the open_files_limit - unless you are running hundreds of databases with hundreds of tables each, that can be lowered.
  288