I'm 90% certain it's part of the bug we're still working on.
Printable View
I'm 90% certain it's part of the bug we're still working on.
I have uploaded the new 1.5.5 beta copied the new files to a test file set and used the zc_install.
The result is what cen be seen by the screen captures I made.
It tells that the db was correctly updated to 1.5.3 but then it says I need to update it because I am on 1.5.2!
kind of confusing and no way to proceed with the upgrade.
Please help if possible.
ThanksAttachment 16045Attachment 16046
It's very possible that you've triggered a database error during the upgrade. Look in the /logs/ folder for zcInstall-DEBUG.log files, to find out the details.Quote:
Originally Posted by enzo-ita
Dreaded Admin SuperUserName/Password after db update error.
Install 1.5.5 in subfolder of our sandbox domain which is on a different server/same host.
1st run, all looked good except no access to Admin after completion. Admin configure created, but zero contents (empty file).
2nd run of zc-install, all functioned as expected. Looks fine with demo data.
Drop all db tables
Import backup 1.5.4 database
Run zc_install as Upgrade. Don't remember any errors.
Attempt admin login using 1.5.4 superuser credentials. No good.
Used this https://www.zen-cart.com/content.php...28i-lost-it%29
AND that worked. Admin access using Admin/admin.
However, none of the admin logins from the imported database will function.
Sandbox: MariaDB 10.0.23/mySQL5.5.5
Live: mySQL 5.6.29
PHP both servers: 5.5.30
i have found a small bug in v1.5.4 which seems to carry over to v1.5.5. not sure if it is worthy of a fix, but i thought i would share it.
in includes/init_includes/init_sanitize.php, on line 72, there is an unset($GLOBALS[$key]).
if someone tries passing over a "db" variable in the URL, it would unset the $db and then zen-cart would generate some error logs, as now one could no longer access the database.
perhaps the dev team is already aware of this behavior, and chosen to do nothing about it. perhaps it has already been covered in the forums before (and if so, i do apologize). perhaps it might be worth wild to have a white-list of variables that can not be manipulated by GET variables. i'm not really sure what the way to go would be...
best.
Are you still working on this?Quote:
Originally Posted by DrByte
The reason for asking is that I've just downloaded a fresh .zip from github, and I've *not* been able to reproduce
lucidlee's error/problem.
This suggests that the problem, if with the zencart/ozpost code was ok on Jan3rd (my previous install date), then got busted with the version lucidlee downloaded, and has been fixed again with the most recent update (Feb 15)
OR, if this isn't the case, then lucidlee still has a problem specific to lucidee,
So, I thought I should ask before going any further.
Cheers
RodG
still working on it
includes/modules/payment/paypal.php
Should not this function be get_error like all the other payment modules? I don't find anything using it.PHP Code:/**
* Used to display error message details
*
* @return boolean
*/
function output_error() {
return false;
}
Could more use be made of the new HTML5 types in input forms? e.g. type="email", type="tel", type="number", etc.
This would make an enormous difference to users on phones and would compliment the new responsive theme. On the iPhone (at least) these type settings cause a modified keyboard to display which makes it easier to enter email addresses, phone numbers and numbers respectively.
Sorry if this is a feature request and not a bug report.
Andy
v155 does this alreadyQuote:
Originally Posted by amayze