Jump to content

Edit History

Warbird

Warbird

Thanks a lot for the pointer.
I managed to identify the following error which pops up each time I visit the modules page, modules alert and module upgrade page.

[28-Aug-2019 19:25:20] WARNING: [pool xxxx] child 11212 said into stderr: "NOTICE: PHP message: PHP Fatal error:  require_once(): Failed opening required '/home/xxxx/public_html/ps/modules/ps_newproducts/ps_newproducts.php' (include_path='/home/xxxx/public_html/vendor/pear/pear_exception:/home/xxxx/public_html/vendor/pear/console_getopt:/home/xxxx/public_html/vendor/pear/pear-core-minimal/src:/home/xxxx/public_html/vendor/pear/archive_tar:.:/opt/alt/php-fpm72/usr/lib/php') in /home/xxxx/public_html/src/Adapter/Module/Module.php on line 360"

It clearly shows that the page still tries to find content in the old, no longer existing, PS subfolder.

I tested a bit further and tried to disable some modules which failed.
Checking the log file shows that also these modules are still expected in the old directory. Example: the category tree:
 

require_once(): Failed opening required '/home/xxxx/public_html/ps/modules/ps_categorytree/ps_categorytree.php

The question is how to clear this error? I have cleared the cache in PS backend but no luck so far.

Any ideas?

Thanks !

Warbird

Warbird

Thanks a lot for the pointer.
I managed to identify the following error which pops up each time I visit the modules page, modules alert and module upgrade page.

[28-Aug-2019 19:25:20] WARNING: [pool xxxx] child 11212 said into stderr: "NOTICE: PHP message: PHP Fatal error:  require_once(): Failed opening required '/home/xxxx/public_html/ps/modules/ps_newproducts/ps_newproducts.php' (include_path='/home/xxxx/public_html/vendor/pear/pear_exception:/home/xxxx/public_html/vendor/pear/console_getopt:/home/xxxx/public_html/vendor/pear/pear-core-minimal/src:/home/xxxx/public_html/vendor/pear/archive_tar:.:/opt/alt/php-fpm72/usr/lib/php') in /home/xxxx/public_html/src/Adapter/Module/Module.php on line 360"

It clearly shows that the page still tries to find content in the old, no longer existing, PS subfolder.
The question is how to clear this error? I have cleared the cache in PS backend but no luck so far.

Any ideas?

Thanks !

×
×
  • Create New...