Magento Forum

   
Package community/Mage_Core_Modules 1.6.1.0 conflicts with: community/Find_Feed 1.0.8
 
Roeltje
Jr. Member
 
Total Posts:  19
Joined:  2009-01-19
Waalwijk, Netherlands
 

Already figured out that FindFeed has to be removed before upgrading… question is… how?

 
Magento Community Magento Community
Magento Community
Magento Community
 
fibermage
Jr. Member
 
Total Posts:  5
Joined:  2011-07-18
 

Does anyone have any ideas on how to remove Find_Feed.  When I try to remove it, it complains about conflicts.  I tired deleting every file with Find Feed and modifying any pointers in xml files to Find Feed, but it still thinks it’s there.  So far, it seems impossible to remove Find Feed and get a successful upgrade to 1.6.2.0. 

Error in connection manager when selecting Find Feed and selecting uninstall and commit.

CONNECT ERROR: community/Mage_Core_Modules 1.6.1.0 is required by: community/Interface_Install_Default 1.6.1.0, community/Mage_Centinel 1.6.1.0, community/Magento_Mobile 1.6.0.0.22.1, community/Phoenix_Moneybookers 1.3.0.1, community/Mage_All_Latest 1.6.2.0, community/Interface_Frontend_Default 1.6.2.0, community/Interface_Frontend_Base_Default 1.6.2.0, community/Mage_Compiler 1.6.2.0, community/Mage_Core_Adminhtml 1.6.2.0

 
Magento Community Magento Community
Magento Community
Magento Community
 
hazel_cl
Jr. Member
 
Total Posts:  13
Joined:  2010-10-16
 

It seems like upgrading to 1.6.2.0 is not going to be possible from 1.6.1.0 since find feed is a listed as a required component for Magento up to 1.6.1. As a previous poster pointed out Find Feeds is obsolete as of 1.6.2, which means that updating to Magento 1.6.1 from the Magento connect or Mage via SSH is not possible. Since the default install of 1.6.1.0 has find feed built in as a required core component in order for it to run properly.

This is the only solution I see for someone to get around this issue, if you want to install Magento 1.6.2 onto your server you will have to do a separate install of 1.6.2 along side 1.6.1 and migrate all of your templates and plugins to the new install. I was able to download the complete tar ball of 1.6.2 via ssh onto my locale host and walked through the install wizard just fine. Magento 1.6.2 will install just fine.

This is the easiest way to download Magento onto your server.
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/installing_magento_via_shell_ssh

 
Magento Community Magento Community
Magento Community
Magento Community
 
Furore
Jr. Member
 
Total Posts:  12
Joined:  2011-10-11
The Netherlands
 

I tried to upgrade to 1.6.2 and had the “ Package community/Mage_Core_Modules 1.6.1.0 conflicts with: community/Find_Feed 1.0.8 “ error, and now i cant reach my admin and my whole site is offline and it says: Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Please help, what can i do to fix this?

 
Magento Community Magento Community
Magento Community
Magento Community
 
Furore
Jr. Member
 
Total Posts:  12
Joined:  2011-10-11
The Netherlands
 

Pfffew, It okay now, I guess the maintenance mode while installing/upgrading was checked. I unchecked it and made a new (failed) upgrade and now i can login again.

But I still cant upgrade cause of the error everybody is having in this topic…

 
Magento Community Magento Community
Magento Community
Magento Community
 
virtualbrands
Jr. Member
 
Total Posts:  1
Joined:  2009-02-15
 

It worked great!

rm -rf /var/cache session
./mage mage-setup .
./mage config-set preferred_state stable
./mage list-installed
./mage list-upgrades
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force
./shell php indexer.php reindexall

Emre Kavlakoglu | Director of Creative Services | virtualbrands interactive

 
Magento Community Magento Community
Magento Community
Magento Community
 
Roeltje
Jr. Member
 
Total Posts:  19
Joined:  2009-01-19
Waalwijk, Netherlands
 
hazel_cl - 23 January 2012 11:49 PM

