#6321 Prevent multiple installation of single instance tools

unreleased
duplicate
nobody
support (446) p3 (267)
General
nobody
2015-03-20
2013-06-03
Chris Tsai
No

There are a number of tools that only make sense to have a single instance of (ie., multiple copies create more menu items, but they affect the same data).

We should prevent more than one instance of these tools.

  • higher priority (since these are anchored and can't be removed once installed): Summary, Files, Reviews, Support
  • lower priority (since you can just remove extra instances): mailing lists, mysql, prweb outgoing mail, vhost

See [#6320] for clean-up

Related

Tickets: #5502

Discussion

  • Chris Tsai - 2013-06-03
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -4,3 +4,5 @@

 * higher priority (since these are anchored and can't be removed once installed): Summary, Files, Reviews, Support
 * lower priority (since you can just remove extra instances): mailing lists, mysql, prweb outgoing mail, vhost
+
+See [#6320] for clean-up
     

  • Dave Brondsema

    Dave Brondsema - 2013-06-03

    I think this could be implemented nicely as a generic method on App like can_install or something like that, so an app can have a custom implementation if needed. The default implementation could check for a max_instances attribute and see if that is reached yet. Then most apps could just specify max_instances=1

    can_install (or whatever it's named) could possibly incorporate other existing checks too, like the status property or installable property. Maybe even can_install could be better named as @property installable ...

     

  • Dave Brondsema

    Dave Brondsema - 2013-08-09
    • status: open --> duplicate
    • Milestone: limbo --> forge-aug-09
     

  • Dave Brondsema

    Dave Brondsema - 2013-08-09

    Same as [#5502]

     

    Related

    Tickets: #5502

Log in to post a comment.