Empty Admin

[landsknecht]

Well this is funky...

I was going to upgrade my shop to the new version, so I pulled a copy from the server to my local machine to start the process. I've tweaked the config files so it all works. Got the database setup locally and everything else. Here's the thing though, the catalog site is displaying locally great, but the admin is showing what looks like an empty install. I am getting the control panel properly, but there are no products, categories, customers, etc...

And yet, like I said, the catalog is showing everything fine...

Any ideas? Thanks in advance,
Stephen

[DrByte]

the admin is showing what looks like an empty install. I am getting the control panel properly, but there are no products, categories, customers, etc...

sounds like your local install has a default "configure.php" file or is pointing to a default database which has no data.

[landsknecht]

Well, not sure what the heck I was doing wrong... I just tried the good old "Rip it out and try again" method and it works now.

Well, almost. Now on the front page I can browse categories and then sub-categories, but when I get to the product listing level I'm getting an error msg, "1054 Unknown column 'p.products_id' in 'on clause'"

Man, I'm starting to feel like a gimp!

[DrByte]

"1054 Unknown column 'p.products_id' in 'on clause'"

your database isn't up-to-date to match your code

[landsknecht]

Sorry to be a bother Doc, but what does that mean? I've just checked and the db tables match from my local site to my server, so does the code. Yet the server version is working just fine.

Are you refering to the versions of PHP/MySQL? Are there discrepancies there that I'm not seeing?

[DrByte]

p.products_id is a reference to a field in a table.

the error message said the column is not recognized.

that suggests that the table it's trying to query doesn't have the indicated column name/field.

thus, your database structure appears to be not matched to what your code requires

ie: version 1.2.x maybe didn't have said field
but version 1.3.x does
and thus version 1.3.x PHP files are looking for it
but if your database is really v1.2.x (or portions of it are, due to some sort of import, etc), then if you're running v1.3.x code against a v1.2.x database, you'll get the indicated error