Mukesh Chapagain's Blog » error

Magento: Helper Data not found error

Mukesh — Mon, 11 Apr 2011 03:24:44 +0000

I created a module, let’s say, ‘MyModule’. When I go to the Admin -> System -> Configuration section of this module, I get this weird error.

Fatal error: Class ‘Mage_MyModule_Helper_Data’ not found

- My Module is enabled.
- I have helper class in ‘Helper’ folder of my module.
- I have deleted/refreshed all cache and session.

According to my findings, the problem should be in XML file. Either the XML file inside app/etc/modules or the XML file inside MyNamespace/MyModule/etc.

1) XML is strictly case sensitive

I opened app/etc/modules/MyNamespace_MyModule.xml to check the case sensitive issue as the XML files are strictly case sensitive.

Everything was okay with it. Here is the code:-



  
    
      local
      true

I was checking the codePool node. You might get this error if you write codepool (all small letters) instead of codePool (P capital). However, in my case, it was okay.

2) XML doesn’t ignore whitespace (even if it is commented)

This was the main cause of the error in my case. You should not keep space in between XML content. I had kept space in MyNamespace/MyModule/etc/config.xml

The tricky part is that the space was inside commented XML code. Didn’t know that XML checks for whitespace inside commented code as well.

I have commented out some code in config.xml as below:-

The space just after the comment start (before default node) and the space just before the comment end (after closing default node) was causing the error. I deleted the whole commented code and my problem was solved. :)

Hope this helps. Thanks.

Copyright © 2011
This feed is for personal, non-commercial use only.
The use of this feed on other websites breaches copyright. If this content is not in your news reader, it makes the page you are viewing an infringement of the copyright. (Digital Fingerprint:
)

Related posts:

Magento: Fatal error: Call to a member function setSaveParametersInSession() on a non-object

Mukesh — Mon, 28 Mar 2011 00:27:44 +0000

Scenario

I was creating a module. I already had one Grid displayed in admin. The Grid was being displayed by a Block class, for example: MyNamespace_MyModule_Block_Adminhtml_MyModule
Now, I had to display another Grid using a new Block class. Let’s say, I created a new Block class: MyNamespace_MyModule_Block_Adminhtml_MyNewGrid

I just copied code from MyNamespace_MyModule_Block_Adminhtml_MyModule and copied it to MyNamespace_MyModule_Block_Adminhtml_MyNewGrid class.

MyNamespace_MyModule_Block_Adminhtml_MyModule

class MyNamespace_MyModule_Block_Adminhtml_MyModule extends Mage_Adminhtml_Block_Widget_Grid_Container
{
  public function __construct()
  {
    $this->_controller = 'adminhtml_mymodule';
    $this->_blockGroup = 'mymodule';
    $this->_headerText = Mage::helper('mymodule')->__('Module Data');
    parent::__construct();
  }
}

MyNamespace_MyModule_Block_Adminhtml_MyNewGrid

class MyNamespace_MyModule_Block_Adminhtml_MyNewGrid extends Mage_Adminhtml_Block_Widget_Grid_Container
{
  public function __construct()
  {
    $this->_controller = 'adminhtml_mymodule';
    $this->_blockGroup = 'mynewgrid';
    $this->_headerText = Mage::helper('mymodule')->__('Module Data New');
    parent::__construct();
  }
}

Cause

The main mistake over here was the confusing naming for controller and blockGroup.

$this->_controller = This is not the controller class name. It is actually your Block class name.
$this->_blockGroup = This is your module’s name.

Solution

Hence, I updated my new grid class in the following way and the problem was solved. See the change in controller and blockGroup from the previous code.

MyNamespace_MyModule_Block_Adminhtml_MyNewGrid

class MyNamespace_MyModule_Block_Adminhtml_MyNewGrid extends Mage_Adminhtml_Block_Widget_Grid_Container
{
  public function __construct()
  {
    $this->_controller = 'adminhtml_mynewgrid';
    $this->_blockGroup = 'mymodule';
    $this->_headerText = Mage::helper('mymodule')->__('Module Data New');
    parent::__construct();
  }
}

Hope this helps. Thanks.

Related posts:

Magento 1.4: No products displayed in category listing

Mukesh — Thu, 22 Jul 2010 13:24:37 +0000

Scenario:

