nightjarnz

Permissions are controlled separately to Members.

nightjarnz

All people that can sign in, are members of some type. All members are people that can sign in. They sign in through the log in form. The log in form (by default) references the built in Member object. The built in Member object thus must reference all members. PERMISSIONS are what you are worried about - authorisation is something complimentary but very separate to authentication.

Aaron Cooper

What's everyone's experence with using the Member class for handling Frontend users? As opposed to a separate class. Something about Frontend members (public) being inside the same collection of objects as CMS users separated by one field gives me the trots.

wmk

And another SS2 site was switched off after an update to SS4 👯‍♂️

wmk

who had this idea to put "previous" and "next" strings in css's content property... That's not the way to make it easily translatable

wmk

custom code on a project where I "just" added fluent for i18n

wmk

html:lang(en-US)& scss selector did the trick