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

Conflict when several plugin require the same dependency with different version #667

Open
lwszaremba opened this issue Jun 2, 2017 · 2 comments

Comments

@lwszaremba
Copy link

I see in register() function a plugin is simply ignored if slug already in the list.
What happen if a plugin require a greater version than another one? The first call is kept, the second is ignored.
So, it is better to be the first to talk (with a high priority), but it is in contradiction with walkthrough in issue #666

Should it be better to keep the settings of the plugin with greatest version instead simply ignoring it?

@jrfnl
Copy link
Contributor

jrfnl commented Jun 3, 2017

This is a known issue and will - eventually - be addressed by TGMPA v3.0. See #394

@mneitz
Copy link

mneitz commented May 19, 2018

I do have one base plugin which is requered for my other plugins - I am running into the same issue that the plugin is not shown if a different minimal version is used :(

Could you please provide and fix for that.
Many thx - Martin

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

3 participants