In your situation I would just play up the fact that it would take a lot of effort to "fix" the problem. If they're that anal about it, they can always pay a lot to have it fixed, but it's really a small issue in the grand scheme of things... and I doubt any users are actually having problems.
------------------------------------------------------------------------ Apache <mailto:[email protected]> May 16, 2011 3:33 PMA client of ours has picked up that Habari uses case sensitive usernames (I did a test a on Wordpress install and noticed it doesn't use case sensitive usernames) - normally this wouldn't be an issue but the client loves to make a lot of demands and their customers are fairly luddite.Does anyone have any best practice they can share. We already suggested telling people its case sensitive at registration but the trouble is our system is integrated with Magento and any change to the registration system would affect both user tables and systems it is just not part of our dev schedule at the moment.I just want to know what the standard experience is and what people would expect or recommend because I would rather not change default behaviour and have a solid argument to back up that case. Otherwise its back to adding yet another change request to the product back catalogue which is fine as long as it makes sense.-- To post to this group, send email to [email protected]To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users
-- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users
<<inline: compose-unknown-contact.jpg>>
