I'm upgrading from 1.5.2 to 1.5.3. When I go to upgrade the db, I'm getting 'Admin Password required to proceed with upgrade'. To reset the admin password, to be sure I was using the right one, but get the same error.
I'm upgrading from 1.5.2 to 1.5.3. When I go to upgrade the db, I'm getting 'Admin Password required to proceed with upgrade'. To reset the admin password, to be sure I was using the right one, but get the same error.
I reset the admin password via phpMyAdmin and then was able to proceed with the db upgrade. Not sure what the original issue was.
The same problem when upgrading from 1.5.1 to 1.5.3.
It keeps asking the admin password even if I surely give it correctly. Refuses to patch the db because of that.
The site also has an annoying red warning about the db needing patching…
We've identified a bug with that password validation specific to v1.5.3. We're working on a fix.
Fix posted at: http://www.zen-cart.com/showthread.p...44#post1253144
Thanks DrByte,
now it accepts the password but the next page is BLANK and the logs has this Fatal Error:
PHP Fatal error: require_once(): Failed opening required '/home/myserverspace123/public_html/shop/../includes/classes/vendors/password_compat-master/lib/password.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/myserverspace123/public_html/shop/includes/classes/class.zcPassword.php on line 52
I am running the update from 1.5.1 to 1.5.3 in a test store prior to doing his live one.
got this message, applied the "password fix", yes I started out with the download from the Sourceforge page. I can now use the password to access admi but...now I get a whie page with this error:
PHP Fatal error: Class 'zcPassword' not found in /home/server/public_html/teststore/includes/functions/password_funcs.php on line 15
that code from 11-17:
// //
// This function validates a plain text password with an encrpyted password
function zen_validate_password($plain, $encrypted, $userRef = NULL)
{
$zcPassword = zcPassword::getInstance(PHP_VERSION); <----this is the line
return $zcPassword->validatePassword($plain, $encrypted);
}
what do I do now, it was working last night.
I have the same exact error. :)Quote:
Originally Posted by ellivir
DarkAngel, the "password fix" is only for the installer. It has nothing to do with the Admin side, so if you're seeing errors trying to log into the Admin, then that makes me wonder if you've removed files from the server.Quote:
Originally Posted by DarkAngel
I know I haven't removed any files from catalog or admin side, but I'm still getting a white screen instead of the database being upgraded.
edited to add: The white screen in during the database upgrade. I get to the screen where you enter your login information at the bottom. I put in my username and password and hit the button to continue and it goes to a white screen.
laurelsstitchery, my last post was directed at DarkAngel, not you. I'm pretty sure your situations are different.
Quote:
Originally Posted by ellivir
ellivir and laurelsstitchery,Quote:
Originally Posted by laurelsstitchery
Just double-checking ... what PHP version are you using?
I'm on 5.4.30 :)
Puzzling.Quote:
Originally Posted by laurelsstitchery
Ajeh and I have tested on 5.3.10 and 5.4.30 and 5.5.7 and had no problems with it. Hmmmm...
Granted, I think our configure.php files are all built with v1.5.3, not copied from older versions.
If I went ahead and ran the SQL files via the patch installer in admin, would it work?
I guess if the whole thing imploded, it's not a huge deal because this is just a test site on my new host's server.
no i did not remove any either but...it seems that although super orders is great in 1.5.1 and lower, it does not place nice with 1.5.3
It has a file that when it is on the server the admin will let you log in but then gives you a totally white page
so I removed the file and was able to get back the admin section.
I also noticed that it worked to edit the files in 1.5.1 but this version has different coding so it choked up.
Hope the mod creators for ty tracker, superorders and edit orders get their packages updated with 1.5.3 code
Well, doing the patches via the SQL installer in admin didn't work either. Back to the drawing board.
This is off-topic for this thread I guess, but tell me if this will work:
1. Downgrade to PHP 5.2 on new host
2. Install ZC 1.5.1 on new host
3. Backup database (1.5.1) on old host
4. Import old database to new host
5. Upgrade ZC to 1.5.3
6. Upgrade PHP back to 5.4.30
I can't figure out another way to do it and have everything work.
Your upgrade issue is not an issue with PHP 5.4
No I understand that, but I was under the impression that ZC 1.5.1 didn't work with PHP 5.4 without some patching. If it does work with 5.4, then great!
No, v1.5.3 will work fine with PHP 5.4
Ok great! Thanks! :)Quote:
Originally Posted by DrByte
Looks like I'm seeing the same or similar issue. When attempting a database update from 1.5.1 to 1.5.2 + 1.5.3 I'm getting this in the logs
[20-Jul-2014 19:40:49 America/Los_Angeles] PHP Warning: require_once(C:/Web/../includes/classes/vendors/password_compat-master/lib/password.php): failed to open stream: No such file or directory in C:\Web\includes\classes\class.zcPassword.php on line 52
[20-Jul-2014 19:40:49 America/Los_Angeles] PHP Fatal error: require_once(): Failed opening required 'C:/Web/../includes/classes/vendors/password_compat-master/lib/password.php' (include_path='.;C:\php\pear') in C:\Web\includes\classes\class.zcPassword.php on line 52
I'm working on a local version of my site (laptop running windows 8 . 1.5.1 was working fine. Did the file merge and the site appears to function, but tells me the database is behind. When running the zc_install database only option, when clicking upgrade now, it goes to a general error, 500 if my memory is correct.
PHP Version = 5.4.24, running on Windows 8 localhost
Anything to check next?
I was having the exact same problem upgrading from 1.5.1 to 1.5.3. Finally I had to pay a web developer to completely uninstall 1.5.1 and then install 1.5.3 It cost me a few dollars but was well worth it to save me the aggravation.Quote:
Originally Posted by jeking
I have following info about the server:Quote:
Originally Posted by DrByte
PHP Version: 5.4.28 (Zend: 2.4.0)
Database: MySQL 5.5.36-cll
Server OS: Linux
HTTP Server: Apache
Quote:
Originally Posted by doitwithlife
I had the same issue, in class.zcPassword.php the DIR_WS_CLASSES that is supposed to be "includes/classes" has turned into "../includes/classes/" therefore the path is no longer valid, see the error log
"C:/Web/../includes/classes/vendors/password_compat-master/lib/password.php"
note the "../" is causing the problem
Below is just a quick fix to get it through, in "includes/classes/class.zcPassword.php" change the following
require_once (DIR_FS_CATALOG . "includes/classes/" . 'vendors/password_compat-master/lib/password.php');
// require_once (DIR_FS_CATALOG . DIR_WS_CLASSES . 'vendors/password_compat-master/lib/password.php');
Hope this helps.
the "../" is causing the problem. Check my previous post for a quick fix.Quote:
Originally Posted by ellivir
As soon as our time permits we will.. I'm sure you understand that PAYING work, family, vacations, etc. is a higher priority.. (for me at least)Quote:
Originally Posted by DarkAngel
Quote:
Originally Posted by DivaVocals
you go girl, thae grand mistress of multitasking...LOL
I totally understand and am waiting on the update. This would have been a paying gig for me too tis why I did atest store using 1.5.3 vs the live 1.5.1 store.
ah well...thanks sweety for all you mod creators/editors do for us.
For those of you getting the file-not-found issue, what is your DIR_FS_CATALOG defined to in your /includes/configure.php file?
Quote:
Originally Posted by DrByte
This is what I have in my configure.php file
define('DIR_FS_CATALOG', 'C:/Web/');
As this is a local version of my site, living on my laptop it seems correct and is the directory where the site lives
Thanks to those of you developing this software during your endless free time :)
It's in the style likeQuote:
Originally Posted by DrByte
/home/myserverspace123/public_html/shop/
I got mine forward by editing the file class.zcPassword.php as suggested above. Now the db is patched and the shop is working.
Mine is - define('DIR_FS_CATALOG', '/home/server/public_html/catalog/');Quote:
Originally Posted by DrByte
I also used the suggested work around tonight to class.zcPassword.php as suggested above. The store is functional locally, but looking at another issue which most likely is unrelatedQuote:
Originally Posted by loveofthehorse
I hate to beat this dead horse a little more, but is this the official solution for the problem? I've tried a few more times and keep getting the same file-not-found error. I just don't want to break something else by using this workaround. :)Quote:
Originally Posted by mobileg
1. Uploaded the revised general.php file linked by DrByte earlier in this thread
2. Applied the revision to 'includes/classes/class.zcPassword.php' as posted earlier in this thread
Now, I'm getting the same white page after the hit the database upgrade button and this error appears in the logs folder:
"[26-Jul-2014 11:39:00 America/New_York] PHP Fatal error: Call to undefined function password_verify() in /home/laurel34/public_html/catalog/includes/classes/class.zcPassword.php on line 92"
So, I undid #2 from above and tried the database upgrade again. Again with the white screen, but no error log this time. I'm about to rip my hair out. Please tell me what to do to get this database upgraded. Please I beg of someone!
Actually, I did get an error log on try #2:Quote:
Originally Posted by laurelsstitchery
"[26-Jul-2014 11:47:12 America/New_York] PHP Warning: require_once(/home/laurel34/public_html/catalog/../includes/classes/vendors/password_compat-master/lib/password.php): failed to open stream: No such file or directory in /home/laurel34/public_html/catalog/includes/classes/class.zcPassword.php on line 52
[26-Jul-2014 11:47:12 America/New_York] PHP Fatal error: require_once(): Failed opening required '/home/laurel34/public_html/catalog/../includes/classes/vendors/password_compat-master/lib/password.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/laurel34/public_html/catalog/includes/classes/class.zcPassword.php on line 52"
And I got it to work finally. THanks! :)Quote:
Originally Posted by laurelsstitchery
doing what??? Might help others if you post what YOU did..Quote:
Originally Posted by laurelsstitchery
Yes! Sorry I meant to include that. When I read through the 'includes/classes/class.zcPassword.php' patch posted earlier in the thread, I thought (and this is what I get for thinking) that it meant to comment out that line, but after going back and reading it another 100 times, I realized that I was meant to comment out that line and paste in the other line. Like I said, too much thinking gets me in trouble. I'm all upgraded and testing now. Thanks for all the help! :)Quote:
Originally Posted by DivaVocals
HI,
I am currently experiencing the same problem. it is no doubt related to the following line of code:
define('DIR_WS_INCLUDES', '../includes/');
which is line 39 in:
zc_install/includes/modules/pages/database_upgrade/header_php.php
now, why this only fails on the the class.zcPassword class and not on other classes, well you got me.
not really sure why this would get redefined here.
Humans.. not infallible.. probably a typo..Quote:
Originally Posted by carlwhat
i'm not sure it's a typo, although it very may well be...Quote:
Originally Posted by DivaVocals
it exists in the upgrade to v1.5.1 as well; and it's curious that the zcPassword class (which i believe is new) is the only class that is failing.
I just did an install of 1.5.3 yesterday using the original download package adding the zip patch to be able to use the admin password of the databaase to be upgraded and did not have any problems with the upgrade the database aspect of the process. I do not know if there was a difference in the files of the original package plus the zip file and the current package. I did see as I was reconstructing the site that there was a plugin installed (master password) that modified some of the area discussed above.
This leads me to ask in relation to the attempted "upgrade" how vanilla is/was the install/upgrade on which difficulty has been found?
After reading all this thread I found I couldn't find a solution to the problem in ZC_install to upgrade my v151 db, to the current v153 ... I've done everything, from repatching the general.php function as suggested by DrByte in the thread, to wipe out completely the admin password and enter a single '1' ... using 'MQ==' a base64 encode in the db ... Nothing works, I am getting the same error,>>> ' Admin Password required to proceed with upgrade more info ... '
BTW here's my Info
Server Name host
cPanel Version 11.42.1 (build 24)
Apache version 2.2.23
PHP version 5.2.17
MySQL version 5.1.73-cll
Architecture i686
Operating system linux
Any ideas?
Should I wipeout the whole thing and start over?
Other than a recently identified paypal mod, if you have downloaded thelatest 1.5.3, the zc_install should present you with the ability to upgrade when that option is selected. Be sure that the username and password is the associated information from the old database. You said this was a vanilla install, correct?Quote:
Originally Posted by icecold
Correct vanilla install, nothing more than a single module, and 2 templates with their modules ...Quote:
Originally Posted by mc12345678
I hope the password script validation uses Encode base 64 otherwise I need to encode 1 into whatever encoder ZC uses ...
BTW I used PHPmyAdmin for that ...
ok I just RESET my Password created a new one and same thing .... :huh:
So are you saying that you had some sort of additional password encrypter using the earlier zC version? If that's the case, then thatshould be incorporated to your upgrade process and new cart. The install is expecting the password to exist as it normally is in ZC. The other option I would think would be to use the default "admin" password for resetting the password.Quote:
Originally Posted by icecold
Did you try the suggested fix posted in THIS thread???????Quote:
Originally Posted by icecold
I did and it didn't work even with my new password, and just in case the upgraded fix ... so I wiped out everything ... and started from scratch, no big deal as it's less time, just to delete everything and start fresh, for a demo store without any products, and just one template and 1 contribution, it will be live soon ;) ... I hope
Well I just had the chance to watch the Zcpassword.php file and realized it's a completely different algorithm anyways, so I decided to start from scratch, now I have the demo site up and running fine ... Soon will be my new store ...Quote:
Originally Posted by mc12345678
I did the whole testing in a separate directory and had no problems with the database upgrade. But now that I'm in the process of upgrading the database that had been the live DB while I was testing, I ran into the password problem. I uploaded the "fix" but now get a white screen upon upgrading and the database does not upgrade. Seems like I've hit a dead end. Have I missed something here?
Several posts in this thread refer to a " 'includes/classes/class.zcPassword.php' patch" and indicate that "patch" solved the problem. But in reading through this thread, I can't see what is involved in this. There seems to be an off-shoot in this thread that had to do with a problem logging into admin rather than upgrading the DB and maybe I missed the steps to try thinking the suggestion had to do with that.
I'm really frantic at this point because I spent a week working in a test environment and everything was fine. Now I put my client's store into maintenance mode thinking it would only take a half hour or so to do the final steps. But been banging up against a wall for an hour now.
Argh!
Ok, I read through the relevant posts a few more times to understand what to do. I'm putting this here more clearly in case others have the problem too.
This is how to solve the problem when a) the DB upgrade does not accept your password and b) you get a blank screen after replacing the fixed file that DrByte posted.
1. Download the replacement file for zc_install > includes > functions > general.php
2. upload the file above into your zc_install directory on your server
3. Open the file CATALOG/includes/classes/class.zcPassword.php [replace CATALOG with your store directory name]
4. comment out line 52 "require_once (DIR_FS_CATALOG . DIR_WS_CLASSES . 'vendors/password_compat-master/lib/password.php');"
5. add a line below "require_once (DIR_FS_CATALOG . "includes/classes/" . 'vendors/password_compat-master/lib/password.php');" and save to your server
6. run the DB upgrade again
That worked for me and if I'm reading other's posts correctly it worked for a bunch of other folks too.
What I don't know is whether editing that line in the class file will screw up anything else down the line. Perhaps others involved in writing the upgrade and the original files can speak to that. So far I haven't seen any problems occurring with the fix but ???
If you undo the changes you made to class.zcPassword.php after you've done the database upgrade, there will be no problems.Quote:
Originally Posted by earmsby
We're investigating a way to make changes only to zc_install code so that you won't have to touch the class.zcPassword file.
If one of you has a test environment and is willing to test an additional change, I'd be grateful.
(All my testing using PHP 5.2.17, 5.3.28, 5.4.31, 5.5.17 has not been able to recreate the same symptom when using the hotfix I published earlier, but I think the following may help...)
/zc_install/includes/functions/general.php (NOTE: this assumes you're using the updated one I posted earlier in this thread, because there are more changes later in the file that I've not quoted here)
Near the top of the file you'll see these lines. Add the one I've highlighted in red/bold:Code:if (!defined('TABLE_UPGRADE_EXCEPTIONS')) define('TABLE_UPGRADE_EXCEPTIONS','upgrade_exceptions');
if (!defined('DIR_WS_CLASSES')) define('DIR_WS_CLASSES', 'includes/classes/');
require('../includes/classes/class.zcPassword.php');
Hi Dr.Byte,
I have tried your suggested fix as you gave in your above post #59 by adding in the line in red, in the appropriate part of the general.php file. I was previously having the same issue as others where I was getting only a white screen when trying to update my database. After applying this line to the general.php file and then trying to update my database, I check the appropriate database update box, fill in my username and password, and then click the Update Database Now button and it just loops me back to this same page. No errors, no sign of it updating, nothing. I tried it a couple of times just to be sure it wasn't my user error.
My server stats are: Linux
Php version - 5.3.28
My SQL version - 5.5.36-cll
Architecture - x86_64
Hope this helps you to figure something out. Please let me know if you have any questions.
Jeff
One other question Dr. Byte, when updating my database, I am upgrading from zen v.1.5.0 to v.1.5.3 can I check multiple boxes when doing the update....i.e. check the boxes for v.1.5.0 to v.1.5.1 and also v.1.5.1.to v.1.5.2 and v.1.5.2 to v.1.5.3 and then run press the Update Database button or do I have to run it three separate times (choosing the next update each time) to get it updated to the latest version.
When I ran the test in my post #60 I only selected to update database v.1.5.0 to v.1.5.1
Thanks,
Jeff
Hello, I have been using Zen Cart since 2005 and I am in awe of it. Thank you everyone who made it for us to build a DYI website. I have been struggling upgrading from 1.5.0 to 1.5.3. I had all the problems mentioned in this "thread" and more mentioned on others. I would like to post something for everyone to think about.
This happen to be what I overlooked that caused these problems for me: I forgot to delete the "removed" files from each version of 1.5.0 to 1.5.3 (by following the list in the changed_files_*.html docs in the /docs folder). So, read them all; more than once will help a lot.
Once I followed all the instructions it turned out I had deleted the WRONG password_funcs.php file. I did not realize a new on was located in the Includes/Functions Folder. I thought it was the one to delete. Wrong of course. I uploaded that one back in place and deleted the one in Admin/Includes/Functions. Everything works now. Doing my Snoopy Happy Dance now! :lol: So just a little thought if this will help anyone else.
BTW- what was actually occurring here was... No Passwords were accepted, No Password resets would work. I was allowed to login once before I had to use phpmyadmin to set to default.
No, it will do all that are checked, all at once, and only if they're needed.Quote:
Originally Posted by NWCE
In a future version we'll probably remove the checkboxes to minimize confusion since they're not really needed anymore (they were put in a long time back because of the way upgrading used to work, but it's much smoother now in how it handles doing required updates).
I'm upgrading from 1.5.0 to 1.5.3 but I'm stuck in the same password admin problem. Even I replace the zc_install/includes/functions/general.php.
Very frustrating day.
Plus... I added the line 53 at include/classes/class.zcPassword.php but the same result.
Original version of 1.3.x that has been upgraded multiple times over the years, and I am at a point of upgrading 1.5.1 to 1.5.3 and when running zc_install I am unable to get past the admin name and password, the password is being rejected.
Earlier in this thread there was a "patch" and further instructions to alter the patched file more, which I did do but to no avail.
I NEED to get the database updated, is there any other way than through the zc_install method to get the database updated?
What PHP version are you using?Quote:
Originally Posted by zipp99
PHP Version 5.3.3
Yes, me too. Original 1.3.9 site. Running 1.5.1 and attempting to upgrade to 1.5.3, which I didn't expect to be difficult but upgrading the database is impossible. I did have the correct admin password but messed that up with PHPMyAdmin in all my efforts to try to accomplish something... so I guess I'll have to ask the server manager to reload the site from a couple days ago. I really don't even want to attempt this upgrade again, this has been so frustrating. I don't understand why I'm totally locked out of every aspect of the site, the front end, admin and all. It's a pure disaster. Can't you revise your upgrade procedures so this doesn't happen??
My version of PHP is 5.3.27.
The reason why I thought it was time to upgrade is because my customers are getting persistent PayPal errors, the one that says the addresses don't match.
In working this again assuming you are going to start over, you could save yourself the business heartache of the upgrade by first making a working backup of your site, and then stepping through the process on that backup.. if not mistaken that is part of the process of the upgrade. At least as identified here: http://www.zen-cart.com/entry.php?3-...d-of-upgrading.Quote:
Originally Posted by daffy
There is no reason to put the live site in jeopardy of loss or damage.
Also, haven't seen that the store side has necessarily been affected are talking about users are. Unable to login (password authentication) or is it not possible to navigate the store after this attempted upgrade? If it is anything other than a login issue, then something went wrong with the file upgrade/merge process. Have seen sites thaat have upgraded the software but not the database still function, but a banner is displayed indicating that the database needs to be upgraded.
I had full backups. I restored the site to 1.5.1 and reset my admin password. But this would have happened even if I'd built a test site with a test database, because the problem happened at the very final step of the upgrade, when the live database is upgraded. That's where it stalled.
Yes, the front end and back end were all locked out. No matter where I navigated on the site, I got the screen saying congratulations, now click here to finish...
So then I did a clean install of 1.5.3 instead of over-writing 1.5.1, but that didn't make a difference. Apparently I cannot upgrade to 1.5.3. , all because of this admin password issue. To me, this is a really big problem over a very small thing.
I have an apache/linux server. I downloaded the very latest ZC version from Sourceforge.
I have a whole lot of error logs if that's helpful, but the logs seem to consistently point to the same errors that are already mentioned in this thread. I assume the any bugfixes were included in the October file?
Sometimes it seemed like it did accept the password, but then I got a white screen and nothing happened.
I was experimenting with many different variations in the config files. For one thing, the upgrade menu would not come up unless I included the database prefix in the config files, even though the default is to leave it blank. I didn't get the database upgrade option unless the prefix was in there. Also, at the top of the config files where it requests location of the server, I had to put in the urls rather than localhost. But it would not accept anything but localhost in the actual section for the database. So maybe my particular config files messed up the database upgrade? I entered what made the Upgrade menu happy. I had all green lights when I pushed the button to upgrade the database.
For people reading this thread: If you are a developer who has updated someone else's cart on your own machine and uploaded a test database to a different machine, (or you're the storeowner and doing that) be sure different versions of PHP aren't causing you trouble - see my explanation here: http://www.zen-cart.com/showthread.p...11#post1260911
php versions are the same on both the development and the live sites, its actually the same hosting env. So I guess its time to just find a different solution. Take care.
Quote:
Originally Posted by zipp99
To upgrade the database manually you could apply the 2 .sql files from the zc_install folder, using phpMyAdmin. In the case of going from v1.5.1 to 1.5.2 to 1.5.3 it's only .sql changes that are needed. It's not always safe to do just .sql scripts because sometimes there's a need for some php-scripted updates too, and that's why zc_install is provided, so that those things can be taken care of in a way that protects the data.Quote:
Originally Posted by zipp99
PHP 5.3.7 and lower have weak security, so it would be prudent to upgrade your PHP version at some point.
I tried installing 1.5.3 again and this time it looks as if the database is upgraded. I did see a message that the database was up to date.
However, now I can't get into the Admin. I get the page that says, "Hello. Thank you for loading Zen CartŪ. You are seeing this page for one or more reasons: "
I've done the zc_install setup a number of times so that's not it. I've checked the configs and the .htaccess. Just absolutely do not get the Admin login no matter what I try.
My shop has been nonfunctional all week. If I use 1.5.1, people can't checkout with PayPal even though I turned off ALL the address checking features they're still getting the 10736 error.
So I tried the upgrade again (via FTP) and now customers can't even get to checkout - because I can't get into Admin to turn things on and off.
I asked my server manager about upgrading the PHP version. We'll see if that helps.
I'm feeling rather desperate actually. ZenCart has never been this impossible before.
My server manager upgraded PHP to version 5.4
I still can't login to the admin. I think I've run the database upgrade scripts a zillion times now hoping to finish installation but it always goes to this screen in the Admin:
Attachment 14739
Here's an error that showed up in the LOGS folder one of those times. This was before we upgraded the PHP:
I'm totally locked out of the Admin and I've done everything I can think of. Suggestions?Code:[29-Nov-2014 09:29:00 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/prillych/public_html/zc_install/includes/classes/installer.php on line 764
The site is working OK on the frontend, but I can't get into the admin at all. Is there any way to kill that screen?? I REALLY think the install procedure is not working right.
One thing it's doing is changing the permissions on the includes/configure.php to 444 every chance it gets, and THEN it gripes at me that it can't write to the configure.php file even though I'm constantly checking on it to make sure it's writable.
Although the configure.php files say they don't want the prefix in there, the site won't run at all unless the database prefix is in there. --- But I think that might be messing up the installation procedure, it's having a hard time writing to some of the tables. I was trying to do it manually with PHPMyAdmin, and I ended up inserting the prefix into the SQL statements, otherwise it couldn't work on the tables.
I've been using ZenCart for almost 10 years, on several sites, and I do everything myself. So it's not like I'm a newbie. I've always been able to fix things on ZenCart, but this is a real mess.
Most likely the change of the configure.php permissions is being done by the server ...
As to the Install screen, ensure that you have a good configure.php file in the directory:
/admin/configure.php
I suspect that it is either missing or the paths/database are incorrect ...
Could you post the files, from the server, for:
/includes/configure.php
/your_secret_admin_dir/includes/configure.php
without showing your_secret_admin_dir or any passwords ...
THIS is the configure.php file from the secret-admin/includes/ folder:
Code:<?php
/**
* SAMPLE (but NOT FUNCTIONAL) file
*
* @package Configuration Settings
* @package Admin
* @copyright Copyright 2003-2014 Zen Cart Development Team
* @copyright Portions Copyright 2003 osCommerce
* @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
* @version GIT: $Id: Author: DrByte May 24 2014 Modified in v1.5.3 $
* @private
*/
/**
* WE RECOMMEND THAT YOU USE SSL PROTECTION FOR YOUR ENTIRE ADMIN:
* To do that, make sure you use a "https:" URL for BOTH the HTTP_SERVER and HTTPS_SERVER entries:
*/
define('HTTP_SERVER', 'http://www.prillycharmin.com');
define('HTTPS_SERVER', 'http://www.prillycharmin.com');
define('HTTP_CATALOG_SERVER', 'http://www.prillycharmin.com');
define('HTTPS_CATALOG_SERVER', 'http://www.prillycharmin.com');
// secure webserver for admin? Valid choices are 'true' or 'false' (including quotes).
define('ENABLE_SSL_ADMIN', 'false');
// secure webserver for storefront? Valid choices are 'true' or 'false' (including quotes).
define('ENABLE_SSL_CATALOG', 'false');
define('DIR_WS_ADMIN', preg_replace('#^' . str_replace('-', '\-', zen_parse_url(HTTP_SERVER, '/path')) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_ADMIN', preg_replace('#^' . str_replace('-', '\-', zen_parse_url(HTTPS_SERVER, '/path')) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
define('DIR_WS_HTTPS_CATALOG', '/');
// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
define('DIR_WS_CATALOG_IMAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'images/');
define('DIR_WS_CATALOG_TEMPLATE', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/templates/');
define('DIR_WS_INCLUDES', 'includes/');
define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
define('DIR_WS_CATALOG_LANGUAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/languages/');
// * DIR_FS_* = Filesystem directories (local/physical)
define('DIR_FS_ADMIN', preg_replace('#/includes/$#', '/', realpath(dirname(__FILE__) . '/../') . '/'));
define('DIR_FS_CATALOG', '/');
//the following path is a COMPLETE path to the /logs/ folder eg: /var/www/vhost/accountname/public_html/store/logs ... and no trailing slash
define('DIR_FS_LOGS', DIR_FS_CATALOG . '/home/prillych/public_html/logs');
define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
define('DIR_FS_CATALOG_TEMPLATES', DIR_FS_CATALOG . 'includes/templates/');
define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');
define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');
define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
// define our database connection
define('DB_TYPE', 'mysql');
define('DB_PREFIX', 'zen_');
define('DB_CHARSET', 'utf8');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', 'xxxxxx');
define('DB_SERVER_PASSWORD', 'xxxxxx');
define('DB_DATABASE', 'xxxxxx');
// The next 2 "defines" are for SQL cache support.
// For SQL_CACHE_METHOD, you can select from: none, database, or file
// If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
// or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
// ie: /path/to/your/webspace/public_html/zen/cache -- leave no trailing slash
define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', '/home/prillych/public_html/cache');
//Explanations of the webserver and path parameters:
// HTTP_SERVER is your Main webserver: eg-http://www.yourdomain.com
// HTTPS_SERVER is your Secure webserver: eg-https://www.yourdomain.com
// HTTP_CATALOG_SERVER is your Main webserver: eg-http://www.yourdomain.com
// HTTPS_CATALOG_SERVER is your Secure webserver: eg-https://www.yourdomain.com
/*
* URLs for your site will be built via:
* HTTP_SERVER plus DIR_WS_ADMIN or
* HTTPS_SERVER plus DIR_WS_HTTPS_ADMIN or
* HTTP_SERVER plus DIR_WS_CATALOG or
* HTTPS_SERVER plus DIR_WS_HTTPS_CATALOG
* ...depending on your system configuration settings
*/
THIS is the configure.php file from the includes folder:
Code:<?php
/**
* dist-configure.php
*
* @package Configuration Settings circa 1.5.2
* @copyright Copyright 2003-2012 Zen Cart Development Team
* @copyright Portions Copyright 2003 osCommerce
* @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
* @version GIT: $Id: Author: DrByte Wed Nov 6 20:54:59 2013 -0500 Modified in v1.5.2 $
* @private
*/
// Define the webserver and path parameters
// HTTP_SERVER is your Main webserver: eg-http://www.yourdomain.com
// HTTPS_SERVER is your Secure webserver: eg-https://www.yourdomain.com
define('HTTP_SERVER', 'http://www.prillycharmin.com');
define('HTTPS_SERVER', 'http://www.prillycharmin.com');
// Use secure webserver for checkout procedure?
define('ENABLE_SSL', 'false');
// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');
define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_INCLUDES', 'includes/');
define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
define('DIR_WS_DOWNLOAD_PUBLIC', DIR_WS_CATALOG . 'pub/');
define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');
// * DIR_FS_* = Filesystem directories (local/physical)
//the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
define('DIR_FS_CATALOG', '/home/prillych/public_html/');
//the following path is a COMPLETE path to the /logs/ folder eg: /var/www/vhost/accountname/public_html/store/logs ... and no trailing slash
define('DIR_FS_LOGS', DIR_FS_CATALOG . '/home/prillych/public_html/logs');
define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');
define('DIR_WS_UPLOADS', DIR_WS_IMAGES . 'uploads/');
define('DIR_FS_UPLOADS', DIR_FS_CATALOG . DIR_WS_UPLOADS);
define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');
// define our database connection
define('DB_TYPE', 'mysql');
define('DB_PREFIX', 'zen_'); // prefix for database table names -- preferred to be left empty
define('DB_CHARSET', 'utf8');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', 'xxxxxx');
define('DB_SERVER_PASSWORD', 'xxxxxx');
define('DB_DATABASE', 'xxxxxx');
// The next 2 "defines" are for SQL cache support.
// For SQL_CACHE_METHOD, you can select from: none, database, or file
// If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
// or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
// ie: /path/to/your/webspace/public_html/zen/cache -- leave no trailing slash
define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', '/home/prillych/public_html/cache');
In your admin version DIR_FS_CATALOG is incorectly defined. It should be:
Some of the other defines that use that may need be shortened.Code:define('DIR_FS_CATALOG', '/home/prillych/public_html/');
DIR_FS_LOGS in your storeside is wrong (has too much information) should end with . 'logs/'); which I think is also the case on the admin side as well.
Sorry, logs should end without the slash... Misread the guidance in the configure.php file for logs...
Should be the define in both configure.php files.Code:define('DIR_FS_LOGS', DIR_FS_CATALOG . 'logs');
Oh, yes, what a relief that is. I'm in the Admin area at last. THANK YOU!
OK, seem to having the same problem as everybody else, tried replacing the general file as suggested, also amended the zcpassword file too, I ended up with a blank page, with no access to admin or the "front page" of the site then had to wipe out the install & re-install fresh "install" files files.
server details;
Server Host: myserver.net (deliberately hidden ok) Database Host: localhost (127.0.0.1)
Server OS: Linux 2.6.18-471.3.1.el5.lve0.8.72 Database: MySQL 5.5.42-cll
Server Date: 06/04/2015 12:01:42 Database Date: 06/04/2015 12:01:42
Server Up Time: Disabled/Unavailable HTTP Server: Apache
PHP Version: 5.4.28 (Zend: 2.4.0) PHP Memory Limit: 512M PHP Safe Mode: Off
PHP File Uploads: On Max Size: 32M POST Max Size: 32M
Database Data Size: 8,313 kB Database Index Size: 2,097 kB
Zen Cart 1.5.4
Database Patch Level: 1.5.1
v1.5.1 [2013-07-12 12:02:27] (Version Update 1.5.0->1.5.1)
v1.5.0 [2013-07-12 12:02:27] (Version Update 1.3.9->1.5.0)
v1.3.9c [2010-05-27 19:12:07] (Fresh Installation)
why is my install now showing that it has 2 zencart versions? why is the install steps showing that i should "upgrade" from 1.5.1 to 1.5.2 & 1.5.3 to 1.5.4 as well? what's my best course of action? should i start again with a fresh install & them simply use mysql to download the current product list, customer list, & upload that to the fresh 1.5.4 install. any advice would be great, love zencart, but sometimes it's a head scratcher....
also tried the following https://www.zen-cart.com/showthread....05#post1266905 same result:
Admin Password required to proceed with upgrade more info...
No, you appear to be having a similar problem to number of other people. This is a far cry than having the *same* problem as anyone else, and I can assure you that it isn't *everyone else* that is even having or had this problem.Quote:
Originally Posted by voluntaryist.only
Knowing and understanding this is one of the 1st things to realise when seeking a solution.
We need to get to some common ground here.Quote:
Originally Posted by voluntaryist.only
Did you get the blank page after replacing the general file, after 'ammending' the zcpassword, or did you do both of these at the same time. If the latter, then you need to undo one of the other just to get back to the original problem. You may have 'fixed' this issue with one of these changes, and broken it in a different way with the other change.
Rule#1. Only make ONE change at a time. If it doesn't have the desired effect, revert back before changing something else. If you don't do this you'll just be adding one problem on top of another with the end result that no one will be able to guide you back to 'common ground' and you'll probably eventually resort to trying a complete new install as the inevitable result.
changing, testing, changing back, then repeating this process is the only way to not get lost.
Told ya so. <g>Quote:
Originally Posted by voluntaryist.only
Now here's a cruncher - if this truly is/was a *fresh* install then you most certainly wouldn't be having the exact same problem as you were previously having, unless of course you somehow have some corrupted files that you re-uploaded, in which case it still isn't really a 'fresh' install, it is only a resinstall of something already broken, which will explain the same problem carrying over from the old to the new.
Although this (probably) really isn't important at all, I always end up asking myself WHY have you hidden this. Does it serve any useful purpose from keeping this a secret? What about the possibility that we may know of a certain host that has a certain specific issue and your host just happens to be the one in question?Quote:
Originally Posted by voluntaryist.only
Which will be easier to solve, us providing you with an extensive list of hosts for you to say 'yes' or 'no' I'm not using them, or for you to simply tell us in the 1st place.
I seriously don't believe that you problem IS a host related issue, but the point is, the more information that you can provide, the better position we are in to help you.
What *other* information do you have that you have 'deliberately hidden'? May be nothing at all. It may be the one vital clue we need. This isn't really a judgement call for you to make unless you know what is actually causing the problem, in which case you wouldn't be needing to seek help in the 1st place.
It isn't.Quote:
Originally Posted by voluntaryist.only
What this is showing is that your system files are from ZenCart 1.5.4 but your database is still at V1.5.1 (in other words, you haven't yet ran the sql upgrade script for v1.5.4
If I assume that you are referring to the patch level steps above (as opposed to the 'install' steps when installing or upgrading zencart itself) the info above is telling us that you 1st installed zencart 1.3.9c as a fresh install back in 2010, this was then updated to v1.5.1 in July 2013 (skipping V1.5.0) and that the 1.5.0 and v1.5.1 patches were both performed at the same time. This is pretty much par for the course, and I see nothing amiss here, other than your current install (V1.5.4) still needs the v1.5.4 upgrade SQL script to be run.Quote:
Originally Posted by voluntaryist.only
Run the SQL upgrade script to bring the database in line with the files.Quote:
Originally Posted by voluntaryist.only
No, that won't work.. in fact based on those patch level entries you may even have already done this once already.Quote:
Originally Posted by voluntaryist.only
If we assume you really DID do a 'fresh install' as you stated (and we've no reason to doubt this), this fresh/new install was done with the V1.5.4 fileset, which being a new/fresh install would have wiped out the current database, and the patch level entry would read something like
v1.5.4 [2015-06-05 19:12:07] (Fresh Installation) - with no other entries. Now, if after this you copied the old database across to this new install, the database will be back to how it was prior to your 'fresh install' - In other words, your database will show *exactly* what it is showing us here:
Zen Cart 1.5.4
Database Patch Level: 1.5.1
v1.5.1 [2013-07-12 12:02:27] (Version Update 1.5.0->1.5.1)
v1.5.0 [2013-07-12 12:02:27] (Version Update 1.3.9->1.5.0)
v1.3.9c [2010-05-27 19:12:07] (Fresh Installation)
You'll find that after you run the v1.5.4 sql upgrade script on the currently installed database, these entries will read like
Zen Cart 1.5.4
Database Patch Level: 1.5.4
v1.5.4 [2015-06-05 12:02:27] (Version Update 1.5.1->1.5.4)
v1.5.1 [2013-07-12 12:02:27] (Version Update 1.5.0->1.5.1)
v1.5.0 [2013-07-12 12:02:27] (Version Update 1.3.9->1.5.0)
v1.3.9c [2010-05-27 19:12:07] (Fresh Installation)
Hopefully you can see that these entries are showing an upgrade history, not things that need to be done in the future.
Anyway, bottom line, your database and files are 'out of sync', and until this is rectified it is a waste of time looking into other causes, problems, or solutions because this kind of mismatch can give very unpredictable results.
Cheers
RodG