Dear Atrol,
In mantis 1.2.x I was using lang_get( 'status_enum_string' ) to get list of statuses. It was picking up correctly custom-created states from the custom_strings_inc.php. In mantis 1.3.1 this function ignores (as I understand) these and simply returns entry from the corresponding language file. Is this a bug, which I should report, or maybe there is new way to get enumerated list of states - including custom states? I searched on https://www.mantisbt.org/bugs/view_all_bug_page.php, but didn't find match.
Thank you.
custom states in 1.3.1
Moderators: Developer, Contributor
custom states in 1.3.1
Mantis Statistics Plugin: https://www.mantisstats.org
Re: custom states in 1.3.1
I don't have time to try this and have a deeper look at the moment.
I am not aware that we intentionally changed something around this.
Before reporting a bug, please double check that
- you copied custom_strings_inc.php to folder config
- you use $g_active_language to distinguish between languages in custom_strings_inc.php
I am not aware that we intentionally changed something around this.
Before reporting a bug, please double check that
- you copied custom_strings_inc.php to folder config
- you use $g_active_language to distinguish between languages in custom_strings_inc.php
Re: custom states in 1.3.1
Thanks a lot!
Copying custom_* files to config/ folder resolved my problem. Is there documentation somewhere on changes between MantisBT 1.2 and 1.3 so I can read before asking?
Copying custom_* files to config/ folder resolved my problem. Is there documentation somewhere on changes between MantisBT 1.2 and 1.3 so I can read before asking?
Mantis Statistics Plugin: https://www.mantisstats.org
Re: custom states in 1.3.1
When upgrading from 1.2.x to 1.3.x follow the upgrade instructions where you are told to copy the configuration files to config folder
https://mantisbt.org/docs/master-1.3.x/ ... ll.upgrade
After upgrading or after a new installation, run the check script mentioned at https://mantisbt.org/docs/master-1.3.x/ ... postcommon
Running this script would have told you that there are custom_* files on the old location.
Worth reading as a rough summary, the release announcement of 1.3.0 https://www.mantisbt.org/blog/?p=440
For a more detailed list of changes, have a look at the change log of all 1.3.x versions starting from 1.3.0-beta.1 https://www.mantisbt.org/bugs/changelog_page.php
There you will find https://www.mantisbt.org/bugs/view.php?id=16850 for the introduction of the config folder.
https://mantisbt.org/docs/master-1.3.x/ ... ll.upgrade
After upgrading or after a new installation, run the check script mentioned at https://mantisbt.org/docs/master-1.3.x/ ... postcommon
Running this script would have told you that there are custom_* files on the old location.
Worth reading as a rough summary, the release announcement of 1.3.0 https://www.mantisbt.org/blog/?p=440
For a more detailed list of changes, have a look at the change log of all 1.3.x versions starting from 1.3.0-beta.1 https://www.mantisbt.org/bugs/changelog_page.php
There you will find https://www.mantisbt.org/bugs/view.php?id=16850 for the introduction of the config folder.