Originally created by: sf-overlords
Created by: jbeard
Created date: 2010-03-10 20:39:28.930000
Assigned to:nobody
When installing a plugin with a particular mount point name, if that mount point is the same as a current subproject, it will allow the addition of the plugin -- but any attempt to access it will redirect to the subproject
Originally by: sf-overlords
Post by max:
It doesn't work this way anymore. Some time ago I added an assertion so now it fails with AssertionError when you try add a plugin with the same mount point.
It's still not very user-friendly. I'd fix but but pls review my mi/79 branch first; I'd build on top of that. Otherwise I'll just be creating a merge conflict for me.
Originally by: sf-overlords
Post by mramm:
Originally by: sf-overlords
Post by mramm:
So, what we should do is just check and error out if there is a collision.
Originally by: sf-overlords
Post by max:
Originally by: sf-overlords
Post by max:
Originally by: sf-overlords
Post by mramm:
status: accepted --> closed
milestone: someday-maybe --> public1
custom_field__size: --> 0