Details

    • Type: Improvement
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.3.0-b1
    • Fix Version/s: 3.3.0-b1
    • Component/s: Modules
    • Labels:
      None

      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

          People

          • Assignee:
            cody Cody Phillips (Inactive)
            Reporter:
            cody Cody Phillips (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              27/Aug/14