0

I pulled whole site from a git repo. Now I am getting this message when I try to access product in admin: 

Fatal error: Class 'Mage_Uploader_Block_Multiple' not found in /Applications/XAMPP/xamppfiles/htdocs/libraccio/app/code/core/Mage/Adminhtml/Block/Media/Uploader.php on line 39

Everything else in admin seems to work fine. Displays fine, menus appear fine and other functionalities. What is causing this?

Edited: I copied over whole directory app/code/core/Mage/Uploader from Magento 1.9.3 per Rafael's advice and now I get this message when I try to get to admin product page: 

Fatal error: Uncaught Error: Call to a member function getConfig() on boolean in /Applications/XAMPP/xamppfiles/htdocs/libraccio/app/code/core/Mage/Adminhtml/Block/Catalog/Product/Helper/Form/Gallery/Content.php:50

Again, what can cause this?

Improve this question
1

1 Answer 1

Reset to default
1

Every Mage_Uploader classes have been introduced with SUPEE-8788 patch or with 1.9.3.X versions.

As you said you pulled the whole site from a GIT repo, my guess is that the app/code/core/Mage/Uploader directory has not been committed to that repo when the website has been patched / upgraded.

A hacky fix would be to download the 1.9.3 Magento files and copy the app/code/core/Mage/Uploader directory from the fresh files to your repo

Improve this answer
5
  • 1
    @VladimirDespotovic on the Magento website
    – Raphael at Digital Pianism
    Commented Nov 15, 2016 at 18:09
  • I tried to apply the patch that you mentioned, with the same result. I also tried to copy over the files from v 1.9.3 with same result. Noting helped.
    – Vladimir Despotovic
    Commented Nov 16, 2016 at 10:46
  • @VladimirDespotovic well that second error with getConfig() means the app/code/core/Mage/Adminhtml/Block/Catalog/Product/Helper/Form/Gallery/Content.php has not been updated either. I think your upgrade failed and you should try a manual upgrade with all the 1.9.3 files
    – Raphael at Digital Pianism
    Commented Nov 16, 2016 at 10:48
  • This is a no. I can't change every Magento file just to fix a bug.
    – Vladimir Despotovic
    Commented Nov 16, 2016 at 10:58
  • Running the patch mentioned in this answer and together with this bug fix solved the problem: magento.stackexchange.com/questions/146219/…
    – Vladimir Despotovic
    Commented Nov 21, 2016 at 14:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.