![]() data analysts, programmers, etc.īut there's no doubt, even before I added a contribution, I was getting 1062 duplicate error messages. Well, I have read SO many articles that say sessions should be INT and auto incremented. if you get duplicate entries then your table is either not cleared, you are generating session id's like wildfire and thus increasing the chances of session id collision or for some other reason you are trying to insert the same session id (instead of updating the existing one). With random session id's (alphanumeric or even plain numeric) that is not such a straightforward issue.Īnd Mark is correct, you are eliminating symptoms not the root cause. If I go to your store with cookies disabled and get session id 2345 in my url's then chances are pretty high that if I alter that to 2344 I get the information from the previous customer. And it solved all my problems.įirst of all, I am not sure those sessions will still function but even if they do it is now so much easier to guess an active session id in use by somebody else. But I'm leaving my sesskey as INT auto incremented becaused based on my research, it's the right thing to do. I mean, there's a loophole in things where you can physically type in checkout_success.php into your browser and never even enter your credit card information, and your order goes through. I mean, there are imaginable scenarios in everything we do. I would like to know more about troubleshooting this error, but I'm afraid I dont' know where to start. ![]() My problem is just that when I set products to special I recieve the error once then it goes away until I set another product to special. My site is working right now, so I don't feel like I have to put it at risk. Don't you think that, regardless of the results of the fix you propose, you are opening up a potential security risk with it? I have to admit that I don't know enough to be able to say one way or another. I appreciate your working on a solution to this, but I have to say that Enigma's comment seems quite relevant. Problems solved, and no more problems arise. Set it to int(32) and set it to auto-increment. the more I've researched, the more I've come up with the fact that you should just go into your phpmyadmin, and change the value of your sesskey in the sessions table to INT, not VarChar. You can truncate table sessions when there are no customers online, but really. ![]() Just fix the sesskey and you're good to go! This was a simple fix that you wouldn't even need to change any of the values for your test runs. Somehow during configuration, the sessions table probably wasn't configured to autoincrement. If I am correct, OsCommerce creates sessions id for every visit to your website, in case a visitor has cookies disabled. This is a mistake! Change the type to INT, the length/values should stay at 32.ĥ) Scroll all the way across to where you see extras and select AUTOINCREMENT from the drop down box.Īll 1062 Duplicate Enty errors will not be resolved. I was having this error everytime I selected create_account, or wishlist_help.ġ) Go to your phpmyadmin, and select the sessions tableĤ) It's probably set at the OSC default, which is varchar(32). ![]() I kept having a duplicate error report for sessions. ![]() The Problem - Duplicate Entry 1062 Errors: Everybody seems to get these, eventually, but very few people post about 'em in here. It's the ol' 1062 Duplicate Entry error, and I have a fix for all. I've researched this to the hilt, and I want to post a fix to the error I've been getting all along, which I've finally put an end to. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |