Alex Weissman
Alex Weissman
For backwards compatibility, we could still have a special `auto` hash type, which will tell UF to try to auto-detect the hash type based on its length (like we do...
> force dev to use UF hash of choice Yes, but in the meantime, you still need to work with the legacy hash before the user signs in again. There's...
What was the issue again? Just the formatting in views?
Still an issue
Seems like a question for @lcharette as he has designed most of our testing environment.
Any takers?
Seems to still be a problem. I know lots of folks configure this in their server config, but it would be easier if it could happen at the application level.
I'm working on a refactor of `ufForm` which will fully expose the ajax parameters through the settings, while remaining backwards-compatible.
Seems like we need to have a broader discussion on client-side i18n.