We have moved to Github. Please open tickets there.

Opened 2 years ago

Closed 2 years ago

#3306 closed Defect (wontfix)

unite require plugin + require priority in manifests

Reported by: ewinslow Owned by:
Priority: normal Milestone: Needs Review
Component: Core Version: Github Master
Severity: minor Keywords:
Cc: brett@… Difficulty:

Description (last modified by ewinslow)

It seems like "require" in both cases implies "require to be enabled", not just installed. This tells me they could simply be a unified xml object.

<requires>
    <type>plugin</type>
    <name>custom_index</name>
    <version>1.7</version>
    <comparison> >= </comparison>
    <priority>after</priority>
</requires>

Change History (3)

comment:1 Changed 2 years ago by ewinslow

  • Description modified (diff)

comment:2 Changed 2 years ago by cash

Brett - any thoughts on this?

comment:3 Changed 2 years ago by brettp

  • Resolution set to wontfix
  • Status changed from new to closed

You can write plugins that interact with or override aspects of other optional plugins. In that case, you want to require order but not active state. Gonna close this, but reopen if there needs to be more discussion.

Note: See TracTickets for help on using tickets.