[jira] [Commented] (OPENMEETINGS-2468) Moving keys 282, 283, 286 and 287 from translation table to configuration
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205358#comment-17205358 ] Ali Alhaidary commented on OPENMEETINGS-2468: - The way I see it that it can localize and personalize :-) Well, we can live with it as we did a small script executed each time we change the build, but that is something not all up graders can do. And most important, I do not want to consume any of your time for minor things. > Moving keys 282, 283, 286 and 287 from translation table to configuration > - > > Key: OPENMEETINGS-2468 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2468 > Project: Openmeetings > Issue Type: Improvement > Components: Dashboard >Affects Versions: 5.1.0 >Reporter: Ali Alhaidary >Assignee: Maxim Solodovnik >Priority: Minor > > Keys 282, 283, 286 and 287 in language table have the same site specific > characteristics as some other configuration keys like site name, google > analytics and mail parameters > When upgrading to a new build or version, these keys need to be configured > each and every time, so moving them to the database makes it more practical. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2468) Moving keys 282, 283, 286 and 287 from translation table to configuration
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205217#comment-17205217 ] Maxim Solodovnik commented on OPENMEETINGS-2468: Well, I'm not sure this need to be moved to configuration this way you can't have localized URLs (right now this is possible) this is true the changes will be lost on upgrade ... not sure what can be done here :((( > Moving keys 282, 283, 286 and 287 from translation table to configuration > - > > Key: OPENMEETINGS-2468 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2468 > Project: Openmeetings > Issue Type: Improvement > Components: Dashboard >Affects Versions: 5.1.0 >Reporter: Ali Alhaidary >Assignee: Maxim Solodovnik >Priority: Minor > > Keys 282, 283, 286 and 287 in language table have the same site specific > characteristics as some other configuration keys like site name, google > analytics and mail parameters > When upgrading to a new build or version, these keys need to be configured > each and every time, so moving them to the database makes it more practical. -- This message was sent by Atlassian Jira (v8.3.4#803005)
