Trial period when enterprise is enabled should count from the moment enterprise was enabled, not when Grist was installed #1140
Labels
self-hosting
Self-hosting setup that needs some love
Comments
jordigh
moved this from Selected for development
to Backlog
in Improvements for self-hosting
jordigh
moved this from Backlog
to Selected for development
in Improvements for self-hosting
jordigh
moved this from Selected for development
to In Progress
in Improvements for self-hosting
jordigh
added a commit
that referenced
this issue
Aug 1, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 1, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 1, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 1, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 1, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 1, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 5, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 5, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 6, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
jordigh
added a commit
that referenced
this issue
Aug 6, 2024
For #1140, I considered trying to use the existing fields in a better way, but because we already use the activations table to store preferences, we need to keep all of the existing data and its usage as-is. The enterprise code will use this new column to decide how long the trial period should be.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Grist is first installed, an activation entity is created in the database with the current timestamp:
https://github.com/gristlabs/grist-core/blob/main/app/server/lib/FlexServer.ts#L767
This is the timestamp that is used to count the number of days in the trial period when enterprised is enabled.
It should instead be counting from the moment that the Enterprise toggle was hit.
The text was updated successfully, but these errors were encountered: