Forum Activity for @brian

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

I would check your S3 settings - I'm not seeing that error here on my end using my S3 settings. Check your bucket security, and any where else you may have enabled a stricter transport mechanism.

Duplicates and 'follow_unique' in jrdiscussion_follow_topic

Jamroom Developers

I would recommend staying with the Discussion module. Adding threading to the forum is likely to be more challenging then just figuring out a good archive scheme for the Discussion module. The recent performance improvements that came out in Comments 2.0 should allow you to continue using the Discussion module for some time to come, and moving to an archive setup should allow you to use it indefinitely.

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

Yes - it's the S3 settings - you need to make sure the access and secret keys are correct AND the bucket exists and is configured correctly - basically a bucket with default settings. I know for certain it works - we use it here on jamroom.net, and I use it on all my sites.

updating template to jrCore_item_detail_features doesn't display prior entered tags

Using Jamroom

Glad to hear that - thanks!

disalow periods in user names

Suggestions


Marking this as solved - this isn't a JR issue.
updated by @brian: 11/18/17 12:33:44PM

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!

Please explain new update for Profiles module

Using Jamroom

Correct.

Please explain new update for Profiles module

Using Jamroom


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.

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.

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.