Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jeremy Holland 20 posts 103 karma points
    Feb 02, 2013 @ 18:10
    Jeremy Holland
    0

    Document Type name support for en-US locale in backoffice

    I recently installed the Tea Commerce starter kit, and I discovered that the document type names were all dictionary tokens (#somename) instead of the real names. This made discovering the function of each page a bit more difficult due to the constant switching between dictionary and document type sections looking for the exact word.

    I solved this usability issue by adding the English (United States) language and then copying the value in the English (UK) box for each node in the dictionary. A little time consuming to simply try out the package, but the final result was much easier to grasp the intent of the content structure.

    Adding support for English (US) might be something to consider for version 2.

    Tea Commerce is a great package! Thanks!

     

    Copy Link
  • Anders Burla 2560 posts 8256 karma points
    Feb 04, 2013 @ 07:29
    Anders Burla
    100

    Hi Jeremy

    Thanks for your idea of adding en-US as a default translated part when you use the Tea Commerce Starter Kit. We will implement it for the new Starter Kit for Tea Commerce 2.0. Maybe in a minor release.

    Copy Link
  • Jeremy Holland 20 posts 103 karma points
    Feb 04, 2013 @ 15:51
    Jeremy Holland
    0

    Hi Anders,

    Is there an approximate release date for Tea Commerce 2?

     

    Copy Link
  • Anders Burla 2560 posts 8256 karma points
    Feb 05, 2013 @ 09:22
    Anders Burla
    0

    We aim for a Q1 release

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft