We used to get tickets complaining that the customers are not able to install Magento Blue theme via Magento Connect. When you try to install you may get the below error.
ERROR: Via magento connect magento-core/Interface_Frontend_Default_Default_Blue requires package "magento-core/Interface_Frontend_Default" (version >= 1.3.1, version <= 1.4.0, excluded versions: 1.4.0), installed version is 1.4.0.0 Install Errors No valid packages found PEAR ERROR: install failed magento-core/Interface_Frontend_Default magento-core/Mage_Core_Modules
To fix this, login to your account via SSH and navigate to the Magento installation folder and execute the below command.
Install Interface_Frontend_Default correct version
./pear install magento-core/Interface_Frontend_Default
And then the Blue theme
./pear install magento-core/Interface_Frontend_Default_Default_Blue
You can get help for pear command by executing
pear help
And to list Channels
pear list-channels Registered ChannelContinue Reading
Sometimes Magento admins face the issue of some values missing from the frontend even though the configuration would have shown to be saved from Backend. This could be due the limit in the number of values set by suhosin.
The common override for this issue is to have the following values set in .htaccess
php_value suhosin.mail.protect 0
php_value suhosin.memory_limit 128M
php_value suhosin.post.max_vars 5000
php_value suhosin.post.max_value_length 500000
php_value suhosin.request.max_vars 5000
php_value suhosin.request.max_value_length 500000
php_flag suhosin.session.cryptua off
For php.ini use the variables without php_value or php_flag
Continue ReadingYou get this error while entering the magento admin home page after login. The home page has a number of warnings and talks about locales. A sample error listing shown is:
Warning: simplexml_load_file() [function.simplexml-load-file]: (null)(null)/home/runinsty/public_html/paths/lib/Zend/Locale/Data/ko.xml:2780: parser error : out of memory error in /home/runinsty/public_html/paths/lib/Zend/Locale/Data.php on line 146
Trace:#0 /home/runinsty/public_html/paths/lib/Zend/Locale/Data.php(146): mageCoreErrorHandler(2, ‘simplexml_load_…’, ‘/home/runinsty/…’, 146, Array)
#1 /home/runinsty/public_html/paths/lib/Zend/Locale/Data.php(217): Zend_Locale_Data::_findRoute(’/home/runinsty/…’)
#2 /home/runinsty/public_html/paths/lib/Zend/Locale/Data.php(231): Zend_Locale_Data::_getFile(’ko’, ‘/ldml/localeDis…’, ‘type’, false, Array)
#3 /home/runinsty/public_html/paths/lib/Zend/Locale/Data.php(787): Zend_Locale_Data::_getFile(’ko’, ‘/ldml/localeDis…’, ‘type’, false, Array)
#4 /home/runinsty/public_html/paths/lib/Zend/Locale.php(594): Zend_Locale_Data::getContent(’ko_KR’, ‘/ldml/localeDis…’, ‘type’)
#5 /home/runinsty/public_html/paths/lib/Zend/Locale.php(611): Zend_Locale::getTranslation(’ko_KR’, ‘language’, ‘ko’)
#6 /home/runinsty/public_html/paths/app/code/core/Mage/Core/Model/Locale.php(246): Zend_Locale::getLanguageTranslation(’ko’, ‘language’, ‘ko_KR’)
#7 /home/runinsty/public_html/paths/app/code/core/Mage/Core/Model/Locale.php(219): Mage_Core_Model_Locale->_getOptionLocales(’ko’, ‘ko_KR’)
#8 /home/runinsty/public_html/paths/app/code/core/Mage/Adminhtml/Block/Page/Footer.php(67): Mage_Core_Model_Locale->getTranslatedOptionLocales(true)
#9 /home/runinsty/public_html/paths/app/design/adminhtml/default/default/template/page/footer.phtml(29): Mage_Adminhtml_Block_Page_Footer->getLanguageSelect()
#10 /home/runinsty/public_html/paths/app/code/core/Mage/Core/Block/Template.php(144): include(’/home/runinsty/…’)
To solve this there are two things to be done, firstly ensure that the memory_limit value for php is more than 64Mb. Next notice the first line in the error sample:
home/runinsty/public_html/paths/lib/Zend/Locale/Data/ko.xml
What we are interested here is the locale ko
Now go to the file /home/runinsty/www/app/etc/config.xml search for the tag <codes> . A listing similar to the below will be seen:
<locale>
<allow>
<codes>
<af_ZA/><!– Afrikaans (South Africa) –>
<ar_EG/><!– Arabic (Egypt) –>
<ar_KW/><!– Arabic (Kuwait) –>
<ar_MA/><!– Arabic (Morocco) –>
<ar_SA/><!– Arabic (Saudi Arabia) –>
<az_AZ/><!– Azerbaijani (Azerbaijan) –>
<bg_BG/><!– Bulgarian (Bulgaria) –>
<bn_BD/><!– Bengali (Bangladesh) –>
<bs_BA/><!– Bosnian (Bosnia) –>
<ca_ES/><!– Catalan (Catalonia) –>
<cs_CZ/><!– Czech (Czech Republic) –>
<cy_GB/><!– Welsh (United Kingdom) –>
<da_DK/><!– Danish (Denmark) –>
<km_KH/><!– Khmer (Cambodia) –>
<ko_KR/><!– Korean (South Korea) –>
<lo_LA/><!– Lao (Laos) –>
<lt_LT/><!– Lithuanian (Lithuania) –>
<lv_LV/><!– Latvian (Latvia) –>
<mk_MK/><!– Macedonian (Macedonia) –>
<mn_MN/><!– Mongolian (Mongolia) –>
<ms_MY/><!– Malaysian (Malaysia) –>
<nl_NL/><!– Dutch (Netherlands) –>
<nb_NO/><!– Norwegian Bokmål (Norway) –>
Now delete all the xml tag lines beginning with <ko_ .
Next clear your browser cache and revisit your page to see the error fly away.
Continue Reading