From 5c2e5138e4f0d0c398ae7164de84e85ad5a96b1f Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 23 Aug 2022 22:51:42 +0000 Subject: [PATCH] --- devdocs/todo.txt | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 985da464..f3c55ae2 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -35,19 +35,17 @@ WIP >>>>>>>>>>>>> todo: move the dbid to the very first position in the shareit order additional fields as only the first two will show in email and reporting todo: register domain name myayanova.com for hanging subscriber servers off of -todo: rockfish not putting time limit on subscription keys, UI needs additions and shit for that +todo: IMPORTANT! rockfish not putting time limit on subscription keys, UI needs additions and shit for that todo: restrict superuser account in some critical ways so it can't be used for day to day work, maybe no dashboard etc nothing too serious that it breaks existing code but remove any features that it shouldn't be used for Find a subtle way to do this particularly for subscription users -todo: superuser consuming a license theoretically but shouldn't so in a subscription mode it needs to be locked down as to what it can be used for, some critical features should block it from use - fuck! Actually, just automatically deduct it from the count, whatever the count is remove one for superuser (or maybe in query filter OUT the superuser id 1!!!!) -todo: customer contact consuming a subscription license always because it doesn't knwo if they are a login or just a contact, maybe solution is to not set a login name if they arebn't a login customer - and change the counting code to ignore no login name users (but only for the customer contact count, not the inside staff count or that would be used to circumvent licening (or do we care? hmmm)) todo: active users in terms of license data should not show in log only on boot but also in the about page (not license because it would confuse people) since it's relevant and we need to know it right away - + +todo: IMPORTANT UPDATE manual, screenshots regarding Customer contact user and regular user and AllowLogin property added!!! + Also license related info about how to free up a user for licensing and how users consume licenses todo: TEST subscription and perpetual license code Does new boot code still work when no database? @@ -56,7 +54,7 @@ todo: TEST subscription and perpetual license code Does it prevent changing a user type? (direct db meddling) Does it prevent installing a new license when too few for existing active? Does it communicate this well to the user? - + Test the living fuck out of this from the NEXT deployment before any hint of live posting as there are so many changes it's necessary