I have a fresh installation of Magento 1.4. I already have installed the sample data for Magento.

Now, when I go to the category listing page, no products are displayed. It says “There are no products matching the selection.“.

By category listing page, I mean the product listing page displayed when any category is clicked. Like, product listing for Furniture category, product listing for Living Room category, etc.

Solution:

- Go to System -> Index Management
- Select All Checkbox
- In Actions, select ‘Reindex Data‘
- Click Submit

Now, go to the category listing page. You will be able to see the products.

Hope this helps. Thanks.

Related posts:

Magento Error – Notice: Undefined index: 0 app/code/core/Mage/Core/Model/Mysql4/Config.php on line 92

Mukesh — Mon, 12 Jul 2010 11:15:19 +0000

I got this error message when migrating my Magento files and database from one server to another.

Notice: Undefined index: 0 in app/code/core/Mage/Core/Model/Mysql4/Config.php on line 92

Solution:

- Open PhpMyAdmin
- Go to your database
- Click SQL
- Run the following SQL Query:

SET FOREIGN_KEY_CHECKS=0;
UPDATE `core_store` SET store_id = 0 WHERE code='admin';
UPDATE `core_store_group` SET group_id = 0 WHERE name='Default';
UPDATE `core_website` SET website_id = 0 WHERE code='admin';
UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
SET FOREIGN_KEY_CHECKS=1;

That’s all. Your error is solved now.

Hope this helps. Thanks.

Related posts:

W3C Validation: IFrame Error with XHTML 1.0 Strict Doctype

Mukesh — Tue, 06 Jul 2010 11:58:20 +0000

IFrames are not supported with XHTML 1.0 Strict Doctype.

When you use IFrame and your doctype is XHTML 1.0 Strict, then you cannot pass the W3C Markup Validation test. You always get errors.

The errors are like:-

there is no attribute “src”
there is no attribute “scrolling”
there is no attribute “frameborder”
there is no attribute “height”
there is no attribute “width”
there is no attribute “allowtransparency”
there is no attribute “title”
element “iframe” undefined

Solution

Use object tag instead of iframe.

Example

Here is an iframe code for Facebook Like Box:-

Using the above IFrame code in your website gives errors when you validate with W3C.

So, the solution is to use Object tag. You will not get the validation errors by using Object.

It’s the same case with including Google Maps in websites.

Hope this helps. Thanks.

Related posts:

Magento: Exception printing is disabled by default for security reasons

Mukesh — Tue, 29 Jun 2010 07:57:37 +0000

Problem:

I am using Magento 1.4. Homepage loads fine. When I go to category (product listing) page, it works fine. But when I go to any product detail page, I get the following error:-

There has been an error processing your request

Exception printing is disabled by default for security reasons.

I don’t get the detailed information about the error as I used to get in previous versions of Magento.

Solution:

In your magento root, there is a folder called errors.

Go inside the errors folder.

There is a file named local.xml.sample.

Rename it to local.xml

Hence, the problem is solved. Now, I am able to see detailed error information.

Another Problem:

Now, when I try to open any product detail page, I get the following error.

Warning: Varien_Autoload::include(Mage\Catalog\Model\Resource\Eav\Mysql4\Product\Attribute\Backend\Tierprice.php) [varien-autoload.include]: failed to open stream: No such file or directory

If I try to add product to cart from product listing page, the product is not added to cart. And, I get the following error message:-

Cannot add item to shopping cart

Solution:

Tierprice.php is not present in app\code\core\Mage\Catalog\Model\Resource\Eav\Mysql4\Product\Attribute\Backend.

There is a file named Tierprice.php0000664.

Rename it to Tierprice.php. Hence, the problem is solved. Now, I am able to open product detail page. And, I am also able to add product to shopping cart.

Hope this helps. Thanks.

Related posts:

Magento: Access denied in admin of custom module

Mukesh — Tue, 16 Feb 2010 09:00:44 +0000

I was building a custom module in Magento. I had created a system.xml file for storing configuration data from admin. From the below system.xml file, you can see that I have created a section named ‘My Module Name‘ which can be accessed from Admin –> System –> Configuration.

In the file below, I have just displayed the section and groups name. I have omitted others fields with dots, as they are not necessary here.



   
		
			My Module Name
			...
			..
			.
			
				
					My Group Name
					...
					..
					.
					
						...
						..
						.
					
				
			
			
				
					Second Group Name
					...
					..
					.
					
						...
						..
						.

Now, when I try to access the ‘My Module Name‘ tab present in Admin –> System –> Configuration, I get the ‘Access Denied‘ Error.

I searched the internet about this problem. In the magentocommerce forum, people suggested to log out and relogin. But it didn’t slove my problem.

Inchoo suggested to edit administrator roles. But, it didn’t solve either.

Then I tried Activecodeonline’s solution. It suggested me to set some nodes in config.xml file of my module. I also think that it’s XML related problem. But this solution didn’t solve my problem. The ‘Access Denied‘ error still exists.

Finally, Activecodeonline was very useful to me ;). Actually, I had 2 groups in my system.xml file (see above xml). Hence, I need to add both group names as children in config.xml file of my module.

Regarding my system.xml file, the following XML is to be added in the config.xml file.


	
		
			
				
					My Group Name
				
				
					My Second Group Name

Here is my config.xml file which solved my problem. Unnecessary parts for here are removed with dots (…) :)



    
       ...
	   ..
	   .
    
    
        ...
		..
		.
    
    
        ...
		..
		.
    
    
		
			...
			..
			.
		
		
			
				
					Allow Everything
				
				
					
						
							My Module
							10
						
						
							
								
									
										
											My Group Name
										
										
											My Second Group Name
										
									
								
							
						
					
				
			
		
		
			...
			..
			.
		
    
    
        ...
		..
		.

Hope this helps and thanks for reading.

Related posts:

Magento: Product Edit Warning: Invalid argument supplied for foreach()

Mukesh — Thu, 10 Dec 2009 07:52:13 +0000

Scenario:

While editing product programatically from frontend. I was trying to change the status of the product with the following code:

Mage::getModel(‘catalog/product’)->load($product->getId())->setStatus(2)->save();

Problem:

Product could not be edited programatically from frontend. The following error message is shown:

Warning: Invalid argument supplied for foreach() in /var/www/magento/app/code/core/Mage/Eav/Model/Entity/Abstract.php on line 937

Solution:

It seems that product updates are only made on the admin side and you have to change the store view while editing product from frontend.

Write the following before you edit product:


Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID);

Hence, my new code will be :


Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID);
Mage::getModel('catalog/product')->load($item->getProductId())->setStatus(2)->save();

Related posts:

Google says Sorry to me

Mukesh — Tue, 08 Dec 2009 02:15:44 +0000

I’m human, Google !

I was googling something and google suddenly said sorry to me. It says my computer is sending automated queries. I was just googling “magento programmer developer nepal” by changing the word position at each time. I just googled this way for at most 5 times.

Google help says the following thing about this issue:

The ‘We’re Sorry’ message appears when Google detects that a computer on your network is sending automated traffic to Google. Automated queries are against our Terms of Service.

Here is the image of the error/security message:

Google says Sorry

I must have been late to make a century but anyways I am happy to do so now. This is my 100th post :)

Blogging is so fun. I love it!

Thanks to everyone who reads me.

Related posts:

Configuration error on new Magento installation

Mukesh — Tue, 07 Jul 2009 12:17:28 +0000

Scenario:

I am installing a fresh magento 1.3.2.1 in my Windows XP computer. I have Xampp installed. While installing magento, I had a problem at the configuration step where I had to fill database host, username, password etc. When I click continue after filling the required fields, the installation process doesn’t move forward. I am redirected to the same page.

Solution:

I googled and was suggested to put 127.0.0.1 instead of localhost in the url; e.g. to put http://127.0.0.1/magento instead of http://localhost/magento . I did the same but then I got the following error displayed:

Database server does not support InnoDB storage engine
Database connection error

This error was solved. I opened my.cnf file present inside mysql/bin/ in notepad and uncommented (removed # sign) from the line skip_innodb.

Change:
#skip-innodb to skip-innodb

But still, my problem was not solved. I could not pass through the configuration page. Then I found a solution which finally helped me. I changed chmod of the following three folders to 777, i.e. making the folders writable. These folders are inside your magento folder. In windows, right click the folder, go to properties, uncheck ‘Read Only’ present under Attributes. The folders to change are as under:

app/etc
var
media

Finally, I am through and I completed Magento installation. Hurray :)

Related posts: