[SOLVED] Removed testdomain, now the real one won't work

[midana]

I moved the whole prestashop public files to my normal domain from my test(sub)domain, changed the urls in database and htaccess and in admin. Everything worked well until I removed the subdomain completely. Then this happens when I try to access the store:

 

Fatal error: Uncaught exception 'Exception' with message 'load error: failed to find /storage/content/45/101045/testsub.censored.com/public_html/modules/prestacreathememanager/theme/less/theme-global.less' in /storage/content/45/101045/censored.com/public_html/modules/prestacreathememanager/lessc.inc.php:1527 Stack trace: #0 /storage/content/45/101045/censored.com/public_html/modules/prestacreathememanager/lessc.inc.php(1582): lessc->compileFile('/storage/conten...') #1 /storage/content/45/101045/censored.com/public_html/modules/prestacreathememanager/prestacreathememanager.php(654): lessc->cachedCompile(Array) #2 /storage/content/45/101045/censored.com/public_html/modules/prestacreathememanager/prestacreathememanager.php(679): PrestacreaThemeManager->cacheCompileLess('/storage/conten...', '/storage/conten...') #3 /storage/content/45/101045/censored.com/public_html/classes/Hook.php(459): PrestacreaThemeManager->hookHeader(Array) #4 /storage/content/45/101045/wlifes in /storage/content/45/101045/censored.com/public_html/modules/prestacreathememanager/lessc.inc.php on line 1527

 

 

Please help :/

[vekia]

hello

 

it looks like problem with non default module named prestacreathememanager

 

have you tried to contact with module developer? i think that module author will know what's going on there, because we don't know this addon, how it works and what it does

[midana]

Apparently it was a problem with the cache, there were cache in different module directories that needed to be removed. These had the old domain properties in them.

[lofromfar]

Hi there,

 

I currently meet the same issue, but I don't find which files I'm supposed to remove... Could you help me if you found the solution to this problem ?

Thank you very much !!

[system_error86]

hello i Have same problem! Any issue ? 

 

 Please help!!!!!!!!!!!!

 

Fatal error: Uncaught exception 'Exception' with message 'load error: failed to find /home/public_html/somefolder/modules/categoriestopmenu/css/less/default.less' in /home//public_html/modules/prestacreathememanager/lessc.inc.php:1527 Stack trace: #0 /home//public_html/modules/prestacreathememanager/lessc.inc.php(1582): lessc->compileFile('/home//p...') #1 /home//public_html/modules/categoriestopmenu/categoriestopmenu.php(434): lessc->cachedCompile(Array) #2 /home//public_html/modules/categoriestopmenu/categoriestopmenu.php(450): CategoriesTopMenu->cacheCompileLess('/home//p...', '/home//p...') #3 /home//public_html/classes/Hook.php(500): CategoriesTopMenu->hookHeader(Array) #4 /home//public_html/classes/controller/FrontController.php(443): HookCore::exec('displayHeader') #5 /home//public_html/controllers/front/IndexController.php(37): FrontControllerCore->initContent() #6 /home//public_html/classes/controller/Controller.php(180): IndexContro in /home//public_html/modules/prestacreathememanager/lessc.inc.php on line 1527 

[lofromfar]

Hi,

 

I solved the problem by emptying the following folders :

/modules/categoriestopmenu/css/less

/modules/customblocks/css/less/

/modules/prestacreathememanager/theme/less/

/modules/prettyslider/css/less/

 

Be careful, this solved the problem but in my case, for an unknown reason, all my CSS (I had to change some properties for biocosmetic) disappeared and I had to re-do it. Save all CSS changes in another folder befoire doing this !

 

Hope this helped !

[system_error86]

Thank you a lot lofromfar! I tried something similar. I uninstalled these modules and I reinstalled them and it works but I lost the css only from the footer so I restored from my backup the hole css and it is OK now thank you so much

[PascalVG]

Sounds like this topic is solved for everyone. Will change the title accordingly.

 

Happy selling!

pascal

[kleinermann]

For me it was enough to clear the module cache in the back-office. I just picked the modules throwing the error (example: categoriestopmenu) and clicked the Empty Cache button (see screenshot).