Answers.Body: <p>You're not gonna like this answer, but... rename your plugin. There's no way to reasonably circumvent <em>all</em> of the conflicts you're going to run into by keeping the same name as an existing public plugin.</p>
  <p>If it's a private plugin that you're only using on a single site, consider converting it into a module instead.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-14T08:08:36.480Z
Answers.Text: Ok, we thought so as well. But how do we do that, without losing data? Renaming it in its plugin files is easy, but what about the databesshizzle?
Answers.UserDisplayName: Marten Brosch
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-14T20:02:39.357Z
Answers.Text: The database impact should be minimal. At worst, maybe you manually adjust a few table names, and/or write some migrations to handle the transition.
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-12T17:53:13.330Z
Answers.LastActivityDate: 2020-08-12T17:53:13.330Z
Answers.UserDisplayName: Lindsey D
Body: <p>We developed a plugin with the name &quot;poll&quot; (composer.json: webhub/poll) for one single project. Now we get the licence error in the control panel, cause there is a plugin to buy which has got the same name (<a href="https://plugins.craftcms.com/poll" rel="nofollow noreferrer">https://plugins.craftcms.com/poll</a>).</p>
  <p>First Problem: ./craft update all wants to update our plugin: poll 0.0.1 =&gt; 1.2.5 but we really do not have a version 1.2.5.</p>
  <p>Second Problem: at the control panel plugins page, we have our plugin listed, but with an licence-code-input-field and the error message, that we don't have a licence.</p>
  <p>The Reason for all of this is, that we picked the wrong name for our plugin, but renaming it is a pretty dirty task. Does anyone has a got a better idea?</p>
  <p>The composer.json looks like this:</p>
  <pre><code>{
    &quot;require&quot;: {
      &quot;aws/aws-php-sns-message-validator&quot;: &quot;^1.6&quot;,
      &quot;carlcs/craft-redactorcustomstyles&quot;: &quot;3.0.4&quot;,
      &quot;cavellblood/craft-string-base64&quot;: &quot;1.0.1&quot;,
      &quot;codemonauts/craft-instagram-feed&quot;: &quot;1.0.5&quot;,
      &quot;craftcms/cms&quot;: &quot;3.5.3&quot;,
      &quot;craftcms/redactor&quot;: &quot;2.7.0&quot;,
      &quot;doublesecretagency/craft-matrixcolors&quot;: &quot;2.0.1&quot;,
      &quot;ether/seo&quot;: &quot;3.6.6&quot;,
      &quot;hybridinteractive/craft-position-fieldtype&quot;: &quot;1.0.16&quot;,
      &quot;meyfa/php-svg&quot;: &quot;^0.9.0&quot;,
      &quot;mildlygeeky/craft-redactor-script-buttons&quot;: &quot;1.1.1&quot;,
      &quot;mmikkel/cp-field-inspect&quot;: &quot;1.2.0&quot;,
      &quot;percipioglobal/craft-colour-swatches&quot;: &quot;^1.2&quot;,
      &quot;studioespresso/craft-dumper&quot;: &quot;2.0.0&quot;,
      &quot;topshelfcraft/environment-label&quot;: &quot;3.2.0&quot;,
      &quot;verbb/expanded-singles&quot;: &quot;1.1.3&quot;,
      &quot;verbb/super-table&quot;: &quot;2.6.0.4&quot;,
      &quot;vlucas/phpdotenv&quot;: &quot;^2.4.0&quot;,
      &quot;webhub/poll&quot;: &quot;0.0.1&quot;,
      &quot;webhub/super-sticker-generator&quot;: &quot;^0.0.1&quot;
    },
    &quot;autoload&quot;: {
      &quot;psr-4&quot;: {
        &quot;modules\\laravelmixmodule\\&quot;: &quot;modules/laravelmixmodule/src/&quot;
      }
    },
    &quot;config&quot;: {
      &quot;sort-packages&quot;: true,
      &quot;optimize-autoloader&quot;: true,
      &quot;platform&quot;: {
        &quot;php&quot;: &quot;7.0&quot;
      }
    },
    &quot;scripts&quot;: {
      &quot;post-root-package-install&quot;: [
        &quot;@php -r \&quot;file_exists('.env') || copy('.env.example', '.env');\&quot;&quot;
      ]
    },
    &quot;repositories&quot;: [
      {
        &quot;type&quot;: &quot;path&quot;,
        &quot;url&quot;: &quot;./plugins/*&quot;
      }
    ],
    &quot;require-dev&quot;: {
      &quot;codeception/codeception&quot;: &quot;^3.1&quot;
    }
  }
  
  </code></pre>
  
Tags: <plugin-development><craft3><plugins>
Title: Licence error and update issue cause of same plugin name / handle
ThreadText: # Licence error and update issue cause of same plugin name / handle
  
  (Asked by: username_0 on 2020-08-12)
  
  We developed a plugin with the name "poll" (composer.json: webhub/poll) for one single project. Now we get the licence error in the control panel, cause there is a plugin to buy which has got the same name (<https://plugins.craftcms.com/poll>).
  
  First Problem: ./craft update all wants to update our plugin: poll 0.0.1 => 1.2.5 but we really do not have a version 1.2.5.
  
  Second Problem: at the control panel plugins page, we have our plugin listed, but with an licence-code-input-field and the error message, that we don't have a licence.
  
  The Reason for all of this is, that we picked the wrong name for our plugin, but renaming it is a pretty dirty task. Does anyone has a got a better idea?
  
  The composer.json looks like this:
  
  ```
  {
    "require": {
      "aws/aws-php-sns-message-validator": "^1.6",
      "carlcs/craft-redactorcustomstyles": "3.0.4",
      "cavellblood/craft-string-base64": "1.0.1",
      "codemonauts/craft-instagram-feed": "1.0.5",
      "craftcms/cms": "3.5.3",
      "craftcms/redactor": "2.7.0",
      "doublesecretagency/craft-matrixcolors": "2.0.1",
      "ether/seo": "3.6.6",
      "hybridinteractive/craft-position-fieldtype": "1.0.16",
      "meyfa/php-svg": "^0.9.0",
      "mildlygeeky/craft-redactor-script-buttons": "1.1.1",
      "mmikkel/cp-field-inspect": "1.2.0",
      "percipioglobal/craft-colour-swatches": "^1.2",
      "studioespresso/craft-dumper": "2.0.0",
      "topshelfcraft/environment-label": "3.2.0",
      "verbb/expanded-singles": "1.1.3",
      "verbb/super-table": "2.6.0.4",
      "vlucas/phpdotenv": "^2.4.0",
      "webhub/poll": "0.0.1",
      "webhub/super-sticker-generator": "^0.0.1"
    },
    "autoload": {
      "psr-4": {
        "modules\\laravelmixmodule\\": "modules/laravelmixmodule/src/"
      }
    },
    "config": {
      "sort-packages": true,
      "optimize-autoloader": true,
      "platform": {
        "php": "7.0"
      }
    },
    "scripts": {
      "post-root-package-install": [
        "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
      ]
    },
    "repositories": [
      {
        "type": "path",
        "url": "./plugins/*"
      }
    ],
    "require-dev": {
      "codeception/codeception": "^3.1"
    }
  }
  
  ```
  
  **Tags:** plugin-development, craft3, plugins
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-08-12. Score: 1
  
  You're not gonna like this answer, but... rename your plugin. There's no way to reasonably circumvent *all* of the conflicts you're going to run into by keeping the same name as an existing public plugin.
  
  If it's a private plugin that you're only using on a single site, consider converting it into a module instead.
  
  > **Comments:**
  > **username_0**: Ok, we thought so as well. But how do we do that, without losing data? Renaming it in its plugin files is easy, but what about the databesshizzle?  
  > **username_1**: The database impact should be minimal. At worst, maybe you manually adjust a few table names, and/or write some migrations to handle the transition.  
  
  ---
  
  