Messages

Also, I see in your demo store (i.e. konakart.com/konakart/Welcome.do) that your state field is a drow-down - how did you do that?  I've enable the state field through the admin interface, but it only displays as a text box, rather than the preferred pre-populated drop-down box.  Similarly, how can I make 'United States' the default in the country drop-down?

Again, I apologize for my ridiculously simple questions here, but as I mentioned, we're in crunch mode to get this released, and there are, all of a sudden, a lot of small little issues to resolve...and again, I know nothing of GWT.  Thanks, all.

I've set up an implementation of the community edition of KonaKart at shop.dispatch.com, complete with a custom SSO design, custom front-end, and a small catalog, but there are still a couple of things I cannot quite figure out.

One thing I cannot figure out is how to change the formatting of dates as they appear to customers.  For example, although I was able to change the format in the Admin app to MM/dd/yyyy, I'm not finding success in having that change propagated out to a user page, like the one page checkout page when it asks for a customer's birthday.  Any ideas on that?

Also, being *completely* unfamiliar with GWT, how can I add validation messages for that screen as well?  So, if someone didn't enter their shipping state, and then they chose to attempt to continue the process, I would like to display a validation message stating whatever problems are on the page, or on a per field basis.

Along the lines of my GWT ignorance, can someone perhaps give me a quick rundown of how it's implemented in KonaKart and how I could go about adjusting some of its behavior?  I'm perfectly okay with references that can help me, too.  There are some (of course) last-minute changes that stakeholders would like to see, but I'm fairly sure that those changes will lie with the GWT code, and I, at this point, just need to figure out how to make the change(s) and move on.

Hello All,

I need to be able to implement multiple product options for the same product. I'm selling a magazine and need to be able to sell a half year and full year subscription. I'm hoping, and figuring, this isn't that big of a deal. When I search for 'models' or 'model' here in the forum I get 2 results total.

The potential pony that I also am asking for is to be able to sell two models of two different products together.

Any help would be greatly appreciated.

KonaKart and OpenCMS will be running on separate servers in disparate instances of Apache Tomcat.

That's close to what we want to do.  Basically, we want to keep the coupling between he two systems as loose as possible, linking off to the prepackaged pages that KonaKart uses.

For example, if we had a news story that talked about rain or something weather-related, we might include a link on that story page off to a KK product page for an umbrella.  The KK pages would be customized so that the general look and feel of those pages wouldn't be all that different from our OpenCMS-generated pages.  This approach keeps development to a minimum; in fact, the lack of need for any large amount of development is why we're trying to go with KK as our solution.  The only catch is allowing the checkout process to seem like an SSO experience - pre-populating the form data for checkout with information stored within our OpenCMS system.

If I understand your approach correctly, it seems to me that I would have to do some more extensive development of the KK OpenCMS module.  By coupling the two systems as closely as you seem to suggest, wouldn't I have to rewrite a lot of the functionality KK has provided me OOTB?  So, I'd have to have layout pages and such for products, for checkout, etc.  KK has all of that already, and I want to try and use what they've given me with as little modification as needed.  Is that true, or am I over-complicating this?  I suppose I could throw some custom code in the Header.jsp and have it look for some OpenCMS User bean in the Session, perhaps, which it could then take and use to assign the pertinent data from that bean to its corresponding KK Struts elements on the JSP at checkout...?

So, with that said, do my previous ideas make sense?  Any ideas on pre-populating checkout form data with OpenCMS user info?

Haha, they were actually my first stop, but they are using their development in this area for commercial purposes.  And unfortunately, it is not within the scope of this project to incur any greater a monetary expense than what it costs for me to sit and develop.

Addendum to earlier posts:

I talked a little bit with the boss about the SSO limitations we've been discussing here in the forum, and that conversation changed the scope of the project a tad bit.  In short, we do not really need a true SSO solution, as I had previously stated.  What we need will just seem like SSO.

Ultimately, we need to have a user go to checkout and have the form data be pre-populated (e.g. address info, name, etc.).  This means that I do not actually care if the user is registered within KonaKart or not; in fact, this seems to be the same as what KonaKart documentation refers to as 'one page checkout' (true?  not true?).  I do need to somehow pass the OpenCMS user data to the KonaKart checkout forms so that it can be used.  This I'm not so sure how to do, though.  Perhaps map values from the OpenCMS user object to a KonaKart customer object and then put that in the Session for use on the JSP by Struts?

Now, some of our products would require registration, and here's the solution I've come up with for that.  Since I have direct control over the header and footer for all KonaKart pages, I could just insert some code into the header that would check for a token.  That token would be placed there upon a user logging into our OpenCMS system.  If the token was not present in the KonaKart header, the user would simply be redirected to a log-in page (or some such similar action).

With this solution in mind, I do see at least one caveat: how would our system (i.e. an OpenCMS eCommerce module) track orders placed by a user?  If I understand KonaKart well enough, orders are stored using the email address as its identifying attribute, no?  So if that's true, I should be able to retrieve all orders based on a user's email address.

Does this seem like a manageable workaround to accomplish my company's goals while continuing to stay within the bounds of the Community Edition?  Am I breaking the future upgrade path for new versions of KonaKart by doing any of these things?  And thank you for your help with these questions, @julie, it's very much appreciated!

Ok, that was pretty much what I expected; we actually take that same approach now between a proprietary registration system and a multimedia platform called KickApps.

However, I'm having the same problem as @michaelwechner - I cannot find the security manager class of which you speak.  I do see LoginIntegrationMgr.java, but that doesn't seem to contain any of the previously mentioned methods (i.e. checkSession(), etc.).  Is this where I need EE?

One more question: if I end up being able to accomplish SSO with the community edition, how would I deal with generating a valid SSO token to be used throughout the user's session?

So, reading through this post, and seeing one other referring to Custom Credential Checking (http://www.konakart.com/docs/CustomCredentialChecking.html), I'm still unsure as to how one could implement a true Single Sign-On (SSO) solution.

I do not want to just circumvent KonaKart credential checking and give someone access if they meet certain requirements.  I want to truly implement an SSO solution; a user on our site should be able to seamlessly go from our registration system to KonaKart.

Specifically, we use OpenCMS to manage all users, whether administrators or end-users visiting our website.  I want to create a solution that would allow a user to log in to our OpenCMS-managed system and also be logged in to KonaKart.  The main way this coupling would be used is if a user on the OpenCMS side logged in to our system and then wanted to purchase a product.  When they add an item to their cart and proceed to checkout, I would want to be able to use the information stored within their OpenCMS user object to fill out form data, etc.

Is this desired functionality only available in the Enterprise Edition?  Or is this something that can be achieved using the Community Edition?