-
Notifications
You must be signed in to change notification settings - Fork 66
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
Comments
Is this still a problem? |
I think so, because I also had this problem, some days ago. |
The first part of this is still true ("not allowed") but the last part has been corrected (it says "New Version") |
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. |
refs #1278 |
You would need to check if the issue still exists, I don't think it's been fixed. |
i think the issue is not fixed, too. |
For what is |
I don't know. |
I also have no idea about this. Seems like this state is never set? |
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. |
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. |
Fix module list regeneration fixes #1014
MuBoard
(which hascore_max
=1.3.5
)MuBoard
isNot allowed
=> That's wrong. It should sayIncompatible
Muboard
isIncompatible
=> That's ok and expectedcore_max
to1.3.99
inVersion.php
(simulating you downloaded a newer version)MuBoard
now keeps beeingNot allowed
@phaidon You recently changed the code in #843, #925. Please take a look again.
The text was updated successfully, but these errors were encountered: