openfoodfoundation / openfoodnetwork

Connect suppliers, distributors and consumers to trade local produce.
https://www.openfoodnetwork.org
GNU Affero General Public License v3.0
1.12k stars 723 forks source link

Display ordering in shopfront field too tight to allow re-ordering of the sequence #12852

Closed tschumilas closed 1 month ago

tschumilas commented 1 month ago

Description

In the new admin interface, the display ordering by shopfront field (in Shop Preferences in the enterprise settings) does not provide enough room for the user to effectively order the shop display by category or by producer.

Expected Behavior

This setting is used by shop managers to control the appearance of the shopfront (ie the order in which categories are displayed, or the order in which producers area displayed). The fields should have sufficient space to allow for this ordering.

Actual Behaviour

The new interface space is too tight and its difficult to fit in two or more lines of categories or producers.

Steps to Reproduce

  1. For an enterprise that is either 'sells own' or 'sells any' - go to the enterprise setting: shop preferences
  2. See the Display ordering in the shopfront setting.

Animated Gif/Screenshot

image

Workaround

No workaround - user has to 'guess' a bit at what the categories or producers are.

Severity

S4

bug-s1: a critical feature is broken: checkout, payments, signup, login bug-s2: a non-critical feature is broken, no workaround bug-s3: a feature is broken but there is a workaround bug-s4: it's annoying, but you can use it bug-s5: we can live with it, only a few users impacted

https://github.com/openfoodfoundation/openfoodnetwork/wiki/Bug-severity -->

Your Environment

Possible Fix

chahmedejaz commented 1 month ago

The display issue of the fields has been fixed such that it will be displaying all the selected choices. Here's the screenshot: image

However, I noticed that in the new screen remove option was not implemented as you can also see in the above screenshot. This has also been implemented in the fix for this issue. Here: image