Can anybody tell me that how can i remove all the settings associated to the extension from the database tables. Like if i am uninstalling the abc extension than the value abc_setup will also be deleted from the core_resource table. Similarly other setting from the core_config_data table too. And also delete the database tables too. Thanks.....
You will have to do that manually in the database (or sometimes via a script which is provided by the plugin author).
You can easily remove your extension using magento connect. It will remove all associated tables from DB. No settings are saved. And your extension is not EAV type then you can delete that file manually with tables.
Some extension add EAV related row in eav_attribute table so you need to check its setup folder for this and if that has been added you need to delete it manually.
Also one entry of version goes into core config table that too needs to be removed.
Module moght also created tables specific for its own feature looking at its setup folder sql code will give you idea on that.
Plus you need to remove complete module folder and >xml that was added to etc/modules folder.
Related
I am working on magento 1.9 version.I want to add a custom image field in drop down of custom options.
I added a text field using following guide
http://magento.ikantam.com/qa/how-add-custom-attributes-custom-options
which is working fine.but when I add a file field then it shows in admin but not save image field value in database.
please help me to solve this.
Neeraj,
Did you specifically click "flush cache storage" By following this guide and adding new tables directly to the database, Magento already has this record in cache. By flushing cache storage, you will allow magento to recognize the new structure and be able to save the record. I have accidentally forgotten to do this quite a few times and you end up with the inability to save a record even though your structure is there.
I have just moved a Magento install from one server to another, and this is a change of domain too. I have moved all files from one /httpdocs directory to another /httpdocs directory.
I have uploaded the new database and imported the data as well as updated the local.xml file to point to the new database.
But when the site loads I get a default looking Magento page, rather than the correctly skinned Magento store.
Is there some config I have missed?
Make changes in your DB :
In core_config_data table, the values you need to change are in the path column. Change the web/unsecure/base_url and web/secure/base_url to match the new domain name by altering the value column for both records.
After that clear all catch, may you forget to do this step.
The answer is here, look at step 4. http://www.atwix.com/magento/moving-magento-to-another-server/
Log in to admin panel and go to System->Configuration->GENERAL/Design
Open package and themes, then set your custom package & themes name here. After that clear all cache from System->Manage Cache.
Hope it will work!
I need to know if it is advisible to add new table in default database of Joomla. Will it be preserved if I update my Joomla.
If yes, then can anybody describe the steps?
Yes, you can add custom database tables if you wish, it doesn't pose any threats. Just make sure you use Joomla coding standards when getting or adding data from the table. More information on that can be found here:
http://docs.joomla.org/J2.5:Accessing_the_database_using_JDatabase
As for updating Joomla, yes, the table will be preserved.
Hope this helps
As already said, you can add any table you like to your Joomla database. Joomla doesn't care for tables it doesn't know. And those extra tables are not modified by an update.
BUT keep two things in mind:
1. If you make backups of your database with a joomla extension (such as lazyBackup) and you want to backup your extra-tables too, then make sure to include these extra tables by choosing the appropriate options in the backup extension. By default those extra table might not be included in your backup.
2. As you can easily see in phpMyAdmin all joomla tables start with a prefix such as he3ie_. This prefix is different on every joomla installation (if you did not choose your own). It is no good idea to start your extra tables with this prefix. This might collide with joomla-tables which could be created in the future (by joomla or by an extension).
as everybody said adding tables will not be affected by Joomla upgrades unless they decide to name a new table the same as yours. A table "name" could also clash with another extension that you want to install so it would be good advise to spend some time thinking on a name that will make sure is unique to your use or component.
Of course if this is a one-off custom thing then it matters less.
If you are looking for a more in-depth tutorial try this YouTube Video: http://www.youtube.com/watch?v=twT3q7dyVpI
Joomla update doesn't disturb your custom database tables or any other data. Just create the database as you want like phpmyadmin etc & use it without any fear.
I am in the process of moving my local website onto a live webhost and am having some confusion while exporting my database tables from phpMyAdmin.
I attached a screenshot for reference.
It seems as if there are two database tables that are being used for my website, I'm not sure how this happened though. What I am trying to figure out is which database table is the one that I need to export along with all my Joomla files?
I went into my htdocs to check the configuration.php file and it says that the database prefix is xxx (i made this up) BUT when I go look into that database table (on phpMyAdmin) the dates of creation don't match up but are current in the "other database table."
Thank you for your help.
Screenshot for reference
To ascertain which is the correct database, create a new user via the Joomla interface, then have a look at the users Joomla table via phpMyAdmin, in both databases, to see in which database the user got created.
This information can be found in your site's admin at Site => Global Configuration => Server
Site move error:
1) We moved the entire site (zip format) and extracted on server.
2) Created the database instance
3) Updated the database urls in config table and local.xml updated with new details.
When I check in browser, it executes site correctly but templates settings and sliders images tables are deleted and recreated with default entries, because "sql" folder has commands like :
DROP TABLE IF EXISTS {$this->getTable('mtslideshow_slide')};
CREATE TABLE {$this->getTable('mtslideshow_slide')}
DROP TABLE IF EXISTS {$this->getTable('mtslideshow_category')};
CREATE TABLE {$this->getTable('mtslideshow_category')}
Same for some content pages also footer etc are roll backed to default.
How to deal with this issue?
Here I'm facing this issue: http://demo.aarnasystems.net/magento/lacxodemo/index.php/
Logo slider, Amasty filter settings, footer design changes are rolled back.
Please let me know, how to avoid to reinitializing the modules on database connection.
Thanks,
Kiran
But you did copy the entire database to a new server? Because if in core_resource table there would be entry for mtslideshow extension with the same version that it had on the last server, then sql shouldn't be run again.