wxanl Posted July 28, 2014 Share Posted July 28, 2014 Hello, i recently installed prestashop afgter some years of absence. I am running version 1.6.0.8 with default-bootstrap theme. All worked fine but all of a sudden the module page is all wrong. It looks like there is no layout or style information available anymore and so i am unable to use any link on that page or configure a module.I allready re-uploaded the Original admin theme but that did not help. Anyone haveing the same problems or could point me in the right direction please ? Link to comment Share on other sites More sharing options...
NemoPS Posted July 28, 2014 Share Posted July 28, 2014 Try enabling error reporting, there might be a broken module (check my signature) Link to comment Share on other sites More sharing options...
wxanl Posted July 28, 2014 Author Share Posted July 28, 2014 Hi Nemo and thanx, i did enable error reporting and tried to log on. I get an error right away and cannot log in. Might not be related but ...Notice: Use of undefined constant _RIJNDAEL_KEY_ - assumed '_RIJNDAEL_KEY_' in DUMMYPATH/public_html/classes/Cookie.php on line 80 Notice: Use of undefined constant _RIJNDAEL_IV_ - assumed '_RIJNDAEL_IV_' in DUMMYPATH/public_html/classes/Cookie.php on line 80 Link to comment Share on other sites More sharing options...
NemoPS Posted July 28, 2014 Share Posted July 28, 2014 ah, easy fix, open that cookie.php file, and there you have $this->_cipherTool = new Rijndael(_RIJNDAEL_KEY_, _RIJNDAEL_IV_); change it to $this->_cipherTool = new Rijndael('_RIJNDAEL_KEY_', '_RIJNDAEL_IV_');v Link to comment Share on other sites More sharing options...
wxanl Posted July 28, 2014 Author Share Posted July 28, 2014 Thank you I can once again log in. The module page error is still there .... I do however notice a message that a certain module might be unsafe. Does not show the name or anything but only qoutes.This module is Untrusted You are about to install "", a module that could not be securely identified by PrestaShop.This generally happens when the module is not distributed through our official marketplace, PrestaShop Addons - or when your server failed to communicate with PrestaShop Addons. Since you did not download the module from PrestaShop Addons, we cannot assert that the module is safe (i.e. that it is not adding some undisclosed functionality like backdoors, ads, hidden links, spam, etc.). Use at your own risk. Link to comment Share on other sites More sharing options...
NemoPS Posted July 30, 2014 Share Posted July 30, 2014 Yeah you can ignore that, it just means that module has not been purchases through the addons store Link to comment Share on other sites More sharing options...
wxanl Posted July 30, 2014 Author Share Posted July 30, 2014 Thank you. Problem still exists though. Is there nobody with any idea what to do (except fresh install) ?? Link to comment Share on other sites More sharing options...
NemoPS Posted July 30, 2014 Share Posted July 30, 2014 You mean this? Notice: Use of undefined constant _RIJNDAEL_KEY_ - assumed '_RIJNDAEL_KEY_' in DUMMYPATH/public_html/classes/Cookie.php on line 80 Notice: Use of undefined constant _RIJNDAEL_IV_ - assumed '_RIJNDAEL_IV_' in DUMMYPATH/public_html/classes/Cookie.php on line 80 Link to comment Share on other sites More sharing options...
wxanl Posted July 30, 2014 Author Share Posted July 30, 2014 No, i mean the original problem with the corrupt module page .... my first post including screenshot .... Link to comment Share on other sites More sharing options...
NemoPS Posted July 30, 2014 Share Posted July 30, 2014 SO that page with no errors, even when error reporting is enabled? Link to comment Share on other sites More sharing options...
wxanl Posted July 30, 2014 Author Share Posted July 30, 2014 That is correct, not in IE and not in Chrome ... Link to comment Share on other sites More sharing options...
NemoPS Posted July 31, 2014 Share Posted July 31, 2014 Can you try opening the chrome's debug console (f12) and see which css files are included in the page? Link to comment Share on other sites More sharing options...
wxanl Posted July 31, 2014 Author Share Posted July 31, 2014 I think that is the problem exactly. There are no css files at all. As i stated in my initial post, i allready did try to upload the Original admin theme files but that did not work. I believe there is some CSS file missing somewhere, i just don't know which one .... Link to comment Share on other sites More sharing options...
NemoPS Posted August 1, 2014 Share Posted August 1, 2014 The css wouldn't display in other pages either in that case, but just to be sure, can you check that admin-theme.css sits in the admin folder/themes/default/css ? You can try embedding it by hand inside default/template/header.tpl at this point Link to comment Share on other sites More sharing options...
wxanl Posted August 1, 2014 Author Share Posted August 1, 2014 I just checked and found that the .css file is present at the location you mentioned. Adding the css file manually to header.tpl did not do anything at all. I did install a test version on a different server to compare files and be able to copy files from test to live if necessary. Link to comment Share on other sites More sharing options...
NemoPS Posted August 2, 2014 Share Posted August 2, 2014 Try copying them at this point, I'm bugged it still doesn't work. Maybe permission level? Link to comment Share on other sites More sharing options...
wxanl Posted August 2, 2014 Author Share Posted August 2, 2014 I don't get it either. It worked in the beginning. and i did not change any permission at all, but will check that also. Link to comment Share on other sites More sharing options...
MarkusVisse Posted September 4, 2014 Share Posted September 4, 2014 (edited) Hi, have found out what is wrong? the problem is not that there is no CSS included, the whole HEADER.tpl is not being included, tha page starts from div, not <html Same here and im freaking out now EDIT: A FIX HAS BEEEN FOUND! More like workaround: copy the contents (without begining comment) from <admin catalog>/themes/default/template/header.tpl to <admin catalog>/themes/default/template/controllers/modules/header.tpl after the begining comment and voila, works like a charm! Glad I've found it Edited September 4, 2014 by MarkusVisse (see edit history) 2 Link to comment Share on other sites More sharing options...
wxanl Posted September 5, 2014 Author Share Posted September 5, 2014 Hi, have found out what is wrong? the problem is not that there is no CSS included, the whole HEADER.tpl is not being included, tha page starts from div, not <html Same here and im freaking out now EDIT: A FIX HAS BEEEN FOUND! More like workaround: copy the contents (without begining comment) from <admin catalog>/themes/default/template/header.tpl to <admin catalog>/themes/default/template/controllers/modules/header.tpl after the begining comment and voila, works like a charm! Glad I've found it Thank a lot for answering this thread and delivering a solution. Unfortunately i did not have the time and patience to wait for a solution. So i did wipe the whole installation and started all over again... However, i appreciate your time and effort answering this thread very much. Link to comment Share on other sites More sharing options...
Recommended Posts