Messages

Hi Wynand,

Yes you can install it without the admin tool. Please follow the thread http://www.konakart.com/forum/index.php/topic,10.0.html .

The tool is almost ready. Either tomorrow or Monday at the very latest.

Paolo

Hi Oleg,

Our long term solution to your problem is that we are planning to add some generic varchar fields to the main tables (customer, product etc) that can be used for personalizations.

Until we have that, a solution for you could be to to add manufacturers_model and products_ean to the product model attribute as comma separated variables (you will have to increase the size of the products_model varchar in the database). Then you will have to modify the JSPs to unpack the data for visualization purposes.

-Paolo

Here at KonaKart we haven't tried out Resin. However, the whole idea behind the zip package is to offer support for different platforms / configurations, so hopefully a manual installation using the zip package should work out. If you do try it, please let us know how you get on.

Thx,

Paolo

Hi Shaheem,

KonaKart uses the Struts and Tiles frameworks. The order in which the boxes are displayed (and whether they are displayed or not) is defined in WEB-INF\tiles-defs.xml . The JSP which lays out the tiles is called MainLayout.jsp. By looking at this JSP you can see that the tiles are positioned in 3 columns. You can modify the JSP to layout the tiles any way you want. If you want to change the width of the tiles you just need to modify the line where you see <td width="125" valign="top">.

Hope this helps.

Paolo

Hey Shaheem,

Please let us know when your shop is online. We'd be really interested in seeing it.

Thx,

Paolo

Also remember that you have to re-start Tomcat to pick up the new values in the properties file.

Hi Oleg,

You need to configure the database connection parameters. Try following the instructions that you can find in earlier posts within this thread.

Paolo

You need to set up some configuration variables in the database. I've attached a script that you can edit and then use. There is a description for each variable so I won't go into any more detail here. Let me know if you have any doubts on the usage of any of the variables.

As for compilation, we all use the Eclipse IDE although I imagine NetBeans to be fine. Ensure that you include all of the Jars that we provide in WEB-INF\lib in the classpath.

Hi Shaeem,

Our admin application is very close to completion. It's just a matter of a few weeks now. We are using AJAX technology in order to provide a snappy user experience, so hopefully you'll like it.

Regarding the problem you have found, the osCommerce admin app uploads images to its htdocs\catalog\images directory since it knows nothing about KonaKart. Being a Java application running in a servlet engine, KonaKart requires its images to be relative to the webapps\konakart\images directory. Maybe rather than editing the database, a simpler solution could be for you to use the osCommerce admin tool to upload the images and then manually copy them (or write a simple script) from the htdocs\catalog\images to the webapps\konakart\images directory. In the database the products_image attribute will contain the name of the image with no directory name in front of it which means that KonaKart will pick it up directly from the webapps\konakart\images directory.

Hope this helps,

Paolo

It certainly helps to understand struts. For small changes, I'd try to understand what is already there and to modify the existing JSPs and Struts actions. For large changes (i.e. a completely new client) you could use the web services interface which would allow you to use whatever technology you are most comfortable with.

The new point release of KonaKart available from our web site (2.1.0.3) should fix the problem. The algorithm has been made smarter. The logic is now:

-If the entered text matches a code or a name, we then take it.
-If we don't get a direct match and get back more than one result, we then provide the drop list.
-If we don't get a direct match but there is only one result, we take it.

Obviously, if someone doesn't like the above algorithm, the UI could be modified to always show a drop list.

I haven't studied it closely, but I think that the Junior version should provide enough security . Maybe you can give us some feedback on that as you do the integration ? Meanwhile we have applied to become an Accredited Storebuilder for WorldPay. The process takes a few days, but when approved (and when we've done the gateway module), WorldPay will confirm that our integration is working correctly.

The recording of the state can work in one of two ways.

If the country has zones associated with it (the US does have zones in the default DB that we ship) then the UI forces you to choose a state from the list of zones if it doesn't recognise the state that you entered to be a valid state. When you pick a state from the zone list, we save the stateId in the entry_zone_id field and the entry_state field remains null. Your entry_zone_id should contain the id of 29 for Maine.

If the country doesn't have a list of zones, then the UI allows you to enter any value for the state and we save that value in the entry_state field.

We are implementing payment gateways based on demand. If WorldPay is important for you, we'll try to get it done ASAP. Based on the information available on their website, it looks rather straightforward to implement.