thehurricane Posted November 19, 2019 Share Posted November 19, 2019 Hello, I want to change template on my PS 1.7.6.1 shop, but on debug mode I have error Quote FatalErrorException Compile Error: Symfony\Component\Debug\DebugClassLoader::loadClass(): Failed opening required '/vendor/composer/../../src/Core/Domain/Theme/ValueObject/ThemeName.php' (include_path='/vendor/pear/pear_exception:/vendor/pear/console_getopt:/vendor/pear/pear-core-minimal/src:/vendor/pear/archive_tar:.:/:/usr/local/php72/lib/pear') in DebugClassLoader.php line 156 All i can see is that some file is missing, I've copied vendor directory from fresh PS install and nothing changed... When I install theme on fresh install on localhost it works. Any1 can show me the way I should check for solution? Link to comment Share on other sites More sharing options...
lototo Posted November 19, 2019 Share Posted November 19, 2019 It can be read permission problem. Files should have 644 folders 755 Link to comment Share on other sites More sharing options...
joomleader Posted November 20, 2019 Share Posted November 20, 2019 Hi friend 1. maybe it is PHP version problem, what is your PHP version on server 2. you only have problem when change template or have same problem with default theme of Prestashop ? Link to comment Share on other sites More sharing options...
thehurricane Posted November 20, 2019 Author Share Posted November 20, 2019 2 hours ago, joomleader said: Hi friend 1. maybe it is PHP version problem, what is your PHP version on server 2. you only have problem when change template or have same problem with default theme of Prestashop ? Thanks for replies. 1. PHP 7.2, but I've tried on other version and the same error... 2. Default theme works fine, it's just theme that I've bought. But I don't think it's problem with theme, as I said it works fine on localhost... 17 hours ago, lototo said: It can be read permission problem. Files should have 644 folders 755 I am trying this right now, and nothing changed Link to comment Share on other sites More sharing options...
tuk66 Posted November 20, 2019 Share Posted November 20, 2019 Failed opening required '/vendor/composer/../../src/Core/Domain/Theme/ValueObject/ThemeName.php Check if you really have the /src/Core/Domain/Theme/ValueObject/ThemeName.php file. 1 Link to comment Share on other sites More sharing options...
thehurricane Posted November 20, 2019 Author Share Posted November 20, 2019 14 minutes ago, tuk66 said: Failed opening required '/vendor/composer/../../src/Core/Domain/Theme/ValueObject/ThemeName.php Check if you really have the /src/Core/Domain/Theme/ValueObject/ThemeName.php file. Thank You! As You've said, I was missing this file. Those /../../ confused me, and I wasn't searching right file... Now I have problem (attachement) - but it's propably module related error and I've should ask developer for help? Link to comment Share on other sites More sharing options...
tuk66 Posted November 20, 2019 Share Posted November 20, 2019 No, this error message is useless. It is only PHP Warning and has nothing to do with the real problem. Unfortunately, it is very difficult to debug fatal errors in 1.7, because such worthless notices and warning usually destroy everything. Link to comment Share on other sites More sharing options...
thehurricane Posted November 20, 2019 Author Share Posted November 20, 2019 14 minutes ago, tuk66 said: No, this error message is useless. It is only PHP Warning and has nothing to do with the real problem. Unfortunately, it is very difficult to debug fatal errors in 1.7, because such worthless notices and warning usually destroy everything. ok thank You for info, but now when I try to use new theme (with debug mode off) on BO it saves and tells that ok. But on front page I have 500 error (not server one, but presta css styled 500 error). And in logs I have "Data from PrestaShop Addons is invalid, and cannot fallback on cache.". I am really confused right now... Link to comment Share on other sites More sharing options...
joomleader Posted November 21, 2019 Share Posted November 21, 2019 About foreach error, that mean 1 module has no data for showing when call foreach, you can check again that module configuration in backend Then enable debug mode for checking why you have error 500 Link to comment Share on other sites More sharing options...
MichaelEZ Posted November 21, 2019 Share Posted November 21, 2019 (edited) well he posted upper screenshot what happens when he has debug mod on.. if i were u i woud disable all external modules, a if theme works turn on one by one and see where problem is Edited November 21, 2019 by MichaelEZ (see edit history) 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