Messages

It's expected behaviour.

In the Enterprise version you can set this property in konakartadmin_gwt.properties:

# Stops logout after a browser refresh
#fbc.save_session_in_cookie                                 = true

You can't disable the image scaling if you use that image tab of the Admin Console.


If you load your images some other way than through the Admin Console you can use whatever images you like... but the Admin Console will only show them if they use the naming convention defined.


Another option is that you can choose to use the previous images tab by setting:

fbc.g.kk_panel_editProduct.images.tab.version = 1

No, not if you load the images through the Admin Console.

The images created are defined by the following key:

fbc.kk_panel_editProduct.images.options

This defaults to:

big;360;360 medium;150;150 small;80;80 tiny;60;60

This is an Enterprise-only configuration.

This is really a question about Java Memory settings.

Search the Internet - You'll find a vast array of information about how to set the various memory settings appropriate for your particular version of Java, on your particular platform, in your particular environment.

A convenient place to set these in KonaKart, on Windows, is in the file:

bin\startkonakart.bat

In there you will see a line beginning "set CATALINA_OPTS="

On this line you will see 3 memory settings (for XX:PermSize XX:MaxPermSize and Xmx).

If Java is not starting up, you will need to adjust these to suit your environment.

Just reduce the values until it starts up....  and stays up.
   

Good questions.... and all of your ideas are valid possibilities.

A lot depends on what your final objective is.

If it's just a quick prototype than I would do as little as possible and that would probably be to make an Eclipse project, put those source files in your SCMS and create a build from that to create the portlets (using the KonaKart ANT files as a guide).  For rapid development it's very useful to be able to run the storefront you're customising from within Eclipse.

However...   when some people integrate with Liferay they just build custom portlets themselves and integrate with KonaKart via the APIs.   This is a completely different way to implement - we have examples of customers who take this approach - and customers who take the former approach where they convert the whole Struts storefront app to a Liferay portlet.  Exampels of each can be found here:  http://www.konakart.com/cms-portal-integrations/liferay/

If you're building independent portlets I would build your own project(s) from scratch and use your SCMS as you require.

One thing to remember with KonaKart is that it's easy to upgrade without changing your storefront.   Therefore, your investment in building the storefront is not lost when a new release of KonaKart comes out.   Put simply,  the upgrade process involves running some SQL to update the database then to replace the server jars...   The APIs remain backwards-compatible so your storefront continues to work with the new version of KonaKart.

I can't reproduce that.  I get a KonaKart dialog box showing the error when, for example, the current password is entered incorrectly, or the new password is the same as a recent one.

Please can you explain step by step how to reproduce?

The system will show the message key itself if it can't find the key (or its value) in the Messages.properties file.  It does that to help you figure out the undefined keys.

All I can assume is that you haven't moved the new Messages file into your classes directory in the appropriate webapp.

Please write to sales@konakart.com advising who the customer is and the strore's URL

v5.0.0.0 was released literally 5 years ago (June 2010).  Why do you need that now?

You can set custom validation on many of the attributes shown in the KonaKart Admin Console by modifying the file:

"*\KonaKart\webapps\konakartadmin\WEB-INF\classes\CustomValidation.properties"

In your case you should look at "Product.quantity"

Yes, that would be a good way to do it.   You are free to write whatever application you like in those Custom panels.

The role-based security in KonaKart can be used to control which users see which panels - including these Custom panels with your custom functionality.

Not sure what you mean there.

The JSON versions of the APIs end up calling the same engines as the other versions of the API (POJO, RMI, SOAP)... and you can customise those in the standard ways described in the User Guide.

It's not possible to change the Admin Application like that;   You would need to add your own custom panels that worked exactly the way you require.

Custom Panel Configuration is an Enterprise Only feature

You can see a description of how to enable the custom panels in the konakartadmin_gwt.poperties file starting at this point:

Code Select Expand

#--------------------------------------------------------------------
#
# Custom Panel Configuration
#
# Allows you to specify custom panels in each section of the Admin
# App
#
# Enterprise Only
#
# Uncomment the line below to make the custom panel appear.
# The Custom panels appear below any KonaKart panels defined for the
# section.


Also, would like to know the difference between 'tep_cfg_select_option(array(\'true\', \'false\')' and 'choice(\'true\', \'false\')'.

The effect is the same.   The odd-looking "tep_cfg..." version is only there for historical reasons.   I recommend you always use:

Code Select Expand

choice(\'true\', \'false\')


Why not just set up a default manufacturer (store owner?) and use that?