I am setting up a Magento(v. 1.6.1.0) site.
To access the API, I needed to create a rule (Admin > System > Web Services > Rules > Add new rule).
When I click the button, I got the following error.
Fatal error: Call to a member function toHtml() on a non-object in /home/dinamal7/public_html/app/code/core/Mage/Adminhtml/Block/Api/Editroles.php on line 52
I ran some research about the issue but couldn't find any solution. Can anybody help me?
Thanks.
Sam
#Sam, looks like there is some problem with the object calling that particular function. As you can see, it is indicating the core file, which is not supposed to have any errors. You can try and replace the "core" folder of your current installation with the one extracted fresh. This should do the trick.
Related
I am really new to PrestaShop and am facing trouble debugging an error in PrestaShop 1.6.1.3
It was working just fine, until I have changed some localization and delivery settings in admin panel.
Now, whenever I make an order, and try to proceed with bank wire payment, I receive the following error:
Fatal error: Call to undefined method Tools::getInvoiceProductName() in /home/makede/domains/manokede.lt/public_html/tools/smarty/sysplugins/smarty_internal_templatebase.php(157) : eval()'d code on line 36
Any help or guidance for how to solve it or at least debug deeper is much appreciated.
by default class Tools have no method called getInvoiceProductName in Presta, if you added this line (where method called), just comment/delete it
Can you please try clearing your cache and then check again?
There is an error suddenly started popping up. The error occurs on various part of website like cart area, product detail page etc..
I am running my site on local server.
the error is as follows:
Fatal error: Call to a member function getReadConnection() on boolean in app/code/core/Mage/Core/Model/Resource/Db/Collection/Abstract.php on line 134
I have googled the issue but that didn't helped either.
You have to define the class and the resource model. Please check this link. I hope solve your problem.
When I load my Magento admin I get the error.
Fatal error: Call to a member function isLoggedIn() on a non-object
in /home/xxx/public_html/app/code/community/TM/Core/Model/Observer.php
on line 12
I think it happened when I replaced some files somewhere in app/code/...
I’m really stuck on this and need desperate help.
Error is in your extension file TM/Core/Model/Observer.php
Disable extension and check after refresh cache
This was fixed by the Full Page Cache Extension people.
I don't know what they did but it was their extension which broke my magento however they fixed it for me right away
I was installing magento 1.9.1 on my server everything went fine but after installation when i click on Go to Backend and give my username and password to login to Admin Panel it gives the following error:
Fatal error: Class 'Mage_Sales_Model_Order' not found in
/home2/siatel/public_html/4ebay/app/code/core/Mage/Reports/Model/Resource/Order/Collection.php
on line 456
Though my frontend side of website is working perfectly ... Please help.
I can see my admin log-in page. Error comes only when I give username and pass and hit continue...
Without more information, it sounds like you're missing your
app/code/core/Mage/Sales/Model/Order.php
file. It seems like you're missing a lot of different files as well. I'd diff your installation vs. the contents of a standard tar archive.
Your error shows like this
Fatal error: Class 'Mage_Shipping_Helper_Data' not found in
/home2/siatel/public_html/4ebay/app/Mage.php on line 547
see the portion 'Mage_Shipping_Helper_Data' not found. It means Magento is looking for a helper class file and it couldnt find it. Magento will look for this file in app/code/core/Mage/Shipping/Helper/Data.php.
I will give you some hint on how this file path came from. First of all magento core files lies in the location app/code/core/. Then missing class name (in this case Mage_Shipping_Helper_Data) will converted as Mage/Shipping/Helper/Data.php. Then this will append to the core codePool directory path. That is app/code/core/Mage/Shipping/Helper/Data.php
For every file, magento assigns path as like this. Please note that, you need to attach .php part to the last keyword. Also you need to copy the exact same data of that file (take into consider the version). It means it need to have a 'Magento way' class name and so on
I'm using Symfony2 RC3 and I have a NewsBundle that has an Article entity.
I generated crud for it using the command: $ php app/console doctrine:generate:crud (with 'write' set to yes).
Now, every page on my site throws this error:
Fatal error: Label 'not_admin_article_create' already defined in /usr/local/zend/apache2/htdocs/AIEF/app/cache/prod/appprodUrlMatcher.php on line 260
If i get rid of
requirements: { _method: post }
for admin_article_create, admin_article_update and admin_article_delete in the generated routing yml file, everything works fine. Any idea why ?
I came across a similar issue recently, Google search wasn't much help but give me ideas of where to look, anyways enough blah blah.
The error I was getting was as follows:
enter code here`Fatal error: Label 'not _ offering management' already defined in /...
Whats I noticed was that there was a duplicate entry in routing_dev.yml and routing.yml, so basically the issue pops up when you happen to have multiple configurations. I think Symfony2 bundle generation adds mapping, but user probably accidental re-configures mapping else where.