Magento error after Upgrade : Can't perform operation, incomplete metadata - php

I have updated version of Magento EE 12.2 to Magento 14.2.0.2 but i get error when update or create product and category. Error massage is "Can't perform operation, incomplete metadata!"
I have also tried 'Enterprise_Index_Model_Action_Exception' with message 'Can't perform operation, incomplete metadata!' but not work for me.
Here is screenshot of error.
2016-06-20T12:36:57+00:00 ERR (3):
exception 'Enterprise_Index_Model_Action_Exception' with message 'Can't perform operation, incomplete metadata!' in app\code\core\Enterprise\Index\Model\Action\Abstract.php:125
Stack trace:
#0 app\code\core\Enterprise\CatalogInventory\Model\Index\Action\Refresh\Row.php(69): Enterprise_Index_Model_Action_Abstract->_validate()
#1 app\code\core\Enterprise\Mview\Model\Client.php(123): Enterprise_CatalogInventory_Model_Index_Action_Refresh_Row->execute()
#2 app\code\core\Enterprise\CatalogInventory\Model\Index\Observer.php(53): Enterprise_Mview_Model_Client->execute('enterprise_cata...', Array)
#3 app\code\core\Mage\Core\Model\App.php(1358): Enterprise_CatalogInventory_Model_Index_Observer->processStockItemSaveEvent(Object(Varien_Event_Observer))
#4 app\code\core\Mage\Core\Model\App.php(1337): Mage_Core_Model_App->_callObserverMethod(Object(Enterprise_CatalogInventory_Model_Index_Observer), 'processStockIte...', Object(Varien_Event_Observer))
#5 app\Mage.php(448): Mage_Core_Model_App->dispatchEvent('cataloginventor...', Array)
#6 app\code\core\Mage\Core\Model\Abstract.php(344): Mage::dispatchEvent('cataloginventor...', Array)
#7 app\code\core\Mage\CatalogInventory\Model\Stock\Item.php(893): Mage_Core_Model_Abstract->afterCommitCallback()
#8 [internal function]: Mage_CatalogInventory_Model_Stock_Item->afterCommitCallback()
#9 app\code\core\Mage\Core\Model\Resource\Abstract.php(110): call_user_func(Array)
#10 app\code\core\Mage\Core\Model\Abstract.php(322): Mage_Core_Model_Resource_Abstract->commit()
#11 app\code\core\Mage\Adminhtml\controllers\Catalog\ProductController.php(728): Mage_Core_Model_Abstract->save()
#12 app\code\core\Mage\Core\Controller\Varien\Action.php(418): Mage_Adminhtml_Catalog_ProductController->saveAction()
#13 app\code\core\Mage\Core\Controller\Varien\Router\Standard.php(254): Mage_Core_Controller_Varien_Action->dispatch('save')
#14 app\code\core\Mage\Core\Controller\Varien\Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#15 app\code\core\Mage\Core\Model\App.php(365): Mage_Core_Controller_Varien_Front->dispatch()
#16 app\Mage.php(684): Mage_Core_Model_App->run(Array)
#17 index.php(83): Mage::run('', 'store')
#18 {main}

Try to use php 5.3 disabling warnings and notices. It avoids some code warnings deprecation in old version.
If you get some invalid function name in the middle, go upgrading to 5.4, 5.5, etc.
It usually works for me. ;)

Related

Plesk reports that updates were not installed for the following items

