These are chat archives for
Sign in to start talking
Issue tracking system
Nov 10 2016 18:52
Are there any password policies available for eventum? ie.. password has to be x characters long, include letters,numbers and symbols?
Nov 10 2016 19:36
eh, i wonder how to solve json encode and charset issue, db upgrade should skip converting or something?
btw, you need to c onvert your data to latin1->utf8 too, just changing APP_CHARSET is not enough. or you don't care about old data?
no, there are no password policies, common sense applies :)
Nov 10 2016 20:28
How can i properly convert from latin1 to utf8?
i do care about the old data
If i implement password policies, would that be something that you guys would be interested in merging in?
Nov 10 2016 21:12
yes, don't mind password policies changes
there existed scripts to convert data, don't appear to exist in master branch
and github wiki is not searchable, how stupid
i see the convert scripts were in old upgrade dirs, which were dropped due better upgrade mechanism
but you can find old version of the script here
so with 2.2 upgrade you should had have the charset convert script
Nov 10 2016 21:33
added some notes about charset here
Nov 10 2016 22:24
Regarding the duplicate patches: I agree that they should be renamed and re-run. Possibly leave a new 28 patch with a pointer to a PR for this
Nov 10 2016 22:38
shoot, i already the latest version running in production. wish the the v2.1.1_to_v2.2 index mentioned to upgrade to utf-8.
could i run it now that i am on the latest version if i modify that script and remove %TABLE_PREFIX% since there are no table prefix's?
Nov 10 2016 22:58
I read the updated upgrading. How do i determine if the former encoding was proper/improper, is it possible programmatically? How could i possibly determine my previous encoding?