[
https://issues.apache.org/jira/browse/OFBIZ-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharan Foga updated OFBIZ-2426:
-------------------------------
Sprint: Bug Crush Event - 21/2/2015
> User friendly success/error messages in eCommerce application
> -------------------------------------------------------------
>
> Key: OFBIZ-2426
> URL: https://issues.apache.org/jira/browse/OFBIZ-2426
> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/ecommerce
> Affects Versions: Trunk
> Reporter: Pranay Pandey
> Priority: Minor
>
> I want to propose a change and want to ask for the suggestions for the way to
> go for it.
> *Proposal:*
> Should have appropriate user friendly success/error messages for eCommerce
> applicaiton on the execution of an event from user. As eCommerce is the
> customer facing application.
> E.g.
> # When user creates his/her profile then then the *success message* shown is
> *"The following occurred:
> The action was performed successfully. "* while it should be shown something
> like: *"New user created successfully."* or *"User profile created
> successfully"*
> # When we talk about an error message then e.g. when user tries to login with
> wrong userId or pwd the message shown is *"The Following Errors Occurred:
> error following occurred during login: User not found."* which should be
> something like: *"User not found"* or when password is incorrect *"Password
> is incorrect"*
>
> There are more places where this can observed well that the success/error
> messages are not best suited for eCommerce application.
> Right now for both of back-office and front-end(eCommerce) application we use
> the same common/webcommon/includes/messages.ftl which shows the same messages
> as of back office application for many operations.
> The idea is we should introduce a new Messages.ftl file for ecommerce only
> which will show user friendly error/success messages to the front-end user
> who is the customer.
> I would really appreciate comments from community members on this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