It seems like upgrading to 1.6.2.0 is not going to be possible from 1.6.1.0 since find feed is a listed as a required component for Magento up to 1.6.1. As a previous poster pointed out Find Feeds is obsolete as of 1.6.2, which means that updating to Magento 1.6.1 from the Magento connect or Mage via SSH is not possible. Since the default install of 1.6.1.0 has find feed built in as a required core component in order for it to run properly.

Upgrading from 1.6.1.0 is possible, since find feed was already taken out there… any older version gives the error… :/

 
Magento Community Magento Community
Magento Community
Magento Community
 
winstein3000
Jr. Member
 
Total Posts:  8
Joined:  2010-11-01
 

This seemed to work for me:

1, Just in case something bad happens, I backed up everything:  made a copy of all files and backup the database.

2, Download the full copy of Magento 1.6.2.0, unzip it, copy over the 1.6.1.0 directory. (Just for fun, I used Filezilla to copy over the files and override the existing files.)

That’s it.

 
Magento Community Magento Community
Magento Community
Magento Community
 
magentoinchina
Member
 
Avatar
Total Posts:  32
Joined:  2009-07-12
 

if anybody still have this problem.please contact me
my skype id is himagentochina.
i have fixed it.

 
Magento Community Magento Community
Magento Community
Magento Community
 
Mom2B
Jr. Member
 
Total Posts:  24
Joined:  2009-03-09
 
tim-openstream - 12 January 2012 03:25 AM

Just do

./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force

Tried this but ssh returns “Permission Denied”, chmod is not accepted either. I get stuck on this:

CONNECT ERROR: Package community/Mage_Core_Modules 1.6.2.0 conflicts with: community/Find_Feed 1.1.0
Package community/Lib_Varien 1.6.1.0 conflicts with: community/Mage_Core_Modules 1.5.1.0
Package community/Lib_Js_Mage 1.6.1.0 conflicts with: community/Mage_Core_Modules 1.5.1.0
Package community/Mage_Locale_en_US 1.6.2.0 conflicts with: community/Mage_Core_Modules 1.5.1.0
Package community/Lib_Mage 1.6.1.0 conflicts with: community/Mage_Core_Modules 1.5.1.0
Package community/Lib_Js_Prototype 1.7.0.0.2 conflicts with: community/Mage_Core_Modules 1.5.1.0

So Mage_Core_Modules 1.6.2.0 is too new and that is why community/Find_Feed 1.1.0 wont’t allow updating, but the installed version Mage_Core_Modules 1.5.1.0 needs to be updated to solve the other conflicts…

?????????????? HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 
Magento Community Magento Community
Magento Community
Magento Community
 
Roeltje
Jr. Member
 
Total Posts:  19
Joined:  2009-01-19
Waalwijk, Netherlands
 
magentoinchina - 31 January 2012 10:44 PM

if anybody still have this problem.please contact me
my skype id is himagentochina.
i have fixed it.

Would be nice if you could write it down here…

 
Magento Community Magento Community
Magento Community
Magento Community
 
bjarni
Jr. Member
 
Total Posts:  2
Joined:  2010-06-04
 

Solution has been proposed
Does anyone have a test server or more PHP knowledge that I do to test this out if it is ok?
downloader\lib\Mage\Connect\Command
open install.php
comment out lines, including 510 to 523
save and then go to Connect Maneger and uninstall find_feed module
then upgrade should work

 
Magento Community Magento Community
Magento Community
Magento Community
 
Zodiac Media
Jr. Member
 
Avatar
Total Posts:  5
Joined:  2010-11-03
London
 

Just tried bjarni’s proposed solution and Magento Connect uninstalls the dependent packages as well.  Output trace as follows:

---

Starting to uninstall community/Find_Feed
Package community/Find_Feed uninstalled
Starting to uninstall community/Mage_Core_Modules
Package community/Mage_Core_Modules uninstalled
Starting to uninstall community/Lib_Varien
Package community/Lib_Varien uninstalled
Starting to uninstall community/Lib_ZF
Package community/Lib_ZF uninstalled
Starting to uninstall community/Lib_ZF_Locale
Package community/Lib_ZF_Locale uninstalled
Starting to uninstall community/Lib_Google_Checkout
Package community/Lib_Google_Checkout uninstalled
Starting to uninstall community/Lib_Js_Calendar
Package community/Lib_Js_Calendar uninstalled
Starting to uninstall community/Lib_Js_Mage
Package community/Lib_Js_Mage uninstalled
Starting to uninstall community/Lib_Js_Prototype
Package community/Lib_Js_Prototype uninstalled
Starting to uninstall community/Lib_Phpseclib
Package community/Lib_Phpseclib uninstalled
Starting to uninstall community/Mage_Locale_en_US
Package community/Mage_Locale_en_US uninstalled
Starting to uninstall community/Lib_Mage
Package community/Lib_Mage uninstalled
Package deleted:
community Find_Feed
community Mage_Core_Modules
community Lib_Varien
community Lib_ZF
community Lib_ZF_Locale
community Lib_Google_Checkout
community Lib_Js_Calendar
community Lib_Js_Mage
community Lib_Js_Prototype
community Lib_Phpseclib
community Mage_Locale_en_US
community Lib_Mage

Cleaning cache

Cache cleaned successfully

---

Not good! Looks like you either do a fresh reinstall of 1.6.2 and migrate data across or sit tight until 1.6.3 comes out which fixes this issue.

 
Magento Community Magento Community
Magento Community
Magento Community
 
magentoinchina
Member
 
Avatar
Total Posts:  32
Joined:  2009-07-12
 
Billy Davies - 02 February 2012 11:14 AM

Just tried bjarni’s proposed solution and Magento Connect uninstalls the dependent packages as well.  Output trace as follows:

---

Starting to uninstall community/Find_Feed
Package community/Find_Feed uninstalled
Starting to uninstall community/Mage_Core_Modules
Package community/Mage_Core_Modules uninstalled
Starting to uninstall community/Lib_Varien
Package community/Lib_Varien uninstalled
Starting to uninstall community/Lib_ZF
Package community/Lib_ZF uninstalled
Starting to uninstall community/Lib_ZF_Locale
Package community/Lib_ZF_Locale uninstalled
Starting to uninstall community/Lib_Google_Checkout
Package community/Lib_Google_Checkout uninstalled
Starting to uninstall community/Lib_Js_Calendar
Package community/Lib_Js_Calendar uninstalled
Starting to uninstall community/Lib_Js_Mage
Package community/Lib_Js_Mage uninstalled
Starting to uninstall community/Lib_Js_Prototype
Package community/Lib_Js_Prototype uninstalled
Starting to uninstall community/Lib_Phpseclib
Package community/Lib_Phpseclib uninstalled
Starting to uninstall community/Mage_Locale_en_US
Package community/Mage_Locale_en_US uninstalled
Starting to uninstall community/Lib_Mage
Package community/Lib_Mage uninstalled
Package deleted:
community Find_Feed
community Mage_Core_Modules
community Lib_Varien
community Lib_ZF
community Lib_ZF_Locale
community Lib_Google_Checkout
community Lib_Js_Calendar
community Lib_Js_Mage
community Lib_Js_Prototype
community Lib_Phpseclib
community Mage_Locale_en_US
community Lib_Mage

Cleaning cache

Cache cleaned successfully

---

Not good! Looks like you either do a fresh reinstall of 1.6.2 and migrate data across or sit tight until 1.6.3 comes out which fixes this issue.

not good? do you reinstall your website according the wizard?if you did not .dont said it is not good

 
Magento Community Magento Community
Magento Community
Magento Community
 
bjarni
Jr. Member
 
Total Posts:  2
Joined:  2010-06-04
 

The solution I proposed comes from magentoinchina.
I skyped him yesterday.
I also talked to him this morning and he claims that if you go through the installation after removing find_feed everything comes back up intact as 1.6.2.
Maybe you did not go far enough with your test and complete the process with the install.
It would be good if someone is in a position to test this completely.
Regards
Bjarni

 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
    Back to top