I received this message yesterday on email from Plesk and there are a lot of items listed.
It appears to be to do largely with Wordpress Toolkit on the server. Plesk is the interface I use on my Ionos Hosted Server.
Sites are working from the server ok but obviously updates will not happen whilst these errors are present.
Does anyone have a clue what could be causing this and how to fix it please.
Thanks
Website "eeeSafe Community Safety Sustainability and Skills" (https://eeesafe.com): PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php:418
Stack trace:
#0 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(418): date()
#1 [internal function]: Cron_Event_Command::format_event()
#2 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(460): array_map()
#3 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(366): Cron_Event_Command::get_cron_events()
#4 [internal function]: Cron_Event_Command->delete()
#5 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()
#6 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}()
#7 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func()
#8 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(419): WP_CLI\Dispatcher\Subcommand->invoke()
#9 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/class-wp-cli.php(1443): WP_CLI\Runner->run_command()
#10 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/plesk/wp-cli-toolkit-command/src/Wpt_Cron_Command.php(30): WP_CLI::run_command()
#11 [internal function]: Wpt_Cron_Command->reschedule()
#12 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()
#13 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}()
#14 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func()
#15 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(419): WP_CLI\Dispatcher\Subcommand->invoke()
#16 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(442): WP_CLI\Runner->run_command()
#17 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1276): WP_CLI\Runner->run_command_and_exit()
#18 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#19 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process()
#20 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#21 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')
#22 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')
#23 {main}
thrown in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php on line 418
Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php:418
Stack trace:
#0 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(418): date()
#1 [internal function]: Cron_Event_Command::format_event()
#2 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(460): array_map()
#3 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(366): Cron_Event_Command::get_cron_events()
#4 [internal function]: Cron_Event_Command->delete()
#5 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()
#6 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}()
#7 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func()
#8 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(419): WP_CLI\Dispatcher\Subcommand->invoke()
#9 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/class-wp-cli.php(1443): WP_CLI\Runner->run_command()
#10 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/plesk/wp-cli-toolkit-command/src/Wpt_Cron_Command.php(30): WP_CLI::run_command()
#11 [internal function]: Wpt_Cron_Command->reschedule()
#12 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()
#13 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}()
#14 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func()
#15 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(419): WP_CLI\Dispatcher\Subcommand->invoke()
#16 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(442): WP_CLI\Runner->run_command()
#17 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1276): WP_CLI\Runner->run_command_and_exit()
#18 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#19 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process()
#20 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#21 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')
#22 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')
#23 {main}
thrown in /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php on line 418
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
I thought it might be something to do with enablin mysqli on my server, where Plesk Web Pro is being used.
I can't find how to do that, but not convinced yet that this might be the answer.

Magento admin giving 500 error - nothing in logs

My Magento-admin stopped working after I tried to install a extension. Now I get a 500 error when I try to access the /admin. Strange thing is that nothing shows up in the error_log. Developer mode log:
Notice: Undefined index: httponly in
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php on
line 7349
#0
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(7349):
mageCoreErrorHandler(8, 'Undefined index...', '/var/www/vhosts...',
7349, Array) #1
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(7421):
Mage_Core_Model_Session_Abstract_Varien->start('adminhtml') #2
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(7777):
Mage_Core_Model_Session_Abstract_Varien->init('core', 'adminhtml') #3
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(33479):
Mage_Core_Model_Session_Abstract->init('core', 'adminhtml') #4
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(23438):
Mage_Core_Model_Session->__construct(Array) #5
/var/www/vhosts/mydomain.com/httpdocs/app/Mage.php(462):
Mage_Core_Model_Config->getModelInstance('core/session', Array) #6
/var/www/vhosts/mydomain.com/httpdocs/app/Mage.php(476):
Mage::getModel('core/session', Array) #7
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(13658):
Mage::getSingleton('core/session', Array) #8
/var/www/vhosts/mydomain.com/httpdocs/includes/src/Mage_Adminhtml_Controller_Action.php(160):
Mage_Core_Controller_Varien_Action->preDispatch() #9
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(13572):
Mage_Adminhtml_Controller_Action->preDispatch() #10
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(17928):
Mage_Core_Controller_Varien_Action->dispatch('index') #11
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(17485):
Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#12
/var/www/vhosts/mydomain.com/httpdocs/includes/src/__default.php(20062):
Mage_Core_Controller_Varien_Front->dispatch() #13
/var/www/vhosts/mydomain.com/httpdocs/app/Mage.php(683):
Mage_Core_Model_App->run(Array) #14
/var/www/vhosts/mydomain.com/httpdocs/index.php(94): Mage::run('',
'store') #15 {main}
Already tried uninstalling the extension, no luck. What should I do to find the cause of the error?
Please, firstly disable compilation, use this:
php -f your_project_folder/shell/compiler.php clear
php -f your_project_folder/shell/compiler.php disable
Then clear cache var/cache. You can just remove this folder.

Magento error after extension installation

I have installed extension from magento connect from website and logged out but when I tried to access admin panel but now I am getting error.
"There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number: 1303816771146"
when i traced error file under var/report i found following error report.
"a:5:{i:0;s:71:"Mage registry key "_singleton/emailattachments/observer" already exists";i:1;s:2604:"
#0 /home/globaltrimming12/public_html/app/Mage.php(223): Mage::throwException('Mage registry k...')
#1 /home/globaltrimming12/public_html/app/Mage.php(477): Mage::register('_singleton/emai...', false)
#2 /home/globaltrimming12/public_html/includes/src/__default.php(21770): Mage::getSingleton('emailattachment...')
#3 /home/globaltrimming12/public_html/app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('core_block_abst...', Array)
#4 /home/globaltrimming12/public_html/includes/src/__default.php(1988): Mage::dispatchEvent('core_block_abst...', Array)
#5 /home/globaltrimming12/public_html/includes/src/__default.php(28179): Mage_Core_Block_Abstract->setLayout(Object(Codnitive_Extifcon_Model_Core_Layout))
#6 /home/globaltrimming12/public_html/includes/src/__default.php(28195): Mage_Core_Model_Layout->createBlock('adminhtml/page_...', 'head')
#7 /home/globaltrimming12/public_html/includes/src/__default.php(27962): Mage_Core_Model_Layout->addBlock('adminhtml/page_...', 'head')
#8 /home/globaltrimming12/public_html/includes/src/__default.php(27928): Mage_Core_Model_Layout->_generateBlock(Object(Mage_Core_Model_Layout_Element), Object(Mage_Core_Model_Layout_Element))
#9 /home/globaltrimming12/public_html/includes/src/__default.php(27929): Mage_Core_Model_Layout->generateBlocks(Object(Mage_Core_Model_Layout_Element))
#10 /home/globaltrimming12/public_html/includes/src/__default.php(14024): Mage_Core_Model_Layout->generateBlocks()
#11 /home/globaltrimming12/public_html/includes/src/__default.php(13949): Mage_Core_Controller_Varien_Action->generateLayoutBlocks()
#12 /home/globaltrimming12/public_html/includes/src/Mage_Adminhtml_Controller_Action.php(275): Mage_Core_Controller_Varien_Action->loadLayout(NULL, true, true)
#13 /home/globaltrimming12/public_html/app/code/core/Mage/Adminhtml/controllers/IndexController.php(81): Mage_Adminhtml_Controller_Action->loadLayout()
#14 /home/globaltrimming12/public_html/includes/src/__default.php(14098): Mage_Adminhtml_IndexController->loginAction()
#15 /home/globaltrimming12/public_html/includes/src/__default.php(18482): Mage_Core_Controller_Varien_Action->dispatch('login')
#16 /home/globaltrimming12/public_html/includes/src/__default.php(18016): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#17 /home/globaltrimming12/public_html/includes/src/__default.php(20808): Mage_Core_Controller_Varien_Front->dispatch()
#18 /home/globaltrimming12/public_html/app/Mage.php(684): Mage_Core_Model_App->run(Array)
#19 /home/globaltrimming12/public_html/index.php(87): Mage::run('', 'store')
#20 {main}";s:3:"url";s:7:"/admin/";s:11:"script_name";s:10:"/index.php";s:4:"skin";s:5:"admin";}"
please let me know where to do changes so I can be able to login to admin panel.
Seems like, your magento compilation is on. Always turn compilation off before installing an extension, and of course disable cache. Find more info on compilation here.

Typo3 solr not showing search result

I have successfully managed to install solr with typo3 6.2
Solr version 4.2
Typo3 version 6.2
Typo3 solr extension 2.8
Indexing processing is working fine as I am not getting anything in the devlog extension .But the problem is that when i try to search something in front end I am getting an error like this.
Es tut uns leid. Ihre Suchanfrage konnte nicht verarbeitet werden.
And in Backend typo3 devlog am getting an error like this
0: exception 'Apache_Solr_ParserException' with message 'Solr response does not appear to be valid JSON, please examine the raw response with getRawResponse() method' in /html/typo3/typo3conf/ext/solr/lib/SolrPhpClient/Apache/Solr/Response.php:206 Stack trace: #0 /html/typo3/typo3conf/ext/solr/lib/SolrPhpClient/Apache/Solr/Response.php(164): Apache_Solr_Response->_parseData() #1 /html/typo3/typo3conf/ext/solr/classes/class.tx_solr_search.php(365): Apache_Solr_Response->__get('response') #2 /html/typo3/typo3conf/ext/solr/pi_results/class.tx_solr_pi_results.php(167): tx_solr_Search->getNumberOfResults() #3 /html/typo3/typo3conf/ext/solr/classes/pluginbase/class.tx_solr_pluginbase_commandpluginbase.php(62): tx_solr_pi_results->getCommandList() #4 /html/typo3/typo3conf/ext/solr/classes/pluginbase/class.tx_solr_pluginbase_pluginbase.php(106): tx_solr_pluginbase_CommandPluginBase->render(NULL) #5 [internal function]: tx_solr_pluginbase_PluginBase->main('', Array) #6 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(6579): call_user_func_array(Array, Array) #7 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/ContentObject/UserContentObject.php(41): TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->callUserFunction('tx_solr_pi_resu...', Array, '') #8 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(863): TYPO3\CMS\Frontend\ContentObject\UserContentObject->render(Array) #9 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php(3641): TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->USER(Array) #10 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php(3589): TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->INTincScript_process(Array) #11 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php(3557): TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->recursivelyReplaceIntPlaceholdersInContent() #12 /html/typo3/typo3_src-6.2.4/typo3/sysext/cms/tslib/index_ts.php(231): TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->INTincScript() #13 /html/typo3/typo3_src-6.2.4/index.php(28): require('/html/typo3/typ...') #14 {main}
0: exception 'Apache_Solr_ParserException' with message 'Solr response does not appear to be valid JSON, please examine the raw response with getRawResponse() method' in /html/typo3/typo3conf/ext/solr/lib/SolrPhpClient/Apache/Solr/Response.php:206 Stack trace: #0 /html/typo3/typo3conf/ext/solr/lib/SolrPhpClient/Apache/Solr/Response.php(164): Apache_Solr_Response->_parseData() #1 /html/typo3/typo3conf/ext/solr/classes/class.tx_solr_search.php(365): Apache_Solr_Response->__get('response') #2 /html/typo3/typo3conf/ext/solr/pi_results/class.tx_solr_pi_results.php(167): tx_solr_Search->getNumberOfResults() #3 /html/typo3/typo3conf/ext/solr/classes/pluginbase/class.tx_solr_pluginbase_commandpluginbase.php(62): tx_solr_pi_results->getCommandList() #4 /html/typo3/typo3conf/ext/solr/classes/pluginbase/class.tx_solr_pluginbase_pluginbase.php(106): tx_solr_pluginbase_CommandPluginBase->render(NULL) #5 [internal function]: tx_solr_pluginbase_PluginBase->main('', Array) #6 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(6579): call_user_func_array(Array, Array) #7 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/ContentObject/UserContentObject.php(41): TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->callUserFunction('tx_solr_pi_resu...', Array, '') #8 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(863): TYPO3\CMS\Frontend\ContentObject\UserContentObject->render(Array) #9 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php(3641): TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->USER(Array) #10 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php(3589): TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->INTincScript_process(Array) #11 /html/typo3/typo3_src-6.2.4/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php(3557): TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->recursivelyReplaceIntPlaceholdersInContent() #12 /html/typo3/typo3_src-6.2.4/typo3/sysext/cms/tslib/index_ts.php(231): TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->INTincScript() #13 /html/typo3/typo3_src-6.2.4/index.php(28): require('/html/typo3/typ...') #14 {main}
Can someone help me with this ??
Any kind of help will appreciated
Thanks in advance
as far as i know Typo3 solr extension 2.8 is not compatible with typo3 6.2. Use 3.0.0 instead

Magento Login to Admin panel throws "Email already exists."

I recently upgraded my Magento system to 1.7.2 and i had several problems.
Most of them were easy to fix but this one is hard.
My problem was that i couldn't log-in as a customer or as an admin to the panel except of 1 user.
So as i got an advice from the internet saying to flush the permission of the admin group.
I did that and now everytime i try to log in to gives me this exception:
Email already exists.
#0 /home/bellater/public_html/app/code/core/Mage/Core/Model/Resource/Db/Abstract.php(676): Mage::throwException('Email already e...')
#1 /home/bellater/public_html/app/code/core/Mage/Core/Model/Resource/Db/Abstract.php(424): Mage_Core_Model_Resource_Db_Abstract->_checkUnique(Object(Mage_Admin_Model_User))
#2 /home/bellater/public_html/app/code/core/Mage/Core/Model/Abstract.php(318): Mage_Core_Model_Resource_Db_Abstract->save(Object(Mage_Admin_Model_User))
#3 /home/bellater/public_html/app/code/core/Mage/Admin/Model/Session.php(142): Mage_Core_Model_Abstract->save()
#4 /home/bellater/public_html/app/code/core/Mage/Admin/Model/Observer.php(95): Mage_Admin_Model_Session->refreshAcl()
#5 /home/bellater/public_html/app/code/core/Mage/Core/Model/App.php(1338): Mage_Admin_Model_Observer->actionPreDispatchAdmin(Object(Varien_Event_Observer))
#6 /home/bellater/public_html/app/code/core/Mage/Core/Model/App.php(1317): Mage_Core_Model_App->_callObserverMethod(Object(Mage_Admin_Model_Observer), 'actionPreDispat...', Object(Varien_Event_Observer))
#7 /home/bellater/public_html/app/Mage.php(447): Mage_Core_Model_App-dispatchEvent('controller_acti...', Array)
#8 /home/bellater/public_html/app/code/core/Mage/Core/Controller/Varien/Action.php(528): Mage::dispatchEvent('controller_acti...', Array)
#9 /home/bellater/public_html/app/code/core/Mage/Adminhtml/Controller/Action.php(160): Mage_Core_Controller_Varien_Action->preDispatch()
#10 /home/bellater/public_html/app/code/core/Mage/Core/Controller/Varien/Action.php(408): Mage_Adminhtml_Controller_Action->preDispatch()
#11 /home/bellater/public_html/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(250): Mage_Core_Controller_Varien_Action->dispatch('index')
#12 /home/bellater/public_html/app/code/core/Mage/Core/Controller/Varien/Front.php(176): Mage_Core_Controller_Varien_Router_Standard-match(Object(Mage_Core_Controller_Request_Http))
#13 /home/bellater/public_html/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#14 /home/bellater/public_html/app/Mage.php(683): Mage_Core_Model_App->run(Array)
#15 /home/bellater/public_html/index.php(87): Mage::run('', 'store')
#16 {main}
can anyone help me please?

Categories