Feature Suggestions

Submit your feature ideas and votes. Take advantage of search to find existing submissions and use your votes wisely.

I would be very interested in ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Coupons for specific items

    I would like to be able to be more specific with coupons.. such as choose specific products or print sizes that the coupon applies too.

    823 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    68 comments  ·  Selling Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Site-wide SSL / HTTPS protocol

    We'd like to force our domain to load HTTPS. I am proposing either an option for customers to install their own SSL certificates or (and I'm sure this would be the preferred method) implement it site-wide.

    As a suggestion, Letsencrypt (now Certbot) just launched out of beta, and is run by the Electronic Frontier Foundation.

    57 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  18 comments  ·  Client Experience  ·  Flag idea as inappropriate…  ·  Admin →
  3. force HTTPS for all Login and back-end operation

    All backend operations should be defaulted to HTTPS, instead of the current state, where all backend operations are forced to HTTP only, with a few exceptions.

    On a non-secured, non-encrypted network, especially on wifi, it is fairly easy for somebody on the same network to monitor and record HTTP connections, originating from within the same network. It is also quite possible for a third party to "listen in" on HTTP connections anywhere enroute in between the ZF user and the ZF server.

    At the moment, only a few specific pages operate on HTTPS in the ZF customer backend, such as…

    10 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Edit View/Admin Ideas  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base