Messages

The first thing that comes to mind is that all configurable paths, both in the database and property files, should be relative to a common "base path". This way I could deploy the application on different paths in different environments (development, test, etc.), and configure just one property if I don't have any particular need of, say, moving the "templates" folder for instance.

Another idea more on the post subject: having the context path in the url should be considered as "uncommon". What I mean is that nobody serious about his business would ever want a "konakart" context appearing in his shop urls, so the distribution should come out-of-the-box with that in mind. The shop application should be deployed in the "ROOT" folder of the tomcat webapp directory. This way, I won't have to move the app when deploying to production and I'd have less configuration tweaks to do.

[if they want to]

What I'd like to see when I "enable checkout without registration" is the possibility for users to... well... checkout without registration if they want to.
So they should see a page with an optional form for checkout details, an optional form for login and an optional button for registration.
Currently they just see the checkout form and (far on top) a "My Account" link that doesn't say neither "login here" nor "register".
Quite confusing.
Luckily we can fix that 

Code Select Expand

How do you know that all users of those base addresses have access to the HttpServletRequest?
It's unfair to discuss architecture and implementation without giving access to any of them... but I know it's my fault, I started it
I was just upset to find out that deploying to a "real" environment had to be harder than expected.
Back to the topic, in case anyone wonders: it works so far.
I have configured two virtual hosts, moved the apps to the respective ROOT, tweaked some configuration files which had the original path in it, changed the configuration via console, and all is fine.
Yet I think that deployment is an aspect of the system that could enjoy some optimization.

Oh gosh, you have the webapp context configured in the admin app instead of just getting it from HttpServletRequest 
See "Store-Front base", "Store-Front image base", ... and who knows if anywhere else!

I need to remove the context path from the url, so that I could access the site with "http://shop.mysite.net" without a trailing "/konakart" .
What is the best approach?
I'm going to define a tomcat virtual host, and I'm going to place the "konakart" and the "konakartadmin" apps in two different virtual hosts with different appBase:

Code Select Expand


<Host name="shop.mysite.net"  appBase="konakartapp" />
<Host name="shopadmin.mysite.net"  appBase="konakartadminapp" />


This implies moving and renaming the webapps.
Is this going to break anything now or in the future?

Thank you.

I confirm that in 7.1.1.1 this still happens: when you click "checkout", you are directed to a registration page that doesn't contain a login form as one would expect.
I guess we have to implement it ourselves 

Hello,

what is the right way of filing a bug report?
Should I post to the forum? Send an email?
Or do I get to report bugs only when paying for support?

I'm asking this because I have the strong feeling that konakart hasn't been thoroughly tested after removing some languages and adding a new one: I keep getting exceptions about missing files and I'd like to tell someone about it 

Just to give a complete picture: I removed the old product images from the filesystem by hand, so the reason I can't change the new product images now might be related to this.

I started from a fresh konakart installation and removed all products and some languages, adding a missing one.
The result has been an inconsistent database and erroneous behavior both in the client and in the console:
- all product images have been kept both in the filesystem and the database
- all order statuses have been kept in the database, for the languages that have been deleted
- I was getting an obscure exception when placing an order, because of the "dirty" order status table which I had to clean by hand
- the console didn't show any order status ad all, before I cleaned it removing the rows for the deleted languages
- I currently can't change the image of a product I have inserted, with no error being reported

Have I stumbled into some bug or is it just me having these problems?

Thank you

Hello,

what do you think is the best way to go from the downloaded community edition to a fully configured production system?
- do you upload the demo database and remove by hand all demo data, or do you start from an empty database (in which case, how do you insert the console admin user to start with?)
- do you install the full konakart distribution on the production server, and later transfer the customized files (.properties, .jsp, etc.), or is it better to install just the war files made with the provided ant task?

Thank you