bernhard Posted August 18, 2015 Share Posted August 18, 2015 i've encountered this error quite often when updating several projects last days... any ideas? updating to 2.6.1 went smoothly all the time. any help how i can debug this? thanks i could also share the installation as it is a test-environment Link to comment Share on other sites More sharing options...
bernhard Posted August 24, 2015 Author Share Posted August 24, 2015 today i moved my dev-project to my live server and i still have the same issue seems that i'm stuck with version 2.6.10 for now... it seems that its not a server issue. can anybody help me where i can start my researches please? Link to comment Share on other sites More sharing options...
bernhard Posted August 25, 2015 Author Share Posted August 25, 2015 ok after doing a modules > refresh all but one errors are gone: what does this error mean? is it critical? everything seems to work fine... it's even not visible when debugging is set to false... Link to comment Share on other sites More sharing options...
LostKobrakai Posted August 25, 2015 Share Posted August 25, 2015 This comes from the new "version change detection" addition from 2.6.10. It checks all modules if the version has changed and if so executes potential migration code. Link to comment Share on other sites More sharing options...
bernhard Posted August 25, 2015 Author Share Posted August 25, 2015 yes, but the red one that fails? Link to comment Share on other sites More sharing options...
LostKobrakai Posted August 25, 2015 Share Posted August 25, 2015 That one failed that exact check. For me that was mostly a matter of refreshing modules once or twice an they were gone, but I'm not sure what exactly could fail for those rarely changed core modules. 1 Link to comment Share on other sites More sharing options...
Jozsef Posted August 14, 2017 Share Posted August 14, 2017 Just had this problem after moving my site from localhost to the live server (v3.0.68 from PHP 5.6 to PHP 7.1).@LostKobrakai, your solution (refreshing the modules twice) sorted the error message and all module version changes registered properly. Thanks for the simple idea. Link to comment Share on other sites More sharing options...
TheMick Posted February 18, 2021 Share Posted February 18, 2021 I get this error after an update from a two weeks old 3.0.165 install to 3.0.172 for the LazyCron module: Configurable module check failed for LazyCron. Many (!!) times of Modules > Refresh did not change anything. Same with deinstalling and installing again. Any ideas what could be the reason or how to get rid of this error? Is there anything to worry about? Link to comment Share on other sites More sharing options...
bernhard Posted February 18, 2021 Author Share Posted February 18, 2021 Already reported ? Link to comment Share on other sites More sharing options...
TheMick Posted February 18, 2021 Share Posted February 18, 2021 Thanks for the info! Really searched quite a bit but did not find it. Having a look in corresponding the weekly update seems to be a good idea ? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now