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

[Extensions] Still problems with non-compatible version of modules, refs #843, #925 #1014

Closed
cmfcmf opened this issue Aug 27, 2013 · 14 comments
Labels
Milestone

Comments

@cmfcmf
Copy link
Contributor

cmfcmf commented Aug 27, 2013

  • Download MuBoard (which has core_max = 1.3.5)
  • Go to Extensions->view()
  • State of MuBoard is Not allowed => That's wrong. It should say Incompatible
  • Refresh page
  • State of Muboard is Incompatible => That's ok and expected
  • Change the core_max to 1.3.99 in Version.php (simulating you downloaded a newer version)
  • State of MuBoard now keeps beeing Not allowed

@phaidon You recently changed the code in #843, #925. Please take a look again.

@ghost ghost assigned phaidon Aug 27, 2013
@ghost
Copy link

ghost commented Sep 14, 2013

Is this still a problem?

@phaidon
Copy link
Contributor

phaidon commented Sep 14, 2013

I think so, because I also had this problem, some days ago.

@craigh
Copy link
Member

craigh commented Dec 21, 2013

The first part of this is still true ("not allowed") but the last part has been corrected (it says "New Version")

@craigh
Copy link
Member

craigh commented Dec 21, 2013

However, even if the module is never installed and the files removed, the state is changed to "Files Missing" which is also incorrect. I think there is a related ticket for that.

@craigh
Copy link
Member

craigh commented Jan 8, 2014

refs #1278

@craigh
Copy link
Member

craigh commented Jun 12, 2014

@cmfcmf @phaidon what is the state of this ticket? Can it be closed?

@cmfcmf
Copy link
Contributor Author

cmfcmf commented Jun 12, 2014

You would need to check if the issue still exists, I don't think it's been fixed.

@phaidon
Copy link
Contributor

phaidon commented Jun 12, 2014

i think the issue is not fixed, too.

@phaidon
Copy link
Contributor

phaidon commented Jun 23, 2014

For what is Not allowed ?
Is it identical with Incompatible?

@phaidon
Copy link
Contributor

phaidon commented Jun 24, 2014

ping @Drak @craigh @Guite @cmfcmf

@cmfcmf
Copy link
Contributor Author

cmfcmf commented Jun 24, 2014

For what is Not allowed ?
Is it identical with Incompatible?

I don't know.

@Guite
Copy link
Member

Guite commented Jun 24, 2014

I also have no idea about this. Seems like this state is never set?

@craigh
Copy link
Member

craigh commented Jun 25, 2014

I've been working on some of this that might be related. I'll try to work on it some more in the next few days if I can.

@phaidon phaidon assigned craigh and unassigned phaidon Jun 29, 2014
@damon18
Copy link

damon18 commented Jul 16, 2014

I just tried to install the git version of Content on 1.4 and got incompatible, then deleted the files and it changed to Files Missing but is still in the extensions list and I don't see any way to remove it.

@craigh craigh removed their assignment Sep 10, 2014
Guite added a commit that referenced this issue Dec 8, 2014
Fix module list regeneration fixes #1014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants