Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

djmonkey1

Pioneers
  • Posts

    2,114
  • Joined

  • Last visited

Everything posted by djmonkey1

  1. You have to delete them manually, obviously at this point Order Editor is not going to do it. What is the class value of your shipping and tax components as stored in the orders_total table? Are they ot_shipping and ot_tax, or are you using custom components?
  2. The only time I ever saw this was when I was developing 5.0 and working out the kinks. As of right now I can't re-create this. As Silverado05 mentioned, you should go into your database and manually delete all the excess entries. Go to the orders_total table, sort by order_id, then find all the entries for this order. It looks like there will be a lot- delete all the extras (ie there should only be one subtotal, one shipping entry, maybe only one tax entry depending on the circumstances, and one total). What are all those components that are showing up so many times? Shipping?
  3. It looks like Manual Order Maker won't work at all unless you have Order Editor , at least according to the install instructions that come with Manual Order Maker. That's a strange way to make a contribution. No wonder insaini just went the obvious next step and combined them into one package.
  4. What operating system and web browser are you using?
  5. Each products tax field is writable. Unfortunately there is no such thing as a shipping_tax field; such a field was included with earlier editions of Order Editor as a workaround but has been removed in 5.0 (and 4.0 as well I believe). As for dollar amount tax total field being editable, it wouldn't matter if it was because the entry would just be overwritten by the output of the ot_tax module.
  6. Order Editor 5.0 is not a revision of Order Editor 4.0. The 4.x and 5.x releases were developed independently, and, linearly speaking, are both updates to the 3.x series of Order Editor. As such they would best be considered parallel forks. Personally I've always considered Order Editor as a stand-alone contribution designed around the editing of orders already placed. Order Editor 4.0, as far as I know, is the only version of the contribution ever released that goes beyond that.
  7. I don't have any plans to do this, however insaini may have mentioned something along those lines.
  8. Instead of if (!tep_session_is_registered('easy_discount')) { tep_session_register('easy_discount'); $easy_discount = new easy_discount(); } use $easy_discount = new easy_discount();
  9. I can't reproduce the  showing up next to the £ bug. I've tried inserting the pound symbol as both just the symbol via cut and paste and also by typing in the html tag £ for it, both work fine. Where are you seeing the  show up?
  10. What happens if you delete the added code if (!tep_session_is_registered('easy_discount')) { tep_session_register('easy_discount'); $easy_discount = new easy_discount(); }
  11. 1 and 2 are probably the same bug; I'll look into this. 3 sounds like you have a custom code somewhere to check the VAT number against an entry in the database and give the customer tax exempt status. You will have to build this custom code into Order Editor as well. I could be of more help if I knew the name of the contribution you used for this, where the custom code is located, etc.
  12. I've never heard of anyone taking down their server by installing Order Editor, although I suppose anything is possible. If you're really that worried about it, just apply the bug fixes to the appropriate files before you upload them.
  13. The non-object is $easy_discount. The member functions in this case would be ->count() and ->get_all(). You would have to re-create the $easy_discount class within Order Editor to get this to work; there are general instructions on how to do this included install.txt file that comes with the Easy Discount contribution. It is possible that this is all you have to do: in admin/edit_orders.php find near the top of the file find require(DIR_FS_DOCUMENT_ROOT . DIR_WS_CLASSES . 'http_client.php'); then, on a new line immediately below that one, add this code: require(DIR_FS_DOCUMENT_ROOT . DIR_WS_CLASSES . 'easy_discount.php'); Next, perform that exact same procedure within admin/edit_orders_ajax.php. Make sure you get all the bug fixes listed in my signature.
  14. Once the bug fixes listed in my signature have been applied 5.0 is ready to go for use on production sites. It does not have any of the "Manual Order Maker" features of 4.0, however.
  15. There should at least be boxes to enter credit card information (card type, card number, etc) on the edit_orders.php page underneath the payment method dropdown. They appear when you select whatever is the pre-selected credit card payment option on your site. Check the information icon tooltip next to "Payment Method" on edit_orders.php for more information.
  16. The only difference between Beta 1 with bugfixes and the final release will be the non-javascript/non-ajax features and cleaner code. Whether or not you feel the upgrade path will be easy depends on your definition of "easy"- i.e., I'll think it's easy, but then again I work with these files almost every day.
  17. Just a quick note to let everyone know that I am working on the final release of 5.0 however I have no ETA as of yet. Due to the dearth of bug reports from BETA 1, I'm skipping BETA 2 and going straight to the final release. At this point I'm thinking that either not many people are using it or the bugs already fixed are the big ones. As mentioned in the previously stated plans for the now defunct BETA 2, the final release will have bug fixes as necessary, an Add a Product function that works without JavaScript, cleaned up and streamlined AJAX code, the ability to toggle the AJAX features on/off via admin, and as always will contain all source code or your money back! If you have any comments, suggestions, bug reports, feature requests, gripes, etc, please don't hesitate to post here.
  18. Part of your problem is the code <FORM method="POST"><input name="orders_numero_facture"><input type="Submit" value="OK"></FORM> That code is contained inside the form "edit_order" and that is why the buttons don't work- you can't have a form inside another form (forms can't be nested).
  19. Order Editor 5.0 does not use a file called oe_order.php. The order class file used by 5.0 is stored at admin/order_editor/order.php. You should revert back to the files you had before you made these changes and make sure everything works properly then. Once you have stable code working you can try again to get this contribution integrated.
  20. It looks to me like you have a payment method with a really long title. Have you tried the fix I suggested?
  21. In admin/edit_orders_ajax.php find //11. insert new comments if ($_POST['action'] == 'insert_new_comment') { and change it to //11. insert new comments if ($_POST['action'] == 'insert_new_comment') { $order = new manualOrder($_POST['oID']); The error in admin/orders.php is caused by the fact that there is no comma after '2007-08-03 20:22:51'. The query should read insert into orders_status_history (orders_id, orders_status_id, date_added, customer_notified, comments) values ('561', '1', '2007-08-03 20:22:51', '1', 'TEST') and then you wouldn't get the error. You need to track down the code in admin/orders.php that generates that query and put the comma back where it belongs.
  22. Disable the payment method dropdown and see if the problem goes away. If so find in admin/edit_orders.php echo tep_draw_pull_down_menu('update_info_payment_method', $enabled_payment, $order->info['payment_method'], 'id="update_info_payment_method" onChange="init()"'); and change it to echo tep_draw_pull_down_menu('update_info_payment_method', $enabled_payment, $order->info['payment_method'], 'id="update_info_payment_method" style="width: 200px;" onChange="init()"'); then re-enable the payment method dropdown menu.
  23. Then that's not it then. I was thinking something more along the lines of 800x600. :) Admin DHTML Menu is still a nice contribution though. It might be something with the HTML. I have not gotten a chance to look through 4.0 yet myself so cannot be much more help.
×
×
  • Create New...