Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-4263

Import Manager: Add Plesk18 mapping file to WHMCS importer.

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.0
    • Fix Version/s: 5.1.0-b2
    • Component/s: Plugins
    • Labels:
      None

      Description

      Plesk services are currently being imported using the Universal Module, and not the Plesk module. This is because there are several plesk mapping files in /plugins/import_manager/components/migrators/whmcs/config/ including:

      plesk8.php
      plesk9.php
      plesk10.php

      Cloning plesk10.php to plesk18.php and replacing this on line 2: plesk10.map to: plesk18.map resolved the issue and properly imported Plesk services using the Plesk module.

      The field mappings have no changed, so it would be ideal if future versions of Plesk could fallback to this new mapping file.

      UPDATE: It appears the customer cloned plesk10.php to plesk.php and set plesk18.map in the file AND set the API version to "". I'm not sure where they did that. Probably should test this.

        Activity

        Hide
        abdy Abdy Franco added a comment -

        The mapping files, seems to be almost identical. I think a possible solution would be to unify these files into one and get the API version through an API call as suggested by the customer, this way we won't require a mapping file for each version.

        Show
        abdy Abdy Franco added a comment - The mapping files, seems to be almost identical. I think a possible solution would be to unify these files into one and get the API version through an API call as suggested by the customer, this way we won't require a mapping file for each version.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              17/Jun/21

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 2 hours, 50 minutes
              1d 2h 50m

                Agile