I was disabling the extensions one by one to check a problem, but accidentally disabled some of the core extensions. Immediately the backend went blank and so I tried to enable all the extensions that I disabled in etc/modules. After that I cleared everything inside var folder but it was still not working.
So I copied the whole of etc/modules folder to replace but it still doesn't work after clearing cache by deleting cache folder.
Then I copied app folder and change local.xml, but it still doesn't work.
How can I restore back my admin page?
My Magento Version is 1.7
Thanks.
Since you have disabled the modules from backend you need to enable it directly from database.The table core_config_data holds the data whether the module is enabled/disabled.Execute the below query and it will list all the available modules
SELECT * FROM `core_config_data` WHERE `path` LIKE '%advanced/modules_disable_output/%'
Now choose the appropriate row and set the value to 0.
Related
I accidentally installed a more recent component of J2XML designed for Joomla 3 into my J2.5 site... and now I have no idea how to remove it. The only Admin page that works is the main Admin page... all the other admin pages are blank... I'm assuming it's logging the error somewhere, but I have no idea where that would be.
Can I manually remove the extension/module? What database tables should i remove?
I have already removed the folder of files, but I'm not familiar enough with the Joomla db structure to know what damage has been caused.
And in this case, backups have failed me.
you should able to look at _components table and remove J2XML entry so it doesn't show in administrator panel
I'm developing a Magento store and there is a guy that manages the store, we were transferring the store to another domain but the old one was with all products.
The guy went in advanced configurations and disabled all modules in the old Magento installation, even the Mage ones and now the initial page is white and the admin is too, what could I do to solve this problem?
The version of Magento is 1.9.1.1.
So, he disabled all the Mage modules, including REMOVE ENGINE ie Mage Core?
Hmm...
Ok, here's what you do.
Use phpMyAdmin to open core_config_data, sort table by path and look for all the paths beginning with advanced/modules_disable_output/Mage_ and change the value from 1 to 0
Then delete all the mage--? subfolders in var/cache/ so Magento is forced to reload the configuration data out of the core_config_data table.
This should put your engine back in so the old jalopy will run.
My Magento cart page is not showing at all. It just comes up with a blank page. Previously this site was developed by another developer and He has disabled the Checkout process. Now I cannot find which settings he has done to stop the checkout process.
Can anyone tell me what are the possibilities to stop the default module from working.
Also every thing else is coming right on the cart page. Header and footer and all the things just that it is not rendering the html for cart block. The Content just came up empty, with no HTML.
Please open the adminpanel and then go to the
System/Configuration/Advanced
there is a tab Disable Modules Output and then enable the Mage_checkout module
As I have told you the previous developer have disabled the modules. But that was not the case the developer have installed some extensions to disable the checkout process but that does not work very well. Then he tries to delete the extensions the wrong way so the entries that were made by those extensions was still in the database table "core_config_data".
And these values are being used by the left over files of the extensions ans he has overridden the magento core files for that. I just copy and replace the core magento files and also cleared the table "core_config_data" table and all things got working once again.
I had a component cause a bunch of errors at installation in my Joomla website. I tried the normal way of removing it by visiting the extension manager and clicking uninstall. This did not work, so I visited these two locations and deleted all the files:
../administrator/components/com_badcomponentname
../components/com_badcomponentname
I then went into phpmyadmin and dropped all the tables that were associated with com_badcomponentname.
The only thing that is left is the listing in the extension manager. I want to be 100% done with this component, but the name still shows up. I can disable the listing and that gets it out of the components drop down list in the admin panel. Where can I go to manually remove the reference?
You say that you dropped all the tables that were associated with the component, however if it is still showing in the Extension Manager, then go back into PhpMyAdmin, go into the table jos_extensions (jos being the prefix which may be different for you) and remove the reference in there too
Ideally you would want to to a search on all tables for the name of the component with or without the prefix com_.
Also inspecting the install SQL files would give you a better idea if you deleted all the associated tables.
In my case, based on #Valentin Despa's answer, I grep'd the full SQL dump of the site, and found the stale menu items in the jos_menu table.
I've got a Magento site however when I login into the admin area to create a new CMS page the content box is appearing in the Page Information tab and not the Content tab. This is causing the validation to fail when I add the content.
Any help would be much appreciated
Try disabling any third party extensions/customizations you may of installed.
It could also be caused by corrupted database entries.
Try reinstalling Magento to a new database and seeing if the issue persists.
If it's fixed, then it's a problem with your data. If it isn't, then it must be a extension or customization causing the bug.
Go to System>Configuration>Advanced and you will see a brand of extension you recently installed. Set it to disabled and hit Save Config. Flush Cache, log out and log back in to admin and it should be corrected. If it is, contact the extension creator and report the bug as it shouldnt do that.The only realy way for that to happen is for something to overrule its placement which would be a 3rd party extension.
The other possibility is that you moved some folders in adminhtml by accident. If thats the case, try uploading an original copy of adminhtml.