Edit Orders v4.0 Support Thread

[hubert]

If ever..for 1.5.5... If the team thinks these events have to be included in next release.

NOTIFY_HEADER_SHOPPING_CART_OPTION_PRICE is called in /includes/modules/pages/shopping_cart/header_php.php
line 119

   $attr_value = $attributes_values->fields['products_options_values_name'];
      }
	  $zco_notifier->notify('NOTIFY_HEADER_SHOPPING_CART_OPTION_PRICE',array('rs'=>&$attributes_values,'products_id'=>$products[$i]['id']));

      $attrArray[$option]['products_options_name'] = $attributes_values->fields['products_options_name'];

NOTIFIER_CART_ATTRIBUT_SELECT
and
NOTIFY_HEADER_SHOPPING_CART_OPTION_PRICE are called in /includes/classes/shopping_cart.php

line 682

   $attribute_price = $db->Execute($attribute_price_query);
          $this->notify('NOTIFIER_CART_CALCULATE_ATTRIBUTE', array('cart'=>$this,'rs'=>&$attribute_price,'products_id'=>$products_id,'options_id'=>$option,'options_values_id'=>$value));

          $new_attributes_price = 0;

and
line 891

       $attribute_price = $db->Execute($attribute_price_query);
    	$this->notify('NOTIFIER_CART_ATTRIBUTE_PRICE_SELECT',array('cart'=>&$this,'rs'=>&$attribute_price,'products_id'=>$products_id,'options_id'=>$option,'options_values_id'=>$value));

        $new_attributes_price = 0;

which seems logical to me.

And just to notice that it works with Dynamic Price Updater 2.0, i.e., when I change the size (first attrib), the price of other attributes is changed, and when I check the box of one of these changed attributes the final price is good thanks to DPU.

[hubert]

Just a question to EO authors : why the payement method is not a dropdown menu ? It would be much easier than typing Cash on delivery or Credit card letter by letter, no ?

[mc12345678]

Just a question to EO authors : why the payement method is not a dropdown menu ? It would be much easier than typing Cash on delivery or Credit card letter by letter, no ?

Not an EO "author".

And what if one wanted to apply a method that was not in that dropdown? Sure, additional ajax/javascript/etc could be added, but as a base operation is that extra code truly needed?

[hubert]

Not an EO "author".

And what if one wanted to apply a method that was not in that dropdown? Sure, additional ajax/javascript/etc could be added, but as a base operation is that extra code truly needed?

Don't we have a finished list of payment methods ? Are not these listed as payement modules ?

[mc12345678]

Don't we have a finished list of payment methods ? Are not these listed as payement modules ?

ZC has a "finished list", but with this plugin not all transactions need actually occur within ZC and store owners can go on to do/document what they wat to support their business needs.. ZC doesn't limit all possibilities to just what is in ZC. Besides that, it's moldable enough such that if you don't like something you can change it. :) but if that list was something desired and to only limit things to that list, additional coding could be done to limit that. All in a matter of what suits ones selling needs. :)

[hubert]

Hello,

As some has noticed I was in the process of getting Dynamic Price Updater to work within Edit Orders.
I've dug into the code and understood a lot, and this is not as easy as it seems.

1) First problem.
Edit Orders which is on the admin side, deals with orders. That is completely different from the customer side : on the client side we deal with a cart. What's the difference ? The difference is about products and attributes ids.
As those who write code certainly already knows, on the client side products are unique. When, as an admin, you add products to your catalog, these products are (in a manner) templates for products to sold. If you sell T-shirts for example, you don't add to the catalog each copy you own, you just add a model with some attributes.
As long as the customer has not pressed the Confirm Order button, the T-shirt is only a template T-shirt. When the customer clicks the Confirm Order button, all the products that are in the cart are copied in a new database table and then, this is the copy you sell.
When the order is done, products and attributes are getting new ids for each copy sold.

As Dynamic Price Updater is using AJAX techniques to read the attributes id in the html page... You see the problem. Id are different. Of course the databases could tell what is the original id of an attribute but modifying DPU so that it makes this request to the database is beyond my javascript and Ajax skills.

2) 2nd problem.
When you are a customer the webpage you're browsing only shows you one product. In Edit Orders when you click Edit, the whole order is opened to modification which means you have to deal with several products on the same page.
Just saying... Wouldn't it be more elegant to be able to edit one product at a time in Edit Orders, that would prevent errors by not opening to modification the products that are not meant to be modified.

3) 3rd problem (which can be 2bis).
I also have a custom module which is making combined attributes pricing, and this one has a table with price modification rules in it. This modules does two things, it writes the price of the attributes just next to their name and also makes things so that the modified price is taken into account in DPU and the cart. So it also uses the same Ajax technique.

I know there's plenty of Ajax tutorials out there and believe me a read a bunch to finally understand what was going on behind the scene, but if there was someone thinking that's not a big deal to help...

[hubert]

ZC has a "finished list", but with this plugin not all transactions need actually occur within ZC and store owners can go on to do/document what they wat to support their business needs..

Just adding an "other" option would be enough to get everybody happy, no ?

ZC doesn't limit all possibilities to just what is in ZC. Besides that, it's moldable enough such that if you don't like something you can change it. :)

Here I think the rationale should be the other way around and is in most cases : if we have a finished list of ot_ modules or shipping modules this should be in a dropdown.
Customizing is obviously if you want something more. I don't want something more, I just it to be more user friendly.
Here, the shop already has a finished list of payement modules that could be retrieved so I don't see why it's open to typing anything more as what you type is meant to be something that exists. I didn't test but I'm quite sure you can't say that someone paid giving m&m's. :-)

no ?

[hubert]

Hello,

running ZC 1.5.4 with Super Orders 4.0.9 and Edit Orders 4.1.1.
Set as using mock cart (but that doesn't make a difference)

Most of my products are priced by attributes, the size price is the base price and other attributes can add amounts to this base price.

When I change the Size drop down menu in Edit Orders and click Update, nothing changes. Seems to me that Edit orders never goes to review the attributes prices or even if it does, it doesn't calculate the final price so that it reflects sum of attributes prices.

Am I confusing ? Or Am I supposed to enter the new price manually in the boxes ?

I hoped that EO was going to get the Size price from the tables and apply it to my modified product, instead nothing is changing...

[lat9]

Any reason you're not using EO 4.1.4 (the most recent version)?

[hubert]

sorry it is 4.1.4... typo