matezznet Posted April 23, 2011 Share Posted April 23, 2011 After using v1.4.1 for short time I cant see installed modules in module tab - the page is blank. I found 2 similar cases desribed in this forum, but with different error messages. My error message is Fatal error: Cannot redeclare non static CarrierModule::$limited_countries as static Dejala::$limited_countries in D:\xampplite\htdocs\prestashop\classes\Module.php(492) : eval()'d code on line 17Can someone help me pls ? Link to comment Share on other sites More sharing options...
shokinro Posted April 23, 2011 Share Posted April 23, 2011 From the error message, it seem the problem is caused by module dejala.Try to remove this module physically from /modules/ folder to see if the error disappear. Link to comment Share on other sites More sharing options...
matezznet Posted April 24, 2011 Author Share Posted April 24, 2011 thanks, I deleted the module and it works now. I don't know what caused this error, only thing which come to my mind is that I used automatic google translation for modules. Link to comment Share on other sites More sharing options...
shokinro Posted April 24, 2011 Share Posted April 24, 2011 glad to know you problem is solved.It will be great if you could mark this thread as SOLVED, thanks. Link to comment Share on other sites More sharing options...
M3tees Posted April 27, 2011 Share Posted April 27, 2011 Hi I am having the same issue except in my back office when i click on the module tab just no modules show up. Like the tab and everything works but It just says modules with no listing of my modules. Whats wrong? Link to comment Share on other sites More sharing options...
shokinro Posted April 27, 2011 Share Posted April 27, 2011 try increase memory in PHP.ini file Link to comment Share on other sites More sharing options...
shacker Posted April 27, 2011 Share Posted April 27, 2011 Thanks for the help. This is a bug in presta 1.4.1?in 1.4.0.17 dont happend Link to comment Share on other sites More sharing options...
shokinro Posted April 27, 2011 Share Posted April 27, 2011 There are multiple scenario could cause the same result.It also happens in 1.4.0.17. If you search in forum, you can find a few of similar issues reported on 1.4.0.17. 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