View Issue Details

IDProjectCategoryView StatusLast Update
0004328mantisbtadministrationpublic2004-11-06 06:55
ReporterErkDog Assigned Tothraxisp  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version0.18.3 
Summary0004328: Unable to Properly modify Severity List.
Description

I have copied the line
$g_severity_enum_string = '10:trivial,20:tweak,30:minor,40:major,50:crash';

from the config_inc_defaults to my config_inc file

that is my edited version.

However Mantis is still associating 10 with Feature 20 with Trivia 30 is Text IE It's not readin the Enum list right.

Text and Feature are not even IN the above list.

TagsNo tags attached.

Relationships

related to 0004466 closedthraxisp Problem with custom strings and workflows 
child of 0004350 closeddhx FAQ 

Activities

vboctor

vboctor

2004-08-15 19:33

manager   ~0006999

Checkout the following article in the manual and letting me know if you still have issues:
http://manual.mantisbt.org/manual.customizing.mantis.enumerations.php

ErkDog

ErkDog

2004-08-15 20:56

reporter   ~0007001

Last edited: 2004-08-15 20:57

$g_severity_enum_string = '11:trivial,21:tweak,31:minor,41:major,51:crash';

I have that set in my config_inc.php
I decided to add 1 to the numbers, because even when I set the new constants it still showed the same first 5

Here is the contents of my custom_constant_inc.php
<?php

    define( 'TRIVIAL',      11 );
    define( 'TWEAK',        22 );
    define( 'MINOR',        33 );
    define( 'MAJOR',        44 );
    define( 'MAJOR',        55 );

?>

which is clearly being read becuase NOW when I go to report bug it says
@11@
@21@
@31@
@41@
@51@
and isn't showing the things from the enum list listed in config_inc.php
lol and now my View Bugs list shows

@50@
@20@
@10@ etc, the old values, without any text associated

edited on: 08-15-04 20:57

thraxisp

thraxisp

2004-08-15 21:18

reporter   ~0007002

You also need to change $s_severity_enum_string in a custom_strings.php file.

We need to update the documentation for this.

ErkDog

ErkDog

2004-08-15 21:37

reporter   ~0007003

works good guys, thanks :)

Wanderer

Wanderer

2004-08-15 23:20

developer   ~0007004

Last edited: 2004-08-15 23:21

With g_active_language in custom_strings full customisation works...

edited on: 08-15-04 23:21

Wanderer

Wanderer

2004-08-24 12:21

developer   ~0007136

$g_severity_enum_string = '11:trivial,21:tweak,31:minor,41:major,51:crash';
I have that set in my config_inc.php
And you have to mirror it for all (all !!!) languages into
custom_strings_inc.php

I can advertise again my demo-site :-) and show my custom* files to everybody

jvh

jvh

2004-09-01 17:41

reporter   ~0007380

i'm also having this problem in 19.0rc1

thraxisp

thraxisp

2004-09-01 18:02

reporter   ~0007382

With the fix I made for 0004448, you can cheat on the string definitions. It is possible to use the string definition for multiple languages. For example:


if ( $g_active_language == 'french' ) {
$s_severity_enum_string = '11:simple,22:cosmÈtique,31:mineur,41:majeur,51:crash';
}else{ # all other languages
$s_severity_enum_string = '11:trivial,21:tweak,31:minor,41:major,51:crash';
}

vboctor

vboctor

2004-09-01 18:21

manager   ~0007383

Starting 0.19.0rc1, the lang_get_current() function should be used in custom_strings_inc.php rather than $g_active_language or any previous direct access to a global variable.

Wanderer

Wanderer

2004-09-01 20:01

developer   ~0007386

Well, it works with old form yet, and - can you provide example of new form?
Instead of
if ( $g_active_language ==
I have to write
if (lang_get_current() ==

yes
?

thraxisp

thraxisp

2004-09-02 01:11

reporter   ~0007390

correct.

thraxisp

thraxisp

2004-09-14 18:29

reporter   ~0007583

This information has been added to the "Customizing Enumerations" section of the manual source.