Hi @warren_samu,
It seems you're using the Magento's compiler.
In my opinion you shouldn't use it.
The easier way to disable it is using Magento shell.
Go to the shell directory and then run:
php compiler.php state
Now you'll see the current status of or compiler. If is enabled and/or compiled, please, execute this commands:
php compiler.php disable php compiler.php clear
Now is disabled and you've cleared all the generated files.
Can you try it and check if the blog module is failing again?
Hi @Damian Culotta!
Thank you for you help.
I did go through shell and disable and clear the compiler.
I also discovered today that an old extension, MageMonkey was causing errors in the exception.log.
Unfortunately, after:
I'm still receiving the following error page when I try to edit a product:
Exception printing is disabled by default for security reasons.
Hello @warren_samu,
If you get still same error then please follow below steps
#define('COMPILER_INCLUDE_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'src'); #define('COMPILER_COLLECT_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'stat');
Hope it will fix your issue. Let us know if you have any trouble.
--
If issue is solved, Click "Kudos" & "Accept as Solution"
The two lines already had hashtags. In fact, this is all that's in the config.php:
<?php /** * Magento * * NOTICE OF LICENSE * * This source file is subject to the Open Software License (OSL 3.0) * that is bundled with this package in the file LICENSE.txt. * It is also available through the world-wide-web at this URL: * http://opensource.org/licenses/osl-3.0.php * If you did not receive a copy of the license and are unable to * obtain it through the world-wide-web, please send an email * to license@magentocommerce.com so we can send you a copy immediately. * * DISCLAIMER * * Do not edit or add to this file if you wish to upgrade Magento to newer * versions in the future. If you wish to customize Magento for your * needs please refer to http://www.magentocommerce.com for more information. * * @category Mage * @package Mage * @copyright Copyright (c) 2008 Irubin Consulting Inc. DBA Varien (http://www.varien.com) * @license http://opensource.org/licenses/osl-3.0.php Open Software License (OSL 3.0) */ ##define('COMPILER_INCLUDE_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'src'); #define('COMPILER_COLLECT_PATH', dirname(__FILE__).DIRECTORY_SEPARATOR.'stat');
For make sure, find hello word related of block on project and remove it.
Where do I find this?
Hi @warren_samu,
Maybe you have a module into app/code/community or, possibly, app/code/local called Something_Hello ? ("Something" won't be the vendor name but the module could be called Hello).
It seems there is a module or a reference to that module that is causing the error too.
I'm afraid not
Hi @warren_samu,
Sorry, the invalid block type probably came from the layout definition on your theme.
If you take a look into the layout xml files into your active theme directory maybe there is a node with a reference to the block hello/hello.
Something like:
<block type="hello/hello" name="hello" />
(I don't know if the name will be hello but the type probably will be like that)
Can you check it?
The two most recently modified files were local.xml and checkout.xml on 8/2/18. These did not contain a reference to either extension and they were modified before the Hello Bar extension was installed.
The rest of the files haven't been modified since 2017 or earlier.
Does anyone know a qualified and trusted Magento developer (freelance or agency) that could assist with this issue? I feel like given the currently level of troubleshooting, someone could go in a fix this in an hour or so.