System Update : Namespace Collision for Plugins
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Description
This is a very low priority issue.
I created a quick plugin today for a client and I was being lazy can called it Contact Form (contact-form). I generally namespace my plugins with my initials (even though they are primary for internal use only), but today I was lazy.
Upon completion of my plugin, I noticed a bunch of updates in the utilities. I had nine updates for a contact form plugin that I didn’t create or download. It appears to be the contact form for CraftCMS 2... that was created by Pixel&Tonic. Please see screenshot.
I know this issue could be very easily avoided by name spacing your plugin correctly, but I thought I should report so it is known for anyone else and for a possible explanation of what could be occurring.
Steps to reproduce
- Create a plugin called Contact Form
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are identified in the issue. Start by reproducing the collision with a plugin named Contact Form and inspect why updates for the unrelated CraftCMS 2 plugin appear. Define the expected update behavior before locating the relevant plugin update code and adding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100