Author Topic: Save and Cancel buttons on new product or edit product page  (Read 2103 times)

Offline buddahboy

  • Full Member
  • ***
  • Posts: 232
  • Karma: +32/-0
    • View Profile
Save and Cancel buttons on new product or edit product page
« on: October 30, 2013, 05:31:47 PM »
Greetings - it may be a good option to have the "save" and "cancel" buttons on the new or edit product page also at the top of the page and not just at the bottom. 

Thank you
Ron
AbanteCart is one hell of a shopping cart.  Donate once in a while and keep the development plus support going.  --  That's my opinion and I'm stickin' to it!

Offline abantecart

  • Administrator
  • Hero Member
  • *****
  • Posts: 3970
  • Karma: +243/-9
    • View Profile
    • Ideal Open Source Ecommerce Solution
Re: Save and Cancel buttons on new product or edit product page
« Reply #1 on: October 30, 2013, 10:49:31 PM »
I think it is a good idea. Thank you for this suggestion.
We need your help to build better free open source eCommerce platform for everyone.
See how you can help

Offline junkyard

  • Full Member
  • ***
  • Posts: 127
  • Karma: +24/-0
    • View Profile
Re: Save and Cancel buttons on new product or edit product page
« Reply #2 on: October 31, 2013, 10:00:56 AM »
... and also near the product Description field if possible.
(quick save buttons work faster and good for edits)

Offline dharding

  • Newbie
  • *
  • Posts: 25
  • Karma: +7/-0
    • View Profile
Re: Save and Cancel buttons on new product or edit product page
« Reply #3 on: June 13, 2018, 05:41:13 PM »
I'm dredging this topic back up to the top, as it appears it was never implemented.

Given the height/length of the product edit page, having the Save/Cancel buttons at the top of the page in addition to the bottom of the page is a necessity.

Can this be manually changed easily, or is it too involved of a change?

Thank you.

Offline abantecart

  • Administrator
  • Hero Member
  • *****
  • Posts: 3970
  • Karma: +243/-9
    • View Profile
    • Ideal Open Source Ecommerce Solution
Re: Save and Cancel buttons on new product or edit product page
« Reply #4 on: June 18, 2018, 08:37:49 AM »
AbanteCart has a quick save feature now. If you create incomplete product and start editing it, you can save each field individually.
If user is creating a new product entirely, normally, he/she fills fields from top to bottom.

It is easy to add an extra buttons at the top, I just think it will be too much for majority of users.

Let's see more opinions.
 
We need your help to build better free open source eCommerce platform for everyone.
See how you can help

Offline dharding

  • Newbie
  • *
  • Posts: 25
  • Karma: +7/-0
    • View Profile
Re: Save and Cancel buttons on new product or edit product page
« Reply #5 on: June 18, 2018, 08:45:24 AM »
If user is creating a new product entirely, normally, he/she fills fields from top to bottom.

Yes, but if you are only using a subset of the available fields (depending on the merchandise you sell), you may find yourself done with data entry and still towards the top of the page.

Regardless, best usability practices recommend that on lengthy data entry pages, you have save buttons at both top and bottom of the page/screen/tab. You shouldn't have to scroll all the way down (or up) to execute a major function.

Thanks.

Offline Basara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3773
  • Karma: +184/-0
    • View Profile
Re: Save and Cancel buttons on new product or edit product page
« Reply #6 on: June 18, 2018, 09:26:42 AM »
.. save buttons at both top and bottom of the page/screen/tab.

Agree, floating Save button will be even better.  ;)
“Chuck Norris is so amazing.”
― Mother Teresa

Offline dharding

  • Newbie
  • *
  • Posts: 25
  • Karma: +7/-0
    • View Profile
Re: Save and Cancel buttons on new product or edit product page
« Reply #7 on: June 18, 2018, 09:46:20 AM »
.. save buttons at both top and bottom of the page/screen/tab.

Agree, floating Save button will be even better.  ;)

I thought about that, but didn't want to suggest it as I thought it might be too difficult to implement effectively. That would be the best option IMO. Not essential, but nice to have. :)