Messages

Hi,

Every now and then (when ofcourse logging is set to log this) I see a query like:

Code Select Expand


SELECT specials.specials_new_products_price, specials.status, specials.expires_date, products_to_categories.categories_id, products.products_date_added, products.products_date_available, products.products_id, products.products_image, products.products_image2, products.products_image3, products.products_image4, products.products_model, products.products_price, products.products_price_1, products.products_price_2, products.products_price_3, products.products_ordered, products.products_quantity, products.products_status, products.products_invisible, products.products_weight, products.products_tax_class_id, products.products_sku, products.products_type, products.products_file_path, products.products_content_type, products.custom1, products.custom2, products.custom3, products.custom4, products.custom5, products.store_id, products.max_download_days, products.max_num_downloads, products.stock_reorder_level, products.can_order_when_not_in_stock, manufacturers.manufacturers_name, manufacturers.manufacturers_id, products_description.products_name, products_description.products_url, products_description.products_viewed, kk_product_to_stores.price_id, products_description.products_description, products_description.products_comparison FROM products LEFT JOIN specials ON products.products_id=specials.products_id LEFT JOIN products_to_categories ON products.products_id=products_to_categories.products_id LEFT JOIN manufacturers ON products.manufacturers_id=manufacturers.manufacturers_id, products_description, kk_product_to_stores WHERE products.products_id=products_description.products_id AND products.products_id=kk_product_to_stores.products_id AND products_description.language_id=1 AND kk_product_to_stores.store_id='SAV' AND products_to_categories.store_id='SAV' AND products.products_id=30593


I can't really pinpoint what part of the code is causing this. Is there a way to disable this? (By the way we're using KkAppEng in our own Wicket app).

[products_options]

Too much options possible?

Create a lot of product attributes in KonaKart. The products_quantity table has a products_options column which gets filled with values like 69159{70562}69172{70814}. These are the ids of the product options belong to a product.

The products_options column is of type VARCHAR(128). This means that the length of these strings inserted in this column (which may have lengthy id's of product_options) may exceed 128 chars at a point if one were to have lots of product options. We had to resize this column to accomodate our needs, but this doesn't scale well for huge systems I think. I suggest to size up this column in a next release?

[When just saving that product, the price looses precision and is saved as a new value 4.3500 in the database!]

I have the same problem!

This happens when we loaded prices into the system from externally with a lot of precision e.g. we have prices like 4.3538

I tried the code from sashwill to set the total ex price myself with correct scale etc. but still got the dreaded java.lang.ArithmeticException.

In KonkartAdmin on the product details tab the price is shown as 4.35 (but internally in the db its 4.3538). When just saving that product, the price looses precision and is saved as a new value 4.3500 in the database!

We're using this precision for rounding purposes (from exc. to inc. tax and adding etc.) but looks like we have to import products with a price with less precision in order to get it working.

Trevor thanks! Now I understand the current setup better.

Is there any roadmap available or release date determined for the next release?

Is there a special place I can submit a feature request - possibly see earlier made feature requests?  E.g. forementioned roadmap?

Hi!

We're trying to achieve in the future to serve a e.g. 20 stores in our multi-store engine mode 2 (products and customers shared) with each a different price for a single product.

By the way it seems implemented there's the main price of a product ("Price Ex Tax") and 3 additional prices ("Price1 Ex Tax, Price2 Ex Tax, Price3 Ex Tax") on the Details tab in konakartadmin. To achieve a different price for a store in the Stores tab for each store with a number (0-3) one of the earlier mentioned prices can be designated for that store.

Would that in essence limit the amount of stores we can have with a different price (in products/customers-shared mode) to 4? There are only 4 hard-wired price fields per product and when set - they differ in behaviour* compared to using the default price.

If that's the case, storing prices in seperate join-table (such as 'products_to_categories' to link products to categories per shop) wouldn't have resulted in more flexibility?

* the documentation states: "If the price Id is set to 0-3, then price 0 to price 3 are used, regardless of the customer group."

When adjusting the fields in the default address format we have, what possible field values are there?

E.g. when using '$firstname $lastname$cr$streets $suburb$cr$postcode $city$cr$country' it seems that $suburb isn't correctly substituted when viewing the customers address e.g. on a packaging slip of an order he made. It's just '$suburb'. Is there a list of fields I can use?

I also read custom fields are not used by the address formatter. Is this still true? I heard earlier a minor patch to AddressInfo would solve the trick?

Hi!

We're looking for a way to have a quick-signup for he newsletter, needing only a full name and a emailaddress for someone who wants to sign up. However, it looks like you need to register a full valid customer (with all address and all and most imporant - a password) in order to manage it as a subscriber. We could however (only having full name and emailaddress) generate default values for every mandatory field (I've read there are a lot of not-null fields as a result to remain backwards compatible with osCommerce) - but then we think we run into problems when that customer actually tried to register sometime as a new user - its emailaddress will already be taken in mode 2.

Is there anyone who has experience with subscribing to a newsletter in KonaKart without having to have all details for a complete new registration?

I would be interested in achieving this effect too.

From what I can tell, you are mixing up the client engine with the server engine.

Ah, yes I did.

All of the managers in the server engine adhere to an interface and are pluggable. However this isn't the case for the client engine. The names of the pluggable managers of the server engine are read from the properties file at startup time so I think that your only chance is to edit the properties file in code that sets up your test and then run it.

Ok, so no programmmatic method of changing the class to be constructed after having read the property file then - for the server engine. Thx.

Hooking into this question, is it possible to have each the search combine fields with "OR" instead of "AND"?

Hi!

It seems that the special price of a product goes for all shops when products/customers are shared. Is there a way to have this special price differ for stores in mode 2?

Regards, Ted

Since I'm not using the Struts/JSP application delivered with Konakart I have to test several interactions from Wicket with the KonaKart API by means of JUnit and e.g. Easymock.

Now I was wondering: konakart.properties allows to change the default manager classes for something other. Can I do this programmatically during tests?

In konakart.properties I want to leave e.g.

#konakart.manager.CustomerMgr = com.konakart.bl.CustomerMgr

in place, but is there a way to set another class (adhering to CustomerMgrIf ?) to use as customer manager?

E.g. in my own code

Code Select Expand


public void storeUser(CustomerIf customer) throws KKException{
appEng.getCustomerMgr().editCustomer(customer);
}


I'd like to have 'getCustomerMgr()' return my own customer manager if my test requires that. I'd rather not adjust konakart.properties for that if I can avoid that. Setting custom managers as each test requires would have my preference.

Just a quick question: it is possible (by e.g. the API) to have a status set on a product-by-product basis inside an order?

E.g. the full order (with 3 products) has state PARTIALLY_DELIVERED, because
product 1 is DELIVERED
product 2 is DELIVERED
product 3 is PARTIALLY_DELIVERED

Looking at the API it seems only the complete order itself has a status and not individual products in it, right?

Via the client API it seems that when searching for a custom field (dataDescriptor.customX) the search only matches on exact values. Is there as way to specify partial matches too?

Is it possible to search for products which have been rated for a certain value? E.g. give me all products with a minimal rating of 3 stars?