Jump to content

ugottasalsa

Members
  • Content count

    725
  • Joined

  • Last visited

1 Follower

Profile Information

  1. Hey there Josh, I went to the PWA forum but really couldn't find a whole lot and didn't really want to go seaching through so many pages of posts. Your problem basically comes down to session information. The customers PWA session info is killed just before checkout_success.php is run. I gave you some ideas in my last post... Did you try any of them? Because this functionality does not currently exist, you will either have to be creative in finding a solution, or pay someone to do it for you. Let me know if I can help any further. -R
  2. Hey all, I know its been awhile, but let me jump in... here's what I see the problem with using osCPrintOrder with PWA... With PWA, the customer never "logs in". The customers PWA session is killed when checkout_process.php is run. This means that when the customer reaches the Checkout_success, there is no customer infomation to be queried, and consequently, no way for osC to know the order info at that point. The idea of PWA is the customers no longer have access to their order info once they reach checkout_success.php. Since they haven't created an account, there is no way for them to login to view information. In fact, that is what it states when the choice is given to either login, register or PWA. Basically, PWA is only good during Checkout, after that, the customer no longer has access to order info. Now, there are a couple of ways around it, BUT... you could be looking at security issues. Instead of querying the customer info to get the Order Info, you could just make the query based on the order number. You could pass the order number itself to checkout sucess from checkout_process.php, then use this order number to query the order info. The drawback to this is you are basically giving unsecure (not logged in) access to your order information to someone that is NOT LOGGED IN, which could then be used to gain access to your other customers orders and information. The other, more secure option would be to move the killing of the session info to checkout_success. Instead of killing the session info in checkout_process.php and prior to reaching checkout_success.php, you would have to move this routine to checkout_success, which would kill the session info when the continue button is pressed. This would keep the Customer and Order info intact until the continue button is pressed... and allow the Customer to print the order info. In order to accompish this, you would have to re-code checkout_success.php and checkout_process.php. I hope all of this makes sense and it helps shed light on your issues with PWA. -R
  3. ugottasalsa

    [COntribution] osC-ProductListingSelect for MS2

    okay... I'll jump in. I know its been awhile. When you move your mouse over the buy now button, what URL appears? If it does not contain the correct product info variables in the URL, then nothing will be added to your cart. Have you made any other modifications to index.php or produt_listing.php? Remember, the products in a particular category are displayed with the product_listing.php module, but it gets its info directly from index.php. Hope this helps. -R
  4. ugottasalsa

    [COntribution] osC-ProductListingSelect for MS2

    Did you run the associated SQL statement on your MySQL DB to add the config options? -R
  5. Okay... so you ran the SQL query... did you verify that you actually have a payment_info field in the Orders table? -R
  6. ugottasalsa

    Wishlist 2.0 Support Thread

    Pass on Hooters? :huh:
  7. Its not the .sql file that you are missing... its the Table define that you are missing. Depending on the version of osCommerce that you are using, this will either go in catalog/includes/application_top.php OR database_tables.php. This also is the same for the Admin section, too. -R
  8. ugottasalsa

    Article Manager v1.0

    Sure.... just don't add it to either of your columns. -R
  9. ugottasalsa

    Article Manager v1.0

    Looks like you missed the language file defines that belong in catalog/includes/languages/english.php. define('BOX_HEADING_ARTICLES', 'Articles'); ...and so on. Look in the Readme.txt file that is included with the contrib, for the following line... Below this line, you will fnd all of the language file defines. -R
  10. That depends on the version of osCommerce that you are using. It could be /catalog/includes/application_top.php or /catalog/includes/database_tables.php. BTW.... All of this is in the instructions. -R
  11. The first error is because you have a missing database table define. Simply add the TABLE_COUPON_GV_CUSTOMER define in the appropriate place. -R
  12. ugottasalsa

    Automated Auction Process

    I can appreciate what you are trying to do, but there are "what if" scenarios that you are just plain overlooking. Sure things SHOULD work, but sometimes they don't. Sh-t happens! ...And yes, it does matter! So what happens if... The Winning Bidder logs in, adds the item to his/her cart, then the phone rings... the baby starts crying... and the kids come home from school. When they finally realize that they were in the middle of paying for their auction, its a day or two later. BUT... by this time, the cart session has expired, and since the DB was already updated when they logged in for the first time, they can no longer login. Now what? Here's another one... You have just logged in as the winning bidder, you haven't added the item to your cart yet, and your PC decides to freeze, causing you to have to reboot. When rebooting, the system will no longer boot? The DB has already been updated so you can no longer login, and their never was a Cart session. Now what? Look at the bigger picture instead of being so closed minded. YOU may not ever experience this, but others might. If you are going to do something, don't do it "half-way". Be professional... do it right! Look, I don't mean to seem harsh, but there are too many people that are being plain lazy and not looking at every possible variable for their contribs. This unfortunately is a good example of just that. You have a good thing here, but its not quite complete. There are a few grey areas. Just because you want to stay away from the core osC files is no excuse. THIS IS AN ADDON FOR OSC... So intergrate it all the way. Instead of saying NO, take it for what its worth. Just my 2 cents. -R
  13. What version of CC/GV are you using? -R
  14. osjunkie... the link should read... gv_redeem.php/gv_no=3434 somehow, you have a comma that shouldn't be there. Track down where the comman is and you will fix your problem. -R
  15. Make sure your active Order Total Modules are set with the correct sort order. -R
×