Skip to content

Wishlist

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

5 results found

  1. Automate SSL Certificate

    LET'S ENCRYPT SSL Certificate should be part of the Custom Domain Mapping process.

    There is no reason for this not to be automated. The concept of having to send an email when their API is so simple feels like the Web early-2000's ;-)

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Better Anti-spam Defence (reCAPTCHA)

    Better captcha for comments to remove spam

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Implement Let's Encrypt

    Wild Apricot should implement Let's Encrypt's new free SSL certificates for all paid accounts with custom domains by default. Perhaps the technology is already compatible, but the process seems to be very different from just emailing the WA tech support a certificate.

    49 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Restrict access to files for different admin roles

    Well I'm going to be announcing our new site to our organization this week. We're going with the community plan so that each of 12 teams will have their own page that they will manage. Many are low tech (like looking for the "any" key). I pushed to get the community plan so that we could do this. I loved the feature that you can give access to one page to one person or group. Ultimately I'd like each user to be able to have their own page if they want.

    I created an account and gave admin access to…

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. Enforce stronger member passwords

    When a password is generated by the application, it seems quite secure. However, when people change their passwords, they usually don't make them as secure as they should be. Is there a way to reject a new password if it isn't secure? Or provide a "meter" that shows just how secure their new password really is so that they can reevaluate their choice? I know of some Javascript coding for this purpose (http://javascript.internet.com/passwords ), but I'm not sure if it's possible to use any of it in a CMS environment like yours.

    Thank you for your attention!

    scottishlass
    "You
    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  • Don't see your idea?

Feedback and Knowledge Base