-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working at all in Magento 1.9 #3
Comments
Working here on Magento 1.9.1, but not working on searches. Is there any backend at all for this? Ok, so my problem seems to be a conflict with the Smartwave_AJAXCatalog. Checking both modules I can confirm they rewrite the same files for Catalogs and Searches. On catalog there are no methods conflicting, but on search they both redefine prepareProductCollection($collection). The Smartwave one doesn't use the parent function at all. I also noticed that you guys return $this and they return $catalog. So far I tried extending one another, disabling them, integrating the code, all with no success. I think the Smartwave thing came with my theme, but I am not sure because I was not the one to install it. |
Unfortunately I am having the same issue as tavinus. I am also running Smartwave_AJAXCatalog. I have tried to delete the extension but breaks the site :( |
also using false in the RicardoMartins_OutofstockLast.xml is not working for me |
Update, managed to disable using false in RicardoMartins_OutofstockLast.xml |
Core magento developers have improved code in 1.9.3.
to
After this modification all should work fine. |
Hi @popovsergiy I made the change you suggested. But it's not working. Magento 1.9.3.1 Link: https://www.pood.com.br/feminino/roupas/tops.html Would you have another tip? Thank you! |
@willgoulding : any solution for this? I have the same issue: this extension is broken on product searches in Magento 1.9. I fixed the crash by modifying app/code/local/Mage/Catalog/Block/Product/List.php, changing the code of _getProductCollection() to:
Now the searches return, but the Out of Stock products are still mixed with the In Stock ones... Anyone knows why? |
This solved for me: fauzi-ar@41faf1b |
Hi, Thanks |
It is almost always because of a conflict between modules. In this case, there are two modules overriding the search. There are some modules that will check for conflicts (they will tell you what files override the same class for example). Otherwise you will have to do it manually or even using This article explains a bit more and also have some links for some extensions for checking conflicts. If you are afraid to install these checkers on your site, you could use them at a separate clone, find the conflicts and then apply the same fix do the main site (without ever installing the checkers at the main site). Your log may also point you to the files where the conflict occurs. Hope this helps... |
Hi
I just sow your email. Thank you so much for taking the time to write it J
I will try to use that information and solve this, hope it'll help
All best and Merry Christmas!
Lior
From: Gustavo Arnosti Neves [mailto:[email protected]]
Sent: Thursday, December 14, 2017 8:38 PM
To: r-martins/Magento-OutOfStockLast
Cc: bohomagic; Comment
Subject: Re: [r-martins/Magento-OutOfStockLast] Not working at all in Magento 1.9 (#3)
It is almost always because of a conflict between modules.
What happens is that you have two modules overriding the same method/function and then only one of them gets executed. So you will probably need to merge the methods somehow if you want to keep both extensions.
In this case, there are two modules overriding the search.
There are some modules that will check for conflicts (they will tell you what files override the same class for example). Otherwise you will have to do it manually or even using find or grep from cli.
This article <http://www.aschroder.com/2013/04/understanding-and-detecting-magento-extension-clashes-or-conflicts/> explains a bit more and also have some links for some extensions for checking conflicts. If you are afraid to install these checkers on your site, you could use them at a separate clone, find the conflicts and then apply the same fix do the main site (without ever installing the checkers at the main site).
Hope this helps...
Cheers!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#3 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AdWpyyTAgvN_4Kc_3I6O0eUsJaISI0wDks5tAWsbgaJpZM4EtWpj> . <https://github.com/notifications/beacon/AdWpyztVkrJdPFFRobcgtdqQ4D6dM1_kks5tAWsbgaJpZM4EtWpj.gif>
|
I see no change in my catalog if this extension is running.
The text was updated successfully, but these errors were encountered: