rudolfl Posted June 7, 2017 Share Posted June 7, 2017 Hi all, I run 2.3.3.4 Customer just complained they had an error at checkout. Payment went through, but order did not. Error was as per picture (customer sent screenshot). Yes, I know, PHP warnings should be disabled, but I was doing some fixing lately and left them on. Needless to say, I can not reproduce the issue when going through checkout myself. Any ideas? Thanks, Rudolf Link to comment Share on other sites More sharing options...
mcmannehan Posted June 7, 2017 Share Posted June 7, 2017 that looks like, the header is send two times. Maybe your fixes do the problem. Some Warnings have to consider, because will produced more warnings or erros. The clever one learn from everything and from everybody The normal one learn from his experience The silly one knows everything better [socrates, 412 before Christ] Computers help us with the problems we wouldn't have without them! 99.9% of the bugs sit in front of the computer! My programmed add-ons: WDW EasyTabs 1.0.3, WDW Facebook Like 1.0.0 if(isset($this) || !isset($this)){ // that's the question... Link to comment Share on other sites More sharing options...
rudolfl Posted June 10, 2017 Author Share Posted June 10, 2017 Hi, I think I should be a bit clear in my question, Displaying warnings causes the error, as warning itself considered to be a heading. That is But why would I get a warning like that? Rudolf Link to comment Share on other sites More sharing options...
tgely Posted June 10, 2017 Share Posted June 10, 2017 @rudolfl maybe this help: https://library.oscommerce.com/Online&en&oscom_2_3&release_notes&v2_3_4#upg7 osCommerce based shop owner with minimal design and focused on background works. When the less is more.Email managment with tracking pixel, package managment for shipping, stock management, warehouse managment with bar code reader, parcel shops management on 3000 pickup points without local store. Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.