500 error. This must be wrong

[Havouza]

Still struggling with my shop transfer and now I think I have found the problem.
The below is from an event log for today. The path to the files is from the OLD shop, not the NEW. Where do I define this? its probably done automatic when you install a shop and now get wrong.

 

*ERROR* 	2019/04/27 - 14:23:09: load error: failed to find /var/www/vhosts/jv74.se/httpdocs/modules/footercustom/views/css/front/less/default.less at line 1417 in file modules/footercustom/lessc.inc.php

 

[Scully]

The error comes from a non-standard module named

footercustom

You might want to try to uninstall this module properly.

[Havouza]

No I dont think so. The path to the shop is Not var/www/vhosts/. That is from the old server and must be stored somewhere. The new path is /home/jv74/public_html. I need to find where to change

[Billy]

Can you open that module and change the path?

If not then you need to define proper path the old fashion way in the file

lessc.inc.php

[Havouza]

where do I find that file?

 

[Billy]

public_html/modules/footercustom/lessc.inc.php

[Billy]

at line 1417

[Havouza]

line 1416-1417

        if (!is_readable($fname))
            throw new Exception('load error: failed to find '.$fname);

[Havouza]

That path must be stored somewhere when youninstall. And there is no possibility to change it via the module. I checked in the working shop that we try to move

Edited April 27, 2019 by Havouza
More info

[Billy]

What if you reset your theme in modules admin? Sometimes this has messed up more than it has fixed for me personally. Yet on the other side of the coin hopefully you have a clone of your main site to test! @Havouza good luck!

Front office Features

Theme Configurator v3.0.8 - by thirty bees

[Billy]

Wait @Havouzareset your module first! I'm sorry

[Havouza]

I have no access to the new shop

 

[Havouza]

The new shop is a clone of the old working one

[Havouza]

My question is where the path in the variable is picked up from. If I can find that I think the problem is solved

This variable picks up the pathinfo somewhere

       $fname
         

 

Edited April 27, 2019 by Havouza

[Havouza]

Just to clarify

$fname = pathinfo
 

Old shop it was /var/www/vhosts/jv74.se/httpdocs/
New shop is /home/admin_jv74/public_html/
But the new shop picks the old pathinfo somewhere. That is the problem which has to be solved

[Billy]

You got me on this & i can only offer up google searches now besides saying the obvious did you dump all cache including browser.

Anyway

https://www.google.com/search?ei=43PEXOPzKOWH_QbfvomYCg&q=prestashop+load+error%3A+failed+to+find+%2Fvar%2Fwww%2Fvhosts&oq=prestashop+load+error%3A+failed+to+find+%2Fvar%2Fwww%2Fvhosts&gs_l=psy-ab.3...15426.18445..18953...0.0..0.351.2144.0j9j0j2......0....1..gws-wiz.vG5jTQIn_sg

https://www.google.com/search?ei=eXjEXMfoB-LD_Qa_5ZW4Dw&q=path+to+php+variable+prestashop&oq=path+to+php+variable+prestashop&gs_l=psy-ab.3...166264.167526..167986...0.0..0.131.468.0j4......0....1..gws-wiz.......0i71j35i304i39.r0gEyjiKUqI

https://www.google.com/search?ei=J3rEXOr8AtGc_QaVy57IBQ&q=path+to+smarty+variable+prestashop&oq=path+to+smarty+variable+prestashop&gs_l=psy-ab.3...34685.37914..38598...0.0..0.400.2370.0j3j2j3j1......0....1..gws-wiz.......35i39.AAcyJ4gr8kU

[Havouza]

yes i dumped all.
It is interesting because this will be a problem if you clone  somewthing to a new server where the path to the web will not be the same as the old one. But somewhere the info is stored. I start to belive it is stored in the db somewhere. I go through the config table now to see if I get lucky

[Havouza]

Some of the developers must know where the pathinfo is stored

[datakick]

This is problem of this particular module, not thirtybees issue. Module saved some info somewhere, it has total autonomy in this area. Tb / prestashop has no way to intervene.

So, you need to look into module source code, or contact module developer.

Nobody can help you without access to the module code.

[musicmaster]

This shouldn't be so difficult. Just do a search for '%jv74.se%' in phpmyadmin in the whole database and do a text string for 'jv74.se' with Astrogrep in the whole shop. 

And you don't need the life shop for that. A working copy on you local computer (localhost) would do - as long as it doesn't contain a path with that string.

[Havouza]

Well database has no hits and I have no windowscomputer, run linux so Astrogrep is no solution. But can I do the same search using only Grep via ssh? How?

[musicmaster]

I seldom use grep. So I would have to consult the manual. It will be faster if you do that yourself.

[Havouza]

Well the answers via grep is confusing. But I will try another path and change the document root in the new apache to follow the old one

[Billy]

When you cleared cache did you clear the cache in your /themes/your_theme_name/cache folder manually.

 

https://www.prestashop.com/forums/topic/292037-solved-removed-testdomain-now-the-real-one-wont-work/

Edited April 28, 2019 by Script-Fu
Corrected path to theme cache.

[Havouza]

Hi!
That I did not do. The cache file for the footer has this line in it. Can this be the culprit?

;s:5:"files";a:2:{s:87:"/var/www/vhosts/jv74.se/httpdocs/modules/footercustom/views/css/front/less/default.less";i:1503588736;s:96:"/var/www/vhosts/jv74.se/httpdocs/modules/footercustom/views/css/front/less/variables-mixins.less";i:1503588736;}s:7:"updated";i:1556451505;}

[Billy]

Best thing to do is dump all the cache in this folder /themes/your_theme_name/cache manually

Also clear /cache/smarty/cache & /cache/smarty/compile manually

Then your browser cache and see if you still have error 500

 

Best