Licence error and update issue cause of same plugin name / handle 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 (https://plugins.craftcms.com/poll).
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.
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:
{
  &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;
  }
}
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.