Can't Login To Admin/Catalog Page Blank

I've had a 1.3.8a shop running for a few months now. Decided to set up another 1.3.8a store (my admin said I had a current version....). No problem. Then I hit the forums and saw that ZC was up to 1.3.9. Wonder why my admin says 1.3.8a appears to be current. Anyway, spent half the day going through the upgrade procedure on the newest site (not "live" yet). End result was a blank catalog page but I could get into admin. Decided to just delete everything and do a clean install of 1.3.9 instead of trying to troubleshoot the upgrade. End result of that is a blank catalog page and I cannot log in to admin.

So, has anyone else had these problems and solved them? I sure could use some help here. I did run a compare on my newly installed files and the unzipped 1.3.9 files and the only differences were in the configure files (as expected). The database tables look okay (I can see the admin there...just can't log in).

Are you saying you deleted all, carried out a clean install and cannot see the new install's catalogue or log into the admin

1.3.9c is the latest and from 1.3.9a quite a few files have changed

Rob

RobWUK:

Are you saying you deleted all, carried out a clean install and cannot see the new install's catalogue or log into the admin

1.3.9c is the latest and from 1.3.9a quite a few files have changed

Rob

Yes, that's what I did. I deleted all of the files and cleaned out the database, then did a fresh install. I also tried a fresh install with a brand new directory and database. Same result both times. It just isn't working for me for some reason. But 1.3.8a works fine.

Am i correct in thinking it completes the install with no problems, and you are presented with the page to visit the store or goto the admin page?

Rob

RobWUK:

Am i correct in thinking it completes the install with no problems, and you are presented with the page to visit the store or goto the admin page?

Rob

Correct. It installs successfully (in a manner of speaking). And I can see the login page for admin. It also will send me a new password for admin. But it stays in the login loop even with the new password.

ive PMd you

Rob

Progress. Figured out how to get into admin. The problem was that I had two catalogs on the same domain so if I was logged in to one of them I was not able to get into the other one. I'm guessing it is a cookie issue but all I know is that if I close the browser and reopen it, I can log in to one or the other of the sites, just not both of them.

Still have a blank catalog page though. Any help on that one would be appreciated.

Here is what my debug log says when I try to access the catalog index page and get a blank page. What should I do to fix this?

[03-Jun-2010 18:54:07] PHP Warning: main(includes/languages//index.php) [<a href='function.main'>function.main</a>]: failed to open stream: No such file or directory in /[path to]/index.php on line 48
[03-Jun-2010 18:54:07] PHP Fatal error: main() [<a href='function.require'>function.require</a>]: Failed opening required 'includes/languages//index.php' (include_path='') in /[path to]/index.php on line 48

Line 48 is:

require($language_page_directory . $current_page . '.php');

Just out of curiosity, does the line below look right? The double slashes are what look odd to me, but maybe it's supposed to be that way? It's from the debug message (see above).

main(includes/languages//index.php)

You are showing two slashes in the paths for the filenames ...

Check your configure.php files in:
/includes/configure.php
/admin/includes/configure.php

and ensure that you do not have trailing slashes or extra slashes in your settings ...

Also, about your issue of not being able to log into more than one Admin at a time sounds like a Session/cache problem. You might try downloading and running the fix_cache_key.php

I have 4 sites on one domain, and I can log into all of them at the same time.......1 browser, 4 tabs.

Ajeh:

You are showing two slashes in the paths for the filenames ...

Check your configure.php files in:
/includes/configure.php
/admin/includes/configure.php

and ensure that you do not have trailing slashes or extra slashes in your settings ...

Thank you for responding. I appreciate it.

The configure files (catalog and admin) were created by the install script and have trailing slashes in places. They look the same as the configure files that work with 1.3.8a and I note that the admin side (with the slashes in the admin configure file) works. It's just the catalog side that doesn't work. Also, note that in the comments on the catalog configure file it says:
// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!

So, I'm still at a loss. If you think one of the paths in the catalog configure file should omit the trailing slash, which one would it be? My thought was that some call in some other file was inserting the extra slash but I haven't been able to figure out what file/call that is yet.

Get Em Fast:

Also, about your issue of not being able to log into more than one Admin at a time sounds like a Session/cache problem. You might try downloading and running the fix_cache_key.php

I have 4 sites on one domain, and I can log into all of them at the same time.......1 browser, 4 tabs.

What cache settings are you using?

BadDog1369:

What cache settings are you using?

Also, I'm thinking it might be easier to just compare the database settings with the configure files (which I would think would be the same) rather than loading and running (then deleting) the fix_cache_key.php file, especially since I did not change servers or move the site from one directory to another. I just have a 1.3.8a install in one directory and a new 1.3.9 install and a totally separate database in another directory, and they have separate databases. Would you agree or am I missing something?

BadDog1369:

What cache settings are you using?

Cache settings?.......I Don't do anything. I've always run more than one site, and always end up logging into more than one at a time, here and there.

BadDog1369:

Also, I'm thinking it might be easier to just compare the database settings with the configure files (which I would think would be the same) rather than loading and running (then deleting) the fix_cache_key.php file, especially since I did not change servers or move the site from one directory to another. I just have a 1.3.8a install in one directory and a new 1.3.9 install and a totally separate database in another directory, and they have separate databases. Would you agree or am I missing something?

Well, I know you didn't move or upgrade, or anything, but apparently SOMETHING is keeping you from logging into both sites at once. And I know that there's times when a person wants to compare something such as a setting, so that's got to be a big pain, having to log out of one, just to log into the other, right? So, I didn't figure it would hurt......may not help, but, it takes a minute or less to get it, send it, run it, delete.

Could be cookies, cache on your pc even. Hope you find it, though, as you shouldn't have to do anything special to log into more than one site at a time.

Get Em Fast:

Cache settings?.......I Don't do anything. I've always run more than one site, and always end up logging into more than one at a time, here and there.

In your admin/includes/configure.php what do you have in this line?

define('SQL_CACHE_METHOD'

You can select none, database, or file and I think the default is none.

Also, what browser are you using?

Could you post, from the server, without showing your username/passwords, the files:
/includes/configure.php
/admin/includes/configure.php

NOTE: if you have changed your /admin directory to another name, it is a good idea to change it for this posting so no one knows what that "secret" Admin Directory name is ... :smile:

Ajeh:

Could you post, from the server, without showing your username/passwords, the files:
/includes/configure.php
/admin/includes/configure.php

NOTE: if you have changed your /admin directory to another name, it is a good idea to change it for this posting so no one knows what that "secret" Admin Directory name is ... :smile:

Linda,
Thanks for looking at this, but the truth is I have given up on it for now. For what it's worth, I'm almost 100% sure the problem was not in the configure files for the following reasons:

1. The files were the stock files as modified by the install script.
2. They had the same path format as the configure files that were working in the 1.3.8 installs I have (two of them).
3. I've been working with osC for years and am pretty comfortable with the code....and the configure files looked fine to me.

If the problem was the double slash, I'm almost certain it was being added by another file that is operative in 1.3.9 but not 1.3.8.

Do you know offhand if the server requirements for 1.3.9 are different from those of 1.3.8? Since my Admin side was working, I guess I assumed the catalog side should work too....and that the server setup was not the issue. I also looked at the htaccess files added by 1.3.9 and didn't see anything offhand that looked like it might be a problem, but I'm not as sure about that as I am about the configure files being okay.

If you think you can help me troubleshoot it, I'd be happy to reinstall 1.3.9 perhaps later today to take another shot at it. In the meantime, I've refocused my efforts on getting the 1.3.8 install (the second one) ready to roll out live after giving up on 1.3.9. If I could figure out why 1.3.9 doesn't work for me, I can always upgrade the 1.3.8 install later (I did that once and it didn't work, which is why I did a clean install only to find out that didn't work either).

Can always give it a shot ... :smile:

Download the current version of Zen Cart, as there was a new release posted, and try installing in a test directory with a test database and let's see where we can go from there ...

BadDog1369:

In your admin/includes/configure.php what do you have in this line?

define('SQL_CACHE_METHOD'

You can select none, database, or file and I think the default is none.

Also, what browser are you using?

O.k. I see what you're asking now. I use the defaulted "none".
The browser..........ALWAYS FireFox for my default browser. Then I'll use the nasty ole' IE ONLY to test with.

OT. Your avitar is all wrong.......Name of Baddog, with a cute little "cuddly" teddy bear? Where's the Pitt Bull or Rot?

I am also having this issue. I am messing around with an upgraded 1.3.9d version of my site that is 1.3.8a. I went thru the upgrade copying over versions of my configure.php pointing to my new db and path on the server, go to my admin page and it loops trying to login with 1 browser (IE). If I open another browser(FF), then I can login to my new site but if I go to my old site admin page, login, then try to go back to my new site, back to the loop issue.

What can I provide or check out to assist in this?

Thanks!