Feature Request: Suggestions...

  • Profile Image
    Asked on December 20, 2012 at 11:25 AM

    First, change the login to accept either an email address and/or a login ID. Many people don't remember their IDs, especially when such are forced to be unique in a particular systme and the can't get the on they use globally.

    Second, many of dhtml popups are choking in strange ways. When I could not log in, I tried to go to the "send an email" reset. The first time failed since I didn't specify the correct email address for my account. (I have several for different divisions/functions for two different professional sites and one personal site). When I tried to enter a new email address, it would not let me and kept trying to send to the first one that failed.

    Third, since dhtml overlays are being used throughout the site, form "previews" should do the same (using an embedded iframe if necessary). There is no need to use a new window / tab / dialog pop-p (forcing people to turn pop-up protection on/off) with the code approach being used elsewhere in the site.

    J.C. Hendee

  • Profile Image
    Answered on December 20, 2012 at 01:34 PM

    Hi J.C,

    Thanks for the suggestions.

    1. You can log in with your email address.

    2.  What browser is this happening on? We can submit a bug report.

    3. Yeah , that sounds like a good suggestion, I will open a feature request ticket with the developers for that

  • Profile Image
    Answered on December 21, 2012 at 11:01 AM

    I use Firefox and Chromium, both the latest editions. Occassionally I use SRWIron for maximum security, but that one wasn't used to access your system. 

    I also use layered privacy and security modules such as DNTM (DoNotTrackMe), Ghostery, and AdBlockPlus... but these should not affect a legitimate and clean dhtml module script/form/process. The only way they would (for the custom settings I gave for your site in each one) is if something in the form's processing tried to store/access second or third party cookie data, which I do not allow. I disabled security measures level by level to the mimimum acceptable; it had no effect upon the problem.

    Google Analytics, though highly questionable from some perspectives, is being used on your site. I gave it full permissions, and nothing changed. I disabled AdBlock fully on your site; nothing changed.

    ChartBeat(?) is the only other third party tracking module I detect on the page in question. Becuase of their privacy status, they will never be allowed access to read/write information about me. If their script is part of the dhtml form process in question, that is what is choking it. Rework that script to have ChartBeat's data access occur AFTER the form submission processe is fully complete and scripted data verification subroutines have run. That should solve the problem for properly accessing this form on your site without compromising people's privacy preferences.

    No organization with an "undisclosed" tracking data purpose / retention should ever be required for accessing anything on a site.

    Privacy Policy:



    Data Collected:

    Anonymous (Browser Information)
    Pseudonymous (IP Address (EU PII))


    Data Sharing:

    Anonymous data is shared with 3rd parties.


    Data Retention:


  • Profile Image
    Answered on December 21, 2012 at 12:06 PM

    Hi there, 

    Thanks for your feedback / input!

    We appreciate it and will have our dev team look at your recomendations.

    The URL of the thread where your ticket has been forwarded is:


    You can add and follow the udates/comments there.