Error: Mage registry key “_singleton/rkt_jscssforsb/observer” already exists Unicorn Meta...

Would reducing the reference voltage of an ADC have any effect on accuracy?

With indentation set to `0em`, when using a line break, there is still an indentation of a size of a space

All ASCII characters with a given bit count

Where did Arya get these scars?

Is Bran literally the world's memory?

A Paper Record is What I Hamper

Check if a string is entirely made of the same substring

My admission is revoked after accepting the admission offer

Identify story/novel: Tribe on colonized planet, not aware of this. "Taboo," altitude sickness, robot guardian (60s? Young Adult?)

Do I need to protect SFP ports and optics from dust/contaminants? If so, how?

Second order approximation of the loss function (Deep learning book, 7.33)

Why is this method for solving linear equations systems using determinants works?

Could Neutrino technically as side-effect, incentivize centralization of the bitcoin network?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

std::is_constructible on incomplete types

Need of separate security plugins for both root and subfolder sites Wordpress?

PIC mathematical operations weird problem

AI positioning circles within an arc at equal distances and heights

How to not starve gigantic beasts

Multiple options vs single option UI

"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?

Israeli soda type drink

My bank got bought out, am I now going to have to start filing tax returns in a different state?

Are these square matrices always diagonalisable?



Error: Mage registry key “_singleton/rkt_jscssforsb/observer” already exists



Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraMage registry key “_singleton/admin/session” already existsMage registry key “application_params” already existsMage registry key “_singleton/core/resource” already exists - need fixes without clearing cacheMagento 1.9 checkout stuck on shipping methodsMage registry key “_singleton/weee/observer” already existsShopping Cart Rule Causing Internal Sever Error 500Mage::registry not updatingMage registry key “_resource_singleton/newsletter/subscriber” already existsMagento Observer already exists errorMagento configswatches Call to a member function toOptionArray() on a non-objectMage registry key already exists Error





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I am building a magento B2B webshop
and now I cant do anything with it because of some error



