Forum Activity for @brian

brian
@brian
18 Nov 2017 12:33:26PM
9,196 posts

disalow periods in user names


Suggestions

brian:
You can use the Banned Items module to ban periods in user names.

Marking this as solved - this isn't a JR issue.
updated by @brian: 18 Nov 2017 12:33:44PM
brian
@brian
16 Nov 2017 04:29:09PM
9,196 posts

updating template to jrCore_item_detail_features doesn't display prior entered tags


Using Jamroom

Yeah that's weird and doesn't look correct - open a ticket for me if you would with the site login so I can check it out.

Thanks!
brian
@brian
16 Nov 2017 04:11:13PM
9,196 posts

Please explain new update for Profiles module


Using Jamroom

Strumelia:
It seems to be saying that members can add more items than their quota permits, ...but that they just won't SEE the extra items. Why would they be able to add more than their quota permits in the first place? Can you help me understand what this is about please?

No - that's not what this means :) Imagine the following scenario:

- you have a user that uploads 20 songs BEFORE you place any quota limits in place
- you then set their quota limit to "10"

in this instance only the first 10 songs will now show to visitors to the profile (based on the order as set in display order). The change made it so if a visitor attempted to view a song that was hidden because of the profile limit (say song #11) they previously would get an error about the quota limits being enforced - it was the message meant to be displayed to the site owner. Now instead it just shows a "not found" page to visitors.

The second fix for hard versus soft limit was that if you had set the profile quota limit to a HARD limit (i.e. not allowed to exceed at all) profile owners would not "see" the songs above the limit to delete them.

Let me know if that helps.
brian
@brian
16 Nov 2017 01:41:54PM
9,196 posts

disalow periods in user names


Suggestions

Sounds like a comet chat issue :)

You can use the Banned Items module to ban periods in user names.
brian
@brian
16 Nov 2017 01:17:24PM
9,196 posts

Archive and Purge


Jamroom Hosting

For the Timeline, make sure the ACP -> Profiles -> Timeline -> Prune System Entries is enabled and set to something like "90" - this will prune out all the "system added" timeline entries - i.e. "so and so commented on..", etc. Timeline entries that are made by the actual user are never purged. This can usually take care of any Timeline DS issues.

As for performance profiling, you can get as involved as you want - most of them I would not recommend running on the production site.

One that you CAN turn on is set the Developer Tools -> Slow Query Log to like 2 seconds - any jrCore_list or jrCore_db_search_items calls that take longer than 2 seconds to return will be logged to the Activity Log along with information about the URL, the user and the parameters and constructed query. This can be used to spot where the "trouble spots" are and can really help narrow down your work to those areas that need it most.

Let me know if that helps.

P.S. I've sent Perrie a reply about sponsoring an archive/deleting module - Paul and I have been discussing it in chat and I think we could build something really cool.
brian
@brian
16 Nov 2017 11:06:25AM
9,196 posts

Archive and Purge


Jamroom Hosting

TiG:
Seems to me that a small comments table would perform well even with inefficient db queries but as the record count grows the inefficiencies will manifest as performance problems. Ergo, the fewer records the better. How is that not the case?

Sorry if I gave that impression - of course a smaller DS will always perform better on inefficient queries so it makes sense to archive records if your use case requires lists that use a larger number of search conditions.
brian
@brian
16 Nov 2017 10:29:48AM
9,196 posts

Archive and Purge


Jamroom Hosting

TiG:
Would it be practical for us to consider migrating from jrDiscussion to jrForum?

It could, but it's not that clear cut.

To be honest the calls on your site that are slowing things down are not the comments that are being listed in a specific topic - that's no problem - those will remain fast even with millions of comments. It's the lists of the type "here's the latest comments on discussions in our community profile that are related to US politics" - that requires more search conditions, which means it is going to be slower.

So if you were to attempt to do those types of lists using the Forum, you might run into the same issues.
brian
@brian
16 Nov 2017 10:26:13AM
9,196 posts

Archive and Purge


Jamroom Hosting

TiG:
So a site with basic comment functionality could handle far more comments than one that gets 'fancy' with its functionality.

Exactly. So when you start facing performance issues, the first thing to do is figure out how to be "less fancy". For example, the front page of your site right now has 13 different site builder blocks on it - 8 of them are lists. Are they all really needed? Look at Reddit - it's ONE list. If they tried to slice their data 8 different ways on every page they could never scale.

I know this isn't something you can decide on immediately, but it's something you can do over time that can really help your site scale better. Focus on reducing the number of unique listings - this gives you a better chance of having a smaller cache with a higher hit rate.
1