admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Allow login checked properly for license in subscription customer contact count check

Browse Source
This commit is contained in:
John Cardinal
2022-08-29 14:55:24 +00:00
parent 808aa574d7
commit 9b7508afe3
3 changed files with 23 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
devdocs/todo.txt
View File

@@ -34,38 +34,11 @@ WIP >>>>>>>>>>>>>
Status: updated on devlops to 8.0.7, testing first subscription HUGE generation...
Status: Test recent change to customer login license check making new user or setting to active or setting to allowlogin
Also in between times fixup the additional fields in product pages for sale see item in parallel work section below (and see if can change price on subscription or do I need to make a new one?)
todo: TEST subscription and perpetual license code LOCALLY "yes" / then posted hosted "YASS"
Does a trial request for sbuscription work? YES YASS
Correct date range? YES YASS
Generate data? YES YASS
v8migrate work? YES YASS
Can generate HUGE data set on trial? YES
Can generaet small data set right after HUGE one? (test of delete empty database timeout issue) YES
Does a trial request for perpetual work? YES
correct date range? YES
Generate data? YES
v8migratework? YES
Can generate HUGE data set on trial? YES
Can generaet small data set right after HUGE one? YES (test of delete empty database timeout issue)
Can I bump a trial subscription and / or perptual expiration date if a trialer needs more time!!! IMPORTANT, this way can keep it brief but allow for wiggle
YES BUT it must not be a TRIAL key, it can be a full key that is time restricted but not flagged trial as raven prevents a trial key being used with a non empty db
Does new boot code still work when no database? YES
Does new boot code work to prevent running if wrong build or maint date expired vs build date?
Does it prevent changing a user to active?
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
REBUILD POST TO NEXT TEST ALL OF ABOVE AGAIN ON HOSTED SERVER
todo: Test how to revoke a license, I'm wondering if new code at license.cs is now preventing installing the revoke license
NOTE: NOT RELEASABLE, MANUAL NEEDS TO BE UPDATED FIRST THEN CAN REBUILD AND POST