Details
Improvement
Blocker
Description
Currently there is no way for a module to track client specific options that affect all services for that client and module (or module row). The primary benefit of which is to store client specific information for a set of services. For example, Plesk, SolusVM, and other modules require creating a single client account for multiple services.
This tasks adds a new module_client_meta table to hold this data.
client_id, module_id, module_row_id (0/optional), key, value, serialized, encrypted
This task also adds a ModuleClientMeta model class that allows modules to read/write options for this data store.
Activity
Cody Phillips (Inactive)
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Paul Phillips
made changes -
| Security | Private [ 10000 ] |
Cody Phillips (Inactive)
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Cody Phillips (Inactive)
made changes -
| Description |
Currently there is no way for a module to track client specific options that affect all services for that client and module (or module row). The primary benefit of which is to store client specific information for a set of services. For example, Plesk, SolusVM, and other modules require creating a single client account for multiple services.
This tasks adds a new *module_client_meta* table to hold this data. +client_id+, +module_id+, +module_row_id+ (null/optional), +key+, value, serialized, encrypted This task also adds a *ModuleClientMeta* model class that allows modules to read/write options for this data store. |
Currently there is no way for a module to track client specific options that affect all services for that client and module (or module row). The primary benefit of which is to store client specific information for a set of services. For example, Plesk, SolusVM, and other modules require creating a single client account for multiple services.
This tasks adds a new *module_client_meta* table to hold this data. +client_id+, +module_id+, +module_row_id+ (0/optional), +key+, value, serialized, encrypted This task also adds a *ModuleClientMeta* model class that allows modules to read/write options for this data store. |
Cody Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Currently there is no way for a module to track client specific options that affect all services for that client and module (or module row). The primary benefit of which is to store client specific information for a set of services. For example, Plesk, SolusVM, and other modules require creating a single client account for multiple services.
This tasks adds a new *module_client_meta* table to hold this data. +client_id+, +module_id+, +module_row_id+, +key+, value, serialized, encrypted This task also adds a *ModuleClientMeta* model class that allows modules to read/write options for this data store. |
Currently there is no way for a module to track client specific options that affect all services for that client and module (or module row). The primary benefit of which is to store client specific information for a set of services. For example, Plesk, SolusVM, and other modules require creating a single client account for multiple services.
This tasks adds a new *module_client_meta* table to hold this data. +client_id+, +module_id+, +module_row_id+ (null/optional), +key+, value, serialized, encrypted This task also adds a *ModuleClientMeta* model class that allows modules to read/write options for this data store. |
Cody Phillips (Inactive)
created issue -