Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom plugins that share names with ones in the Plugin Store have name/update collisions #3751

Closed
aaronbushnell opened this issue Jan 30, 2019 · 2 comments

Comments

@aaronbushnell
Copy link
Contributor

Description

There are times we build a custom plugin for a client and don't intend to publish this to the Plugin Store. For instance, I may create a simple "Twitter" or "Weather" plugin. However, if there's already a "Twitter" or "Weather" plugin in the Plugin Store then I see the updates for that plugin in the "Updates" section of the control panel.

The same goes for the "Plugin" page. If I click the icon for the custom "Twitter" plugin it takes me to the Twitter plugin that currently exists in the Plugin Store.

Steps to reproduce

  1. Create a "Twitter" plugin using the Plugin Factory generator and ensure you set the version to 1.0.0
  2. Add it into a plugins directory in your Craft project
  3. Add the following to your composer.json:
"repositories": [
    {
      "type": "path",
      "url": "path/to/plugins/*"
    }
  ]
  1. Run composer require authorName/twitter
  2. Go to Utilities > Updates within the control panel
  3. You'll see the changelog for the actual "Twitter" plugin in the Plugin Store

Additional info

  • Craft version: 3.1.6.1
  • PHP version: 7.3.1
  • Database driver & version: MySQL 5.7.25
@brandonkelly
Copy link
Member

Duplicate of #3054 - see the discussion there.

@aaronbushnell
Copy link
Contributor Author

Ah, sounds like I oughta be utilizing Modules in place of Plugins to avoid this. Thanks, @brandonkelly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants