that error means the entire DB is down,
OR your config files are hashed
that error means the entire DB is down,
OR your config files are hashed
Zen cart PCI compliant Hosting
Thanks for the immediate response!
(I am presently very grateful for good tech support at my hosting company, too -- cause I got this fixed now.)
In my case:
they said:
"
We have not changed anything on the server. However, if you use 'localhost' in your scripts to connect to the database, it uses a socket. The socket breaks sometimes, and using '127.0.0.1' instead is more reliable, if a bit slower.
Please check if setting the database server to 127.0.0.1 solves the connection problem.
P.S. I have fixed the socket now, but I have no idea when it will go down again... 127.0.0.1 is by far more reliable.
"
So I just changed "localhost" to "127.0.0.1" in each of the "configure.php" files, and voila! I'm back online with the database.
Don't know if this will fix others' situations or not (and I'm assuming in any case you need to get your correct number from your host company -- not just use 127.0.0.1).
dustin
ungeziefer,
I will try to answer your question in a simple manner;
When you create a DB it is an empty container...with nothing defined as to structure i.e. tables...
Running the install moves the mysql structure and base data to the empty DB.
To prevent having to start with an empty DB (no products or settings), you should reguarly create a backup of your working DB. Then if there is a problem you can restore the backup to the DB and only be missing the transactions since the last backup.
Hope this assists
Zen-Venom Get Bitten
O.K. -- I'm SLOWLY getting it ...
So after I re-import my old (exported) database into the new one, I have to re-run the "installer" but click on "upgrade" rather than "install" -- is that correct?
And if/when I do this, it will not destroy all my ZenCart customizations, I trust?
Thank you.
dustin
The DATABASE only contains your data, the information about your products, orders and settings you made by using the Admin.
The FILES contain the code that actually controls the way the program runs and the way it looks.
The 2 pieces work together to build a dynamic, interactive shopping cart.
When doing an upgrade you have to upgrade both pieces to keep them in synch with each other.
Please do not PM for support issues: a private solution doesn't benefit the community.
Be careful with unsolicited advice via email or PM - Make sure the person you are talking to is a reliable source.
I don't mean to be flippant, but isn't that EVERYTHING?
I just tried to do a re-import of my old database into my new one, and my entire store -- EVERYTHING -- is gone. (Hopefully I will be able to restore it somehow ... I'm giving up on salvaging my old database -- I'm just going to start over [again] with a brand new one.)
I am too angry to be writing now. I am going to stop.
I think I'm doing everything right -- following these instructions for database export/import, etc.
I'm using a test site now, to be safe. When I go to "upgrade," it says:
"Database Information -- Upgrade Sniffer predicts: *** No upgrade required ***"
I click the "upgrade" button anyway, but nothing really happens -- my inventory is still nonexistant.
(Probably this is not the right thread for this -- but in the event that you can help me out, kobra, I would greatly appreciate it.)
Thanks,
dustin
This thing is like a commond cold or something. I've caught it.
When I try to go to admin I get this error.
0 DB_ERROR_NOT_CONNECTED
in:
[db_cache table]
Database is there and working for the store.
public_html/includes/configure.php is there, and the store comes up fine is there and I can open it edit it etc.
I tried changing local host to 127.0.0.1, also tried changing it to the shared ip number that the domain points too. problem still exist.
but I can't get into admin.
db_cache is empty,
Now someone said that the config files maybe hashed, but they are there. Do I replace them anyway?
Should I reinstall my db from backup, even though the store is working, it's just admin that isn't.
Thanks!
HA! I figured it out.
When I moved I changed the db users password, and of course changed it in /public_html/includes/configure.php
I didn't realize that admin had it's own configure.php file. Once I went a digging I found that file in /public_html/admin/includes/configure.php. changed the password in there, and boom I'm in.
Damn I'm getting good. haha.