Jump to content

kgt

Members
  • Content count

    2,878
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by kgt

  1. The problems with Paypal IPN stem from the fact that that payment module deviates from the standard way osCommerce payment modules work. In order to keep DCC working with IPN, I have to download the latest version and see what they've done. I promise to do that as soon as I have the time, but it probably won't be today or tomorrow. If you're decent with code, you can open checkout_process.php and includes/modules/payment/paypalIPN.php and compare them. There aren't many changes that have to happen to get it working, but they have to be redone for every IPN release.
  2. I'm sorry, you're correct. I was thinking of admin/includes/boxes/catalog.php, not categories.php. I knew you had a template because this is a common problem with templates. Do a google search for your error, and you should be able to find some solutions.
  3. The configuration table is needed by oscommerce to run, and if it was deleted when you installed DCC, then you did something wrong. You'll need some help figuring out what went wrong and what steps are needed to recover. I'd help you, but I don't have much time to even monitor this thread for the next week or so. You'll get more active help in the general question forum.
  4. Revisit the install instructions for admin/includes/boxes/catalog.php.
  5. You've got a template, and for some reason template makers seem to like putting things in places they don't belong. However, that's not really your problem. It's looks like your real problem is that you uploaded admin/includes/boxes/categories.php to catalog/includes/boxes/categories.php. That file should be in the admin directory. You'll need to restore categories.php from a backup and re-upload admin/includes/boxes/categories.php to the correct directory.
  6. Make sure that your start/end dates for the coupon are valid dates. The coupons admin expects you to enter dates in the format provided in your admin/includes/english.php file towards the top. If your english.php says date format is mm/dd/yyyy, and you try to enter the date as dd/mm/yyyy, then you can get this error. That reason is no valid coupons can be found with an active date range that includes today. Look closely at your coupons. If they say something like 3/17/0007, then something is wrong.
  7. That error message is not the same as the one in the help file. Note the ot_ on the start of the file name. This error happens when you upload your class file to your languages directory. includes/modules/order_total/ot_discount_coupon.php and includes/languages/english/modules/order_total/ot_discount_coupon.php should NOT have the same content. You'll need to re-upload the language file from the install zip.
  8. 1. Yes, if you have Paypal set to aggregate cart totals. 2. I cannot say for sure, but I think so. 3. Yes.
  9. I'm not familiar enough with Protx to say for sure. If all you did to install the Protx module was upload it to includes/modules/payment and includes/languages/english/modules/payment, then you'll be fine. If it requires you to make changes to checkout_payment.php, checkout_confirmation.php, checkout_process.php, or includes/classes/order.php, then there might be an issue (but even then it's fairly unlikely). Paypal IPN is the only payment module I know of that won't work with DCC "out of the box".
  10. If the module is there, it should be picked up. That page is just displaying all files in finds in your modules directory. If you have uploaded ot_discount_coupon.php to catalog/includes/modules/order_total you will either get an error, or the file will display. If it's not, you've got another problem outside the scope of this contribution.
  11. The customer I originally wrote this for had MVS. That shouldn't be the problem.
  12. Turn on error_reporting to find out what the error is. See my response here: http://forums.oscommerce.com/index.php?sho...d=1042895
  13. You're getting a fatal error, but you have display errors turned off (which is why you get a blank screen). It's pointless to just guess at the error (though you might try commenting out line 14 in includes/modules/order_total/ot_discount_coupon.php since it tends to give people problems). I recommend setting up a test site so you can make sure everything is error-free before going live. Add the following two lines to the top of includes/application_top.php to turn on error reporting so you can find out what the error is: ini_set('error_reporting', E_ALL); ini_set('display_errors', 1);
  14. To click "install," you need to go to Admin > Modules > Order Total first. Then once it's installed, go to Admin > Catalog > Discount Coupons to create and edit coupons.
  15. They display only after refresh? Are you certain the first block of code you quoted appears before this line in your code: $order = new order;
  16. Make sure you uploaded includes/classes/discount_coupon.php (and all other new files). Those two files should NOT be the same. They have the same name, but the content should be different. If they have the same content, you've uploaded the originals incorrectly. Re-upload them.
  17. If you send me your email, I can send you screenshots.
  18. Discounts will apply to specials. The next version will allow you to exclude products on special.
  19. I don't have time to do an update for the newest version of Paypal right now. I'm very busy with real work. The changes are fairly small. You can find DCC code in that module by searching for my handle (kgt). All code should be commented.
  20. Fixed discounts are actually percentage discounts applied to a fixed amount (the max order). This gives a fixed discount. The discussion of this & why can be found earlier in this thread. If you're using a percentage discount, leave the max order field blank.
  21. If you enter a max order, the discount will always be applied to that amount.
  22. kgt

    Can Someone Explain STS

    If you pay attention to the URL when you navigate through your site, you'll see it reference file names like product_info.php?something=something index.php create_account.php etc Those filenames correspond directly to filenames in your catalog root directory. $content is pulled from the output of those files. You can affect the appearance to a degree by using CSS (which affects mostly color schemes). For greater control over both the content and the layout, you need to create template files for each page you want custom content/layout. The structure for setting that up is described in the documentation. If you want to create a custom layout, you do not have to create a custom template for every file (just the ones you want to customize). You can also customize modules and boxes. I'd recommend starting with just a custom box so that you get the hand of it before tackling something with more meat to it.
  23. kgt

    API Payment module into OScommerce

    The form you need to actually display to the customer would be similar to the form displayed in the selection() function of most payment modules (see the authorize.net module). You would then need to "add" the other hidden fields, like your merchant id, when you actually pass the information to the payment gateway. This would depend on the method chosen. To keep the customer on your site, you must have the code submit the information to the payment gateway, and handle any errors. This is the slightly more complicated method. To pass the customer to the payment gateway, which then either passes the customer back after processing or makes a remote call back to your site after processing to complete the order, you can follow the example in the PDF. To follow the example in the PDF would not require cURL. You'd add the cc fields in the selection() function. You'd then add the hidden fields in the process_button() function (again see the authorize.net module). You'd set the form submission url: $this->form_action_url to the URL in the example. You should then need to do some configuration with the payment gateway to enter in the URL for checkout_process.php. To do the cURL method, in which the customer never leaves your site, you would do all of the above EXCEPT set the form submission URL. The form submission URL would be checkout_process (as it is with the normal checkout procedure). In before_process(), you would use cURL to send the forum information to the URL in the PDF. You'd then parse and handle the response. If there's an error, redirect back to checkout_payment. If you want to use the second method, I'd recommend getting the first to work, and then going from there. The first method will give you a better understanding of how the osCommerce payment modules work without getting to deep into how to interact with the payment gateway.
  24. kgt

    API Payment module into OScommerce

    You can use the other payment modules as an example of how to proceed. Without more info, it's hard to give more help. (The link doesn't work.)
  25. kgt

    Can Someone Explain STS

    $content will be pulled from the stock osCommerce files found in your catalog root. To change the layout of $content, you'd need to create template files for each content item. This is covered by the Create a Template for a Specific Page, etc, sections of the manual. At it's most basic, STS will allow you to create a frame of sorts for the content. If you wish to reformat the content, then you need to create a template file for each page you wish to alter the content format (each page has different content and so requires different code to handle that).
×