v1.0.0a3 - custom_fields problems

[corseman]

Hi,

I just upgrade my mantis version to the v1.0.0a3 and I found a problem regarding the custom field function.
Description: In Management\Custom field, I add a new custom field (wich is an enumeration field) and click on update.
The next page shown was "operation successfull".

But when I came back to the custom fields list I did not see the new field.
I checked in the db and the custom field is in the mantis_custom_field table (with the value I setup).

Thanks for any help.

Corseman

[corseman]

I found a workaround in the bugtracker (issue 0005696).
Below the workaround I had applied:

In CORE/, edit the custom_field_api.php file.
Line 628: add to the FROM condition "$t_custom_field_project_table as cfpt" (ie you should have: FROM $t_custom_field_table as cft, $t_custom_field_project_table as cfpt).

Then comment the line 629: JOIN $t_custom_field_project_table as cfpt on cft.id = cfpt.field_id.

This workaround worked for me.

Hope this post can help.

Thanx to eurayle ;)

Corseman

[guest]

I tried the solution described:

In CORE/, edit the custom_field_api.php file.
Line 628: add to the FROM condition "$t_custom_field_project_table as cfpt" (ie you should have: FROM $t_custom_field_table as cft, $t_custom_field_project_table as cfpt).

Then comment the line 629: JOIN $t_custom_field_project_table as cfpt on cft.id = cfpt.field_id.

but is does not work for me. I see the fields in the db but list no joy :(

Any ideas?

thanks

Rob

[illes]

0005712: Entered custom fields are not stored into the database at status change
http://bugs.mantisbt.org/view.php?id=5712 [^]
--
Fixed in CVS. Added optional CFs displayed at resolve or close to bug_update.
bug_update.php -> 1.86