Forum Activity for @brian

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom

Just wanted to add here that Jamroom is (as far as I can tell reading the GDPR requirements) already mostly GDPR compliant. The only thing a site might want to change is their Privacy Policy and Terms of Service to use more appropriate "GDPR language".

The only thing we are working on right now is an update to the User module that allows the site to change the "notifications" tab - this allows you to pick whatever format may be easier for your users, since a lot of the GDPR is about making it easy for a user to see HOW they will be contacted and how their data is used.

Note that the data retention period for the GDPR is (as far as I know) still a gray area - I do not believe you have to automatically delete a user's account if they have not logged in in X days, but instead you just must make it easy for the user to delete their account and in turn have it delete ALL their data (which JR already does).

Let me know if that helps or you know of a GDPR requirement that needs support on our end.

Thanks!

Activity Timeline Question

Design and Skin Customization

Yep - exactly. You can string as many values as you want on the not_in - i.e.


So you're not just limited to 2 values - you can have 20 if you want.
updated by @brian: 05/19/18 12:05:53PM

Activity Timeline Question

Design and Skin Customization

You will get better performance by changing this:


To this:

the "not_in" operator takes a comma separated list of values to match.

The "ignore_missing" key is a special key that is only needed on !=, not_like and not_in operators (basically negating operators) that can be added to tell the core that it can ignore any items that do NOT have the key you are searching on, otherwise the core has to include any items that are missing the key you are searching on (since those items "do not match").

Basically anywhere we can cut down the number of separate search conditions will always result in a higher performing query.
updated by @brian: 05/19/18 11:52:01AM

Beta core updates

Using Jamroom

You want to turn off the BETA channel in ACP -> Core -> Marketplace -> Tools -> Marketplace Channels.

Let me know if that helps.

Add gtag.js to Google Analytics module selection?

Installation and Configuration

I believe the gtag.js is still in beta, but I can look at adding support for it. It looks like the main difference is that gtag.js supports sending events to Analytics, Adwords AND Doubleclick (versus just Analytics).

System Updates remain after installing

Installation and Configuration

1) Update the module
2) run an integrity check and reset caches

How to use the notifications dropdown menu - more clarity is needed

Using Jamroom

You will be able to select between the drop-down (current) method and "all on one page" method in the next release of the user module - that's coming soon.

Add gtag.js to Google Analytics module selection?

Installation and Configuration

Can you let me know where you are seeing this at? The official docs still show it working the way the module works:

https://developers.google.com/analytics/devguides/collection/analyticsjs/

Thanks!

MySQL error after updating Jamroom

Jamroom Developers

Looking at this some more, my suspicion is that you have a {jrCore_list} call either in your header.tpl or footer.tpl that is relying on a variable being set in the template (or passed in via $_post) that is NOT being set. Since the error in your first screenshot came in on the activity log, that makes me think it's probably in your header/footer.

AWS Backup

Using Jamroom

When you save the config, the module tries to "validate" the entered S3 credentials are correct (even with the daily backup to S3 unchecked). I'm not seeing any issues on this end - I suspect it is network related if you still getting packet errors.