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.
Related
I've been trying to duplicate Odoo's datebase in order to create a production database and a testing one. How can I do this? Once this is ready, how do I know which database I am working at?
You can do database related operation like create new , duplicate , drop, backup database or restore database from odoo ui it self.
http://server_address:port/web/database/manager
Here you will get all the option to manage database from ui.
just click on database manager just below the password field of login page then you can see Menu Named 'DUPLICATE' just click on that then there are two fields write there the source database name and new(Duplicated) Database and then click on Duplicate button on header. It duplicates DB in Seconds
After I have moved my website to the new Domain and server . I cant log into admin.
The admin Url Gets updated but I can't login . The front end home page appears but cant go to categories and products pages.
In the error logs it always show one table or the other missing like this time it shows
a:5:{i:0;s:101:"SQLSTATE[42S02]: Base table or view not found: 1146 Table 'xxxx_table.sales_flat_order' doesn't exist";i:1;s:3451:"#0 /var/www/lib/Varien/Db/Statement/Pdo/Mysql.php(110): Zend_Db_Statement_Pdo->_execute(Array)
Some how if I get over this table it shows another table missing next time .
I have done all the basic troubleshooting:
changed core config URL.
Deleted cache and session and also core cache session path from core_config_data
Followed These:
Magento Admin Not Logging In (after domain transfer)
http://www.magentocommerce.com/wiki/how_to_fix_login_for_admin_on_local_install#dokuwiki__top
No Luck after all this any Guesses, Tips or advice
Procedure of Backup:
Yes I have taken the backup of files and a entire database backup from PhpMyAdmin. Uploaded the file on the Root and then uploaded the database. Infact created the new database with same database name and username as previous .Using same encryption key etc. One things I would like to mention I am modifying the host file to see this current development website via Ip address because on the actual domain we have the live website ? Can this be a issue ?
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 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
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.