#3642 closed defect (duplicate)
Error Creating Custom Ticket Fields
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | devel |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Using 0.10b1..
Adding the following to trac.ini:
[ticket-custom] custom_1 = select custom_1.label Module custom_1.options All|Catalog Front|Administration Tool|Installation Module custom_1.value 0
Created the following error:
arsingError: File contains parsing errors: /home/svn/trac/conf/trac.ini [line 90]: 'custom_1.label Module\n' [line 91]: 'custom_1.options All|Catalog Front|Administration Tool|Installation Module\n' [line 92]: 'custom_1.value 0\n'
append = <bound method ParsingError.append of File contai...ation Module\n' [line 92]: 'custom_1.value 0\n'>
args = ('File contains parsing errors: /home/svn/trac/conf/trac.ini',)
errors = [(90, r"'custom_1.label Module\n'"), (91, r"'custom_1.options All|Catalog Front|Administration Tool|Installation Module\n'"), (92, r"'custom_1.value 0\n'")]
filename = '/home/svn/trac/conf/trac.ini'
message = "File contains parsing errors: /home/svn/trac/con...lation Module\\n'\n\t[line 92]: 'custom_1.value 0\\n'"
Looking closer at TracTicketsCustomFields shows that no "label" field is available for "select", even though it is shown as an example below it.. removing the "label" line produced a similar error.
After removing the lines from trac.ini I am left with am empty select pull down menu on the new ticket page. My second issue is how can this empty box be removed?
Thanks for your time! I hope this fixes another bug for the final 0.10 release!
Attachments (0)
Change History (3)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
The parsing error is because you didn't put an "=" between the settings and their values.
Regarding deleting custom fields see #2099. Currently removing the custom field settings isn't picked up until the server is restarted.
comment:3 by , 19 years ago
Thanks for the clarification. I do not believe I had overlooked that. Thanks for your time on this, it is much appreciated.



Update: the emty pull down menu seems to have automagically removed itself after a minute..