a:5:{i:0;s:69:"Mage registry key "_singleton/rkt_jscssforsb/observer" already exists";i:1;s:3637:"#0 app/Mage.php(223): Mage::throwException('Mage registry k...')
#1 app/Mage.php(477): Mage::register('_singleton/rkt_...', false)
#2 app/code/core/Mage/Core/Model/App.php(1316): Mage::getSingleton('rkt_jscssforsb/...')
#3 app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('adminhtml_block...', Array)
#4 app/code/core/Mage/Adminhtml/Block/Template.php(80): Mage::dispatchEvent('adminhtml_block...', Array)
#5 app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Template->_toHtml()
#6 app/code/core/Mage/Adminhtml/Block/Dashboard/Diagrams.php(55): Mage_Core_Block_Abstract->toHtml()
#7 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard_Diagrams->_prepareLayout()
#8 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#9 app/code/core/Mage/Adminhtml/Block/Dashboard.php(66): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...')
#10 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard->_prepareLayout()
#11 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#12 app/code/core/Mage/Core/Model/Layout.php(472): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...', 'dashboard')
#13 app/code/core/Mage/Core/Model/Layout.php(239): Mage_Core_Model_Layout->addBlock('adminhtml/dashb...', 'dashboard')
#14 app/code/core/Mage/Core/Model/Layout.php(205): Mage_Core_Model_Layout->_generateBlock(Object(Mage_Core_Model_Layout_Element), Object(Mage_Core_Model_Layout_Element))
#15 app/code/core/Mage/Core/Model/Layout.php(210): Mage_Core_Model_Layout->generateBlocks(Object(Mage_Core_Model_Layout_Element))
#16 app/code/core/Mage/Core/Controller/Varien/Action.php(344): Mage_Core_Model_Layout->generateBlocks()
#17 app/code/core/Mage/Core/Controller/Varien/Action.php(269): Mage_Core_Controller_Varien_Action->generateLayoutBlocks()
#18 app/code/core/Mage/Adminhtml/Controller/Action.php(275): Mage_Core_Controller_Varien_Action->loadLayout(NULL, true, true)
#19 app/code/core/Mage/Adminhtml/controllers/DashboardController.php(40): Mage_Adminhtml_Controller_Action->loadLayout()
#20 app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_DashboardController->indexAction()
#21 app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(250): Mage_Core_Controller_Varien_Action->dispatch('index')
#22 app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#23 app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#24 app/Mage.php(684): Mage_Core_Model_App->run(Array)
#25 index.php(87): Mage::run('', 'store')
#26 {main}";s:3:"url";s:81:"/Magento/index.php/ma_admin/dashboard/index/key/f1e58b7d15977224c929ac0010422f85/";s:11:"script_name";s:18:"/Magento/index.php";s:4:"skin";s:5:"admin";}









share|improve this question

























  • Can you explain what you have done so far and when the errors started to occur? We need more information to help you

    – Sander Mangel
    Mar 3 '15 at 12:57











  • Did you clear the cache?

    – Marius
    Mar 3 '15 at 13:02











  • the error started after i tried to unistall a plugin from the connect manager js and css for static block because i didnt need it and i couldnt save static block properly

    – DaanRio
    Mar 3 '15 at 13:02




















2















I am building a magento B2B webshop
and now I cant do anything with it because of some error



a:5:{i:0;s:69:"Mage registry key "_singleton/rkt_jscssforsb/observer" already exists";i:1;s:3637:"#0 app/Mage.php(223): Mage::throwException('Mage registry k...')
#1 app/Mage.php(477): Mage::register('_singleton/rkt_...', false)
#2 app/code/core/Mage/Core/Model/App.php(1316): Mage::getSingleton('rkt_jscssforsb/...')
#3 app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('adminhtml_block...', Array)
#4 app/code/core/Mage/Adminhtml/Block/Template.php(80): Mage::dispatchEvent('adminhtml_block...', Array)
#5 app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Template->_toHtml()
#6 app/code/core/Mage/Adminhtml/Block/Dashboard/Diagrams.php(55): Mage_Core_Block_Abstract->toHtml()
#7 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard_Diagrams->_prepareLayout()
#8 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#9 app/code/core/Mage/Adminhtml/Block/Dashboard.php(66): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...')
#10 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard->_prepareLayout()
#11 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#12 app/code/core/Mage/Core/Model/Layout.php(472): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...', 'dashboard')
#13 app/code/core/Mage/Core/Model/Layout.php(239): Mage_Core_Model_Layout->addBlock('adminhtml/dashb...', 'dashboard')
#14 app/code/core/Mage/Core/Model/Layout.php(205): Mage_Core_Model_Layout->_generateBlock(Object(Mage_Core_Model_Layout_Element), Object(Mage_Core_Model_Layout_Element))
#15 app/code/core/Mage/Core/Model/Layout.php(210): Mage_Core_Model_Layout->generateBlocks(Object(Mage_Core_Model_Layout_Element))
#16 app/code/core/Mage/Core/Controller/Varien/Action.php(344): Mage_Core_Model_Layout->generateBlocks()
#17 app/code/core/Mage/Core/Controller/Varien/Action.php(269): Mage_Core_Controller_Varien_Action->generateLayoutBlocks()
#18 app/code/core/Mage/Adminhtml/Controller/Action.php(275): Mage_Core_Controller_Varien_Action->loadLayout(NULL, true, true)
#19 app/code/core/Mage/Adminhtml/controllers/DashboardController.php(40): Mage_Adminhtml_Controller_Action->loadLayout()
#20 app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_DashboardController->indexAction()
#21 app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(250): Mage_Core_Controller_Varien_Action->dispatch('index')
#22 app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#23 app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#24 app/Mage.php(684): Mage_Core_Model_App->run(Array)
#25 index.php(87): Mage::run('', 'store')
#26 {main}";s:3:"url";s:81:"/Magento/index.php/ma_admin/dashboard/index/key/f1e58b7d15977224c929ac0010422f85/";s:11:"script_name";s:18:"/Magento/index.php";s:4:"skin";s:5:"admin";}









share|improve this question

























  • Can you explain what you have done so far and when the errors started to occur? We need more information to help you

    – Sander Mangel
    Mar 3 '15 at 12:57











  • Did you clear the cache?

    – Marius
    Mar 3 '15 at 13:02











  • the error started after i tried to unistall a plugin from the connect manager js and css for static block because i didnt need it and i couldnt save static block properly

    – DaanRio
    Mar 3 '15 at 13:02
















2












2








2








I am building a magento B2B webshop
and now I cant do anything with it because of some error



a:5:{i:0;s:69:"Mage registry key "_singleton/rkt_jscssforsb/observer" already exists";i:1;s:3637:"#0 app/Mage.php(223): Mage::throwException('Mage registry k...')
#1 app/Mage.php(477): Mage::register('_singleton/rkt_...', false)
#2 app/code/core/Mage/Core/Model/App.php(1316): Mage::getSingleton('rkt_jscssforsb/...')
#3 app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('adminhtml_block...', Array)
#4 app/code/core/Mage/Adminhtml/Block/Template.php(80): Mage::dispatchEvent('adminhtml_block...', Array)
#5 app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Template->_toHtml()
#6 app/code/core/Mage/Adminhtml/Block/Dashboard/Diagrams.php(55): Mage_Core_Block_Abstract->toHtml()
#7 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard_Diagrams->_prepareLayout()
#8 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#9 app/code/core/Mage/Adminhtml/Block/Dashboard.php(66): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...')
#10 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard->_prepareLayout()
#11 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#12 app/code/core/Mage/Core/Model/Layout.php(472): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...', 'dashboard')
#13 app/code/core/Mage/Core/Model/Layout.php(239): Mage_Core_Model_Layout->addBlock('adminhtml/dashb...', 'dashboard')
#14 app/code/core/Mage/Core/Model/Layout.php(205): Mage_Core_Model_Layout->_generateBlock(Object(Mage_Core_Model_Layout_Element), Object(Mage_Core_Model_Layout_Element))
#15 app/code/core/Mage/Core/Model/Layout.php(210): Mage_Core_Model_Layout->generateBlocks(Object(Mage_Core_Model_Layout_Element))
#16 app/code/core/Mage/Core/Controller/Varien/Action.php(344): Mage_Core_Model_Layout->generateBlocks()
#17 app/code/core/Mage/Core/Controller/Varien/Action.php(269): Mage_Core_Controller_Varien_Action->generateLayoutBlocks()
#18 app/code/core/Mage/Adminhtml/Controller/Action.php(275): Mage_Core_Controller_Varien_Action->loadLayout(NULL, true, true)
#19 app/code/core/Mage/Adminhtml/controllers/DashboardController.php(40): Mage_Adminhtml_Controller_Action->loadLayout()
#20 app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_DashboardController->indexAction()
#21 app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(250): Mage_Core_Controller_Varien_Action->dispatch('index')
#22 app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#23 app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#24 app/Mage.php(684): Mage_Core_Model_App->run(Array)
#25 index.php(87): Mage::run('', 'store')
#26 {main}";s:3:"url";s:81:"/Magento/index.php/ma_admin/dashboard/index/key/f1e58b7d15977224c929ac0010422f85/";s:11:"script_name";s:18:"/Magento/index.php";s:4:"skin";s:5:"admin";}









share|improve this question
















I am building a magento B2B webshop
and now I cant do anything with it because of some error



a:5:{i:0;s:69:"Mage registry key "_singleton/rkt_jscssforsb/observer" already exists";i:1;s:3637:"#0 app/Mage.php(223): Mage::throwException('Mage registry k...')
#1 app/Mage.php(477): Mage::register('_singleton/rkt_...', false)
#2 app/code/core/Mage/Core/Model/App.php(1316): Mage::getSingleton('rkt_jscssforsb/...')
#3 app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('adminhtml_block...', Array)
#4 app/code/core/Mage/Adminhtml/Block/Template.php(80): Mage::dispatchEvent('adminhtml_block...', Array)
#5 app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Template->_toHtml()
#6 app/code/core/Mage/Adminhtml/Block/Dashboard/Diagrams.php(55): Mage_Core_Block_Abstract->toHtml()
#7 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard_Diagrams->_prepareLayout()
#8 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#9 app/code/core/Mage/Adminhtml/Block/Dashboard.php(66): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...')
#10 app/code/core/Mage/Core/Block/Abstract.php(293): Mage_Adminhtml_Block_Dashboard->_prepareLayout()
#11 app/code/core/Mage/Core/Model/Layout.php(456): Mage_Core_Block_Abstract->setLayout(Object(Mage_Core_Model_Layout))
#12 app/code/core/Mage/Core/Model/Layout.php(472): Mage_Core_Model_Layout->createBlock('adminhtml/dashb...', 'dashboard')
#13 app/code/core/Mage/Core/Model/Layout.php(239): Mage_Core_Model_Layout->addBlock('adminhtml/dashb...', 'dashboard')
#14 app/code/core/Mage/Core/Model/Layout.php(205): Mage_Core_Model_Layout->_generateBlock(Object(Mage_Core_Model_Layout_Element), Object(Mage_Core_Model_Layout_Element))
#15 app/code/core/Mage/Core/Model/Layout.php(210): Mage_Core_Model_Layout->generateBlocks(Object(Mage_Core_Model_Layout_Element))
#16 app/code/core/Mage/Core/Controller/Varien/Action.php(344): Mage_Core_Model_Layout->generateBlocks()
#17 app/code/core/Mage/Core/Controller/Varien/Action.php(269): Mage_Core_Controller_Varien_Action->generateLayoutBlocks()
#18 app/code/core/Mage/Adminhtml/Controller/Action.php(275): Mage_Core_Controller_Varien_Action->loadLayout(NULL, true, true)
#19 app/code/core/Mage/Adminhtml/controllers/DashboardController.php(40): Mage_Adminhtml_Controller_Action->loadLayout()
#20 app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_DashboardController->indexAction()
#21 app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(250): Mage_Core_Controller_Varien_Action->dispatch('index')
#22 app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#23 app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#24 app/Mage.php(684): Mage_Core_Model_App->run(Array)
#25 index.php(87): Mage::run('', 'store')
#26 {main}";s:3:"url";s:81:"/Magento/index.php/ma_admin/dashboard/index/key/f1e58b7d15977224c929ac0010422f85/";s:11:"script_name";s:18:"/Magento/index.php";s:4:"skin";s:5:"admin";}






ce-1.9.1.0 registry






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 3 '15 at 13:02









Sander Mangel

35k571138




35k571138










asked Mar 3 '15 at 12:56









DaanRioDaanRio

651111




651111













  • Can you explain what you have done so far and when the errors started to occur? We need more information to help you

    – Sander Mangel
    Mar 3 '15 at 12:57











  • Did you clear the cache?

    – Marius
    Mar 3 '15 at 13:02











  • the error started after i tried to unistall a plugin from the connect manager js and css for static block because i didnt need it and i couldnt save static block properly

    – DaanRio
    Mar 3 '15 at 13:02





















  • Can you explain what you have done so far and when the errors started to occur? We need more information to help you

    – Sander Mangel
    Mar 3 '15 at 12:57











  • Did you clear the cache?

    – Marius
    Mar 3 '15 at 13:02











  • the error started after i tried to unistall a plugin from the connect manager js and css for static block because i didnt need it and i couldnt save static block properly

    – DaanRio
    Mar 3 '15 at 13:02



















Can you explain what you have done so far and when the errors started to occur? We need more information to help you

– Sander Mangel
Mar 3 '15 at 12:57





Can you explain what you have done so far and when the errors started to occur? We need more information to help you

– Sander Mangel
Mar 3 '15 at 12:57













Did you clear the cache?

– Marius
Mar 3 '15 at 13:02





Did you clear the cache?

– Marius
Mar 3 '15 at 13:02













the error started after i tried to unistall a plugin from the connect manager js and css for static block because i didnt need it and i couldnt save static block properly

– DaanRio
Mar 3 '15 at 13:02







the error started after i tried to unistall a plugin from the connect manager js and css for static block because i didnt need it and i couldnt save static block properly

– DaanRio
Mar 3 '15 at 13:02












4 Answers
4






active

oldest

votes


















9














Your PHP developer should be able to solve the exact problem with this trace, but to explain the Problem:



You have an observer which calls rkt_jscssforsb/observer as singleton (the default) but this model could not be loaded, so it saves false in the registry, which is not recognized by the next call of this singleton as it has the value false, so it is tried again to call this singleton, but the registry does not allow to write a value, which already exist.



Thats why you get the error message:
Mage registry key "_singleton/rkt_jscssforsb/observer" already exists



As you noted in your comment, you uninstalled a module, if this module had the name rkt_jscssforsb you should first try to clean the cache, maybe forcefully by delete magento/var/cache/* or try to grep/search trough the code for the occurence of it to clean up the rest






share|improve this answer


























  • yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

    – DaanRio
    Mar 3 '15 at 13:09











  • Thanks maby that works the i tried to unistall that module but that didnt work

    – DaanRio
    Mar 3 '15 at 13:17



















3














I faced the same issue while removing the extension manually.



Approach to follow:

1. Revert the changes made.

2. With that, you will get the admin panel. Now, disable compliation at system>tools>compilation & disable all the cache types under at system>cache management.

3. Now remove the extension the way you were removing.

4. Go to admin panel, it must be working now. Clear cache from system>cache management.



Hope, this help to someone!






share|improve this answer































    2














    Check if your event observer xml code in your module's config.xml is all correct.



    It should be something like this:



    <events>
    <event_name_that_you_are_working_on>
    <observers>
    <some_unique_identifier>
    <type>singleton</type>
    <class>YourNamespace_YourModule_Model_Observer</class>
    <method>functionNameInYourObserver</method>
    </some_unique_identifier>
    </observers>
    </event_name_that_you_are_working_on>
    </events>


    I once got this kind of error because I was using modulename/observer inside class node. Using full class name (YourNamespace_YourModule_Model_Observer) solved the error for me.



    In your module's event-observer xml code, you might be using class like below:



    <class>yourmodule/observer</class>


    Try using this instead (as done in above event-observer xml code):



    <class>YourNamespace_YourModule_Model_Observer</class>





    share|improve this answer































      0














      Porque ocorre?
      O compilador do Magento basicamente faz com que todas as classes, de todos os módulos sejam reunidos em um único arquivo PHP. Porém, ele faz isso de tempos em tempos, cacheando esse arquivo. Quando se instala um novo módulo, ele não atualiza esse arquivo principal.



      Como resolver
      Para resolver é muito simples. Só precisamos atualizar o compilador. Para isso, abra o terminal da sua loja usando um acesso SSH, vá até o diretório base(raíz) da sua loja magento e digite os seguintes comandos:



      php -f shell/compiler.php disable 
      php -f shell/compiler.php clear
      php -f shell/compiler.php compile
      sudo rm -r var/cache/*


      Você também pode desabilitar o compilador do magento em Sistema->Ferramentas->Compilador.






      share|improve this answer








      New contributor




      Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





















        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "479"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f59406%2ferror-mage-registry-key-singleton-rkt-jscssforsb-observer-already-exists%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        4 Answers
        4






        active

        oldest

        votes








        4 Answers
        4






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        9














        Your PHP developer should be able to solve the exact problem with this trace, but to explain the Problem:



        You have an observer which calls rkt_jscssforsb/observer as singleton (the default) but this model could not be loaded, so it saves false in the registry, which is not recognized by the next call of this singleton as it has the value false, so it is tried again to call this singleton, but the registry does not allow to write a value, which already exist.



        Thats why you get the error message:
        Mage registry key "_singleton/rkt_jscssforsb/observer" already exists



        As you noted in your comment, you uninstalled a module, if this module had the name rkt_jscssforsb you should first try to clean the cache, maybe forcefully by delete magento/var/cache/* or try to grep/search trough the code for the occurence of it to clean up the rest






        share|improve this answer


























        • yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

          – DaanRio
          Mar 3 '15 at 13:09











        • Thanks maby that works the i tried to unistall that module but that didnt work

          – DaanRio
          Mar 3 '15 at 13:17
















        9














        Your PHP developer should be able to solve the exact problem with this trace, but to explain the Problem:



        You have an observer which calls rkt_jscssforsb/observer as singleton (the default) but this model could not be loaded, so it saves false in the registry, which is not recognized by the next call of this singleton as it has the value false, so it is tried again to call this singleton, but the registry does not allow to write a value, which already exist.



        Thats why you get the error message:
        Mage registry key "_singleton/rkt_jscssforsb/observer" already exists



        As you noted in your comment, you uninstalled a module, if this module had the name rkt_jscssforsb you should first try to clean the cache, maybe forcefully by delete magento/var/cache/* or try to grep/search trough the code for the occurence of it to clean up the rest






        share|improve this answer


























        • yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

          – DaanRio
          Mar 3 '15 at 13:09











        • Thanks maby that works the i tried to unistall that module but that didnt work

          – DaanRio
          Mar 3 '15 at 13:17














        9












        9








        9







        Your PHP developer should be able to solve the exact problem with this trace, but to explain the Problem:



        You have an observer which calls rkt_jscssforsb/observer as singleton (the default) but this model could not be loaded, so it saves false in the registry, which is not recognized by the next call of this singleton as it has the value false, so it is tried again to call this singleton, but the registry does not allow to write a value, which already exist.



        Thats why you get the error message:
        Mage registry key "_singleton/rkt_jscssforsb/observer" already exists



        As you noted in your comment, you uninstalled a module, if this module had the name rkt_jscssforsb you should first try to clean the cache, maybe forcefully by delete magento/var/cache/* or try to grep/search trough the code for the occurence of it to clean up the rest






        share|improve this answer















        Your PHP developer should be able to solve the exact problem with this trace, but to explain the Problem:



        You have an observer which calls rkt_jscssforsb/observer as singleton (the default) but this model could not be loaded, so it saves false in the registry, which is not recognized by the next call of this singleton as it has the value false, so it is tried again to call this singleton, but the registry does not allow to write a value, which already exist.



        Thats why you get the error message:
        Mage registry key "_singleton/rkt_jscssforsb/observer" already exists



        As you noted in your comment, you uninstalled a module, if this module had the name rkt_jscssforsb you should first try to clean the cache, maybe forcefully by delete magento/var/cache/* or try to grep/search trough the code for the occurence of it to clean up the rest







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 3 '15 at 13:15

























        answered Mar 3 '15 at 13:07









        FlyingmanaFlyingmana

        5,17632062




        5,17632062













        • yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

          – DaanRio
          Mar 3 '15 at 13:09











        • Thanks maby that works the i tried to unistall that module but that didnt work

          – DaanRio
          Mar 3 '15 at 13:17



















        • yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

          – DaanRio
          Mar 3 '15 at 13:09











        • Thanks maby that works the i tried to unistall that module but that didnt work

          – DaanRio
          Mar 3 '15 at 13:17

















        yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

        – DaanRio
        Mar 3 '15 at 13:09





        yeah I have to do it all on my own I know a litlle PHP But i am all new to magento :$

        – DaanRio
        Mar 3 '15 at 13:09













        Thanks maby that works the i tried to unistall that module but that didnt work

        – DaanRio
        Mar 3 '15 at 13:17





        Thanks maby that works the i tried to unistall that module but that didnt work

        – DaanRio
        Mar 3 '15 at 13:17













        3














        I faced the same issue while removing the extension manually.



        Approach to follow:

        1. Revert the changes made.

        2. With that, you will get the admin panel. Now, disable compliation at system>tools>compilation & disable all the cache types under at system>cache management.

        3. Now remove the extension the way you were removing.

        4. Go to admin panel, it must be working now. Clear cache from system>cache management.



        Hope, this help to someone!






        share|improve this answer




























          3














          I faced the same issue while removing the extension manually.



          Approach to follow:

          1. Revert the changes made.

          2. With that, you will get the admin panel. Now, disable compliation at system>tools>compilation & disable all the cache types under at system>cache management.

          3. Now remove the extension the way you were removing.

          4. Go to admin panel, it must be working now. Clear cache from system>cache management.



          Hope, this help to someone!






          share|improve this answer


























            3












            3








            3







            I faced the same issue while removing the extension manually.



            Approach to follow:

            1. Revert the changes made.

            2. With that, you will get the admin panel. Now, disable compliation at system>tools>compilation & disable all the cache types under at system>cache management.

            3. Now remove the extension the way you were removing.

            4. Go to admin panel, it must be working now. Clear cache from system>cache management.



            Hope, this help to someone!






            share|improve this answer













            I faced the same issue while removing the extension manually.



            Approach to follow:

            1. Revert the changes made.

            2. With that, you will get the admin panel. Now, disable compliation at system>tools>compilation & disable all the cache types under at system>cache management.

            3. Now remove the extension the way you were removing.

            4. Go to admin panel, it must be working now. Clear cache from system>cache management.



            Hope, this help to someone!







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 8 '16 at 14:41









            Anurag KhandelwalAnurag Khandelwal

            3441417




            3441417























                2














                Check if your event observer xml code in your module's config.xml is all correct.



                It should be something like this:



                <events>
                <event_name_that_you_are_working_on>
                <observers>
                <some_unique_identifier>
                <type>singleton</type>
                <class>YourNamespace_YourModule_Model_Observer</class>
                <method>functionNameInYourObserver</method>
                </some_unique_identifier>
                </observers>
                </event_name_that_you_are_working_on>
                </events>


                I once got this kind of error because I was using modulename/observer inside class node. Using full class name (YourNamespace_YourModule_Model_Observer) solved the error for me.



                In your module's event-observer xml code, you might be using class like below:



                <class>yourmodule/observer</class>


                Try using this instead (as done in above event-observer xml code):



                <class>YourNamespace_YourModule_Model_Observer</class>





                share|improve this answer




























                  2














                  Check if your event observer xml code in your module's config.xml is all correct.



                  It should be something like this:



                  <events>
                  <event_name_that_you_are_working_on>
                  <observers>
                  <some_unique_identifier>
                  <type>singleton</type>
                  <class>YourNamespace_YourModule_Model_Observer</class>
                  <method>functionNameInYourObserver</method>
                  </some_unique_identifier>
                  </observers>
                  </event_name_that_you_are_working_on>
                  </events>


                  I once got this kind of error because I was using modulename/observer inside class node. Using full class name (YourNamespace_YourModule_Model_Observer) solved the error for me.



                  In your module's event-observer xml code, you might be using class like below:



                  <class>yourmodule/observer</class>


                  Try using this instead (as done in above event-observer xml code):



                  <class>YourNamespace_YourModule_Model_Observer</class>





                  share|improve this answer


























                    2












                    2








                    2







                    Check if your event observer xml code in your module's config.xml is all correct.



                    It should be something like this:



                    <events>
                    <event_name_that_you_are_working_on>
                    <observers>
                    <some_unique_identifier>
                    <type>singleton</type>
                    <class>YourNamespace_YourModule_Model_Observer</class>
                    <method>functionNameInYourObserver</method>
                    </some_unique_identifier>
                    </observers>
                    </event_name_that_you_are_working_on>
                    </events>


                    I once got this kind of error because I was using modulename/observer inside class node. Using full class name (YourNamespace_YourModule_Model_Observer) solved the error for me.



                    In your module's event-observer xml code, you might be using class like below:



                    <class>yourmodule/observer</class>


                    Try using this instead (as done in above event-observer xml code):



                    <class>YourNamespace_YourModule_Model_Observer</class>





                    share|improve this answer













                    Check if your event observer xml code in your module's config.xml is all correct.



                    It should be something like this:



                    <events>
                    <event_name_that_you_are_working_on>
                    <observers>
                    <some_unique_identifier>
                    <type>singleton</type>
                    <class>YourNamespace_YourModule_Model_Observer</class>
                    <method>functionNameInYourObserver</method>
                    </some_unique_identifier>
                    </observers>
                    </event_name_that_you_are_working_on>
                    </events>


                    I once got this kind of error because I was using modulename/observer inside class node. Using full class name (YourNamespace_YourModule_Model_Observer) solved the error for me.



                    In your module's event-observer xml code, you might be using class like below:



                    <class>yourmodule/observer</class>


                    Try using this instead (as done in above event-observer xml code):



                    <class>YourNamespace_YourModule_Model_Observer</class>






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Apr 8 '16 at 12:47









                    Mukesh ChapagainMukesh Chapagain

                    3,90612343




                    3,90612343























                        0














                        Porque ocorre?
                        O compilador do Magento basicamente faz com que todas as classes, de todos os módulos sejam reunidos em um único arquivo PHP. Porém, ele faz isso de tempos em tempos, cacheando esse arquivo. Quando se instala um novo módulo, ele não atualiza esse arquivo principal.



                        Como resolver
                        Para resolver é muito simples. Só precisamos atualizar o compilador. Para isso, abra o terminal da sua loja usando um acesso SSH, vá até o diretório base(raíz) da sua loja magento e digite os seguintes comandos:



                        php -f shell/compiler.php disable 
                        php -f shell/compiler.php clear
                        php -f shell/compiler.php compile
                        sudo rm -r var/cache/*


                        Você também pode desabilitar o compilador do magento em Sistema->Ferramentas->Compilador.






                        share|improve this answer








                        New contributor




                        Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.

























                          0














                          Porque ocorre?
                          O compilador do Magento basicamente faz com que todas as classes, de todos os módulos sejam reunidos em um único arquivo PHP. Porém, ele faz isso de tempos em tempos, cacheando esse arquivo. Quando se instala um novo módulo, ele não atualiza esse arquivo principal.



                          Como resolver
                          Para resolver é muito simples. Só precisamos atualizar o compilador. Para isso, abra o terminal da sua loja usando um acesso SSH, vá até o diretório base(raíz) da sua loja magento e digite os seguintes comandos:



                          php -f shell/compiler.php disable 
                          php -f shell/compiler.php clear
                          php -f shell/compiler.php compile
                          sudo rm -r var/cache/*


                          Você também pode desabilitar o compilador do magento em Sistema->Ferramentas->Compilador.






                          share|improve this answer








                          New contributor




                          Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.























                            0












                            0








                            0







                            Porque ocorre?
                            O compilador do Magento basicamente faz com que todas as classes, de todos os módulos sejam reunidos em um único arquivo PHP. Porém, ele faz isso de tempos em tempos, cacheando esse arquivo. Quando se instala um novo módulo, ele não atualiza esse arquivo principal.



                            Como resolver
                            Para resolver é muito simples. Só precisamos atualizar o compilador. Para isso, abra o terminal da sua loja usando um acesso SSH, vá até o diretório base(raíz) da sua loja magento e digite os seguintes comandos:



                            php -f shell/compiler.php disable 
                            php -f shell/compiler.php clear
                            php -f shell/compiler.php compile
                            sudo rm -r var/cache/*


                            Você também pode desabilitar o compilador do magento em Sistema->Ferramentas->Compilador.






                            share|improve this answer








                            New contributor




                            Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.










                            Porque ocorre?
                            O compilador do Magento basicamente faz com que todas as classes, de todos os módulos sejam reunidos em um único arquivo PHP. Porém, ele faz isso de tempos em tempos, cacheando esse arquivo. Quando se instala um novo módulo, ele não atualiza esse arquivo principal.



                            Como resolver
                            Para resolver é muito simples. Só precisamos atualizar o compilador. Para isso, abra o terminal da sua loja usando um acesso SSH, vá até o diretório base(raíz) da sua loja magento e digite os seguintes comandos:



                            php -f shell/compiler.php disable 
                            php -f shell/compiler.php clear
                            php -f shell/compiler.php compile
                            sudo rm -r var/cache/*


                            Você também pode desabilitar o compilador do magento em Sistema->Ferramentas->Compilador.







                            share|improve this answer








                            New contributor




                            Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            share|improve this answer



                            share|improve this answer






                            New contributor




                            Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            answered 3 hours ago









                            Tiago França FernandesTiago França Fernandes

                            1




                            1




                            New contributor




                            Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





                            New contributor





                            Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            Tiago França Fernandes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Magento Stack Exchange!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f59406%2ferror-mage-registry-key-singleton-rkt-jscssforsb-observer-already-exists%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

                                How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

                                變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...