This is the error message that I received when logging onto the homepage after I installed the sample products for the 0.7.15480 release. any ideas on how I can fix this. it was installed into a clean database.
I’ve got mine working by importing the sample data into an empty database I had called “magento”. The SQL import didn’t succeed without errors, but there were 174 tables in the database after a few tries and I decided that was enough for now
I followed that up with an install from a tar file with the “beta” option chosen for package download.
so:
- drop & create new database (dropping the tables inside an existing database instead is cumbersome because of relations throwing errors upon delete)
- import sample data
- install newest magento version
Before running every batch of SQL commands, run this:
SET SQL_MODE=''; SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO';
After each one run this:
SET SQL_MODE=IFNULL(@OLD_SQL_MODE,''); SET FOREIGN_KEY_CHECKS=IFNULL(@OLD_FOREIGN_KEY_CHECKS,0);
Hello...just getting into this platform. Seems nice so far.
I’m trying to load the sample data. I dropped all my tables, reinstalled. I had already loaded the necessary files into the /media folder. When I get into the admin backend, there are no products. I think the question is this: Do I load the sample data SQL script BEFORE or AFTER I reinstall. Should there be zero tables in my DB when I run the script? Or do I let the install happen, then load the sample script.
I’m having trouble importing the sample data into MySql via Phpadmin. When attemping I receive the following error:
No data was received to import. Either no file name was submitted, or the file size exceeded the maximum size permitted by your PHP configuration. See FAQ 1.16.
What did I miss? Thanks!
Running Ubuntu 7.10 (32bit), MySQL 5.0.45, PHP 5.2.3
Before running every batch of SQL commands, run this:
SET SQL_MODE=''; SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO';
Thanks for the help, but I still get the same error :-(
Any other idea?
I ended up doing a command line import with the data using
mysql -u USER -p DBNAME < dump.sql
Thank you MindWerks… that method worked a treat…
tried latest phpmyadmin - loads of errors importing…
tried MySQL Query browser - errors
tried bigdump php script - same error.......
To use MindWerk’s method, I...
1) deleted all tables from my shop database,
2) copied a clean version of magento to my webroot folder,
3) installed magento,
4) ran the MySql -u root -p shop < sample_data.sql from a command prompt
5) went into magento admin (remember that the install overwrites admin user id with uid=’admin’ pw=’123123’) and selected ‘System-->Cache Management’
6) Selected the ‘Refresh All Cache’ checkbox and then ‘Save cache settings’
7) back to frontend - all data now shown
Before running every batch of SQL commands, run this:
SET SQL_MODE=''; SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO';
Thanks for the help, but I still get the same error :-(
Any other idea?
Hi! I get the same error on a clean new database (not even sample data). I too tried Moshe’s fixe to no avail. I understand the problem :
catalog_category_entity_int references a store ‘0’ which doesn’t exist in core_store. I guess the solution is to hand-build a new database without these integrity problems.
Sales: Call 877.832.5289 (N America)|310.295.4144 (International)
