View Issue Details

IDProjectCategoryView StatusLast Update
0028515mantisbtcustom fieldspublic2022-01-05 14:53
Reportermdkhamruddin Assigned Todregad  
PriorityhighSeverityblockReproducibilityalways
Status closedResolutionno change required 
Product Version2.24.1 
Summary0028515: APPLICATION ERROR 0001300 Custom field not found.
Description

Hello Team

Facing issue with Mantis Custom field, kindly help

TagsNo tags attached.

Relationships

has duplicate 0028521 closeddregad APPLICATION ERROR 0001300 Custom field not found. 
related to 0029413 closeddregad APPLICATION ERROR 1300 Custom field not found with case-sensitive database 

Activities

dregad

dregad

2021-05-06 13:36

developer   ~0065478

mdkhamruddin,

The provided information is not sufficient to provide any help in resolving the issue. A complete and detailed description is required for the support team to get a clear understanding of the problem.

Please explain what you do, what are the results you expect to get and what you actually get.

Also provide detailed, step-by-step instructions to reproduce the issue; the additional information listed below may also be useful:

  • Exact version of MantisBT, PHP, Database, Web server, Browser and Operating System
  • Relevant customizations (e.g. changes in config_inc.php, etc)
  • Installed plugins or custom functions ?
  • Was the MantisBT source code modified in any way ?
mdkhamruddin

mdkhamruddin

2021-05-07 04:59

reporter   ~0065483

Hello Dregad

While try to access Manage Custom Fields( manage_customfield_page.php ) kindly check below snip attached

1)
.Ubuntu ( server)
.MantisBT Version 2.24.1
.Schema Version 210
.PHP Version 7.1.33-25+ubuntu16.04.1+deb.sury.org+1
.Database Driver mysqli
.Database Version, Description 10.4.17, 10.4.17-MariaDB-1:10.4.17+maria~xenial
.Browser ( Mozilla, chrome, internet explorer ,Microsoft edge

2)Relevant customizations nothing done

3) plugin using
Avatars via Gravatar 2.24.1
Import/Export issues 2.24.1
Inline column configuration 2.0.0
jQuery UI Library 1.12.1
Linked custom fields 1.0.1
Mantis CSV Importer 2.0.0
Mantis Graphs 2.24.1
MantisBT Core 2.24.1
MantisBT Formatting 2.24.1

4) MantisBT source code not modified

image-2.png (21,269 bytes)   
image-2.png (21,269 bytes)   
image-3.png (18,989 bytes)   
image-3.png (18,989 bytes)   
dregad

dregad

2021-05-07 11:07

developer   ~0065485

You missed the most important bit of information

Please explain what you do, what are the results you expect to get and what you actually get.

Also provide detailed, step-by-step instructions to reproduce the issue;

As for

2)Relevant customizations nothing done

Really ? I would expect at least information about your custom field.

mdkhamruddin

mdkhamruddin

2021-05-09 12:18

reporter   ~0065492

1)
i tried looking at the error logs on the server, but for whatever reason, it doesn’t appear that errors are getting logged. I also tried removing various customizations from the configuration files, but that also did nothing (i hopefully put everything back the way it was before after my experiment)

i suspect that the custom field configurations are stored in the database

2)please check the snip from working mantis site ( are you looking for more info ?)

image.png (90,569 bytes)   
image.png (90,569 bytes)   
mdkhamruddin

mdkhamruddin

2021-06-09 08:11

reporter   ~0065617

any luck for me ?

dregad

dregad

2021-06-09 11:39

developer   ~0065618

Luck has nothing to do with it. Start by answering 0028515:0065485

mdkhamruddin

mdkhamruddin

2021-07-27 19:39

reporter   ~0065717

Hello

thanks for replying to the person who has manging the mantis has left the organisation ,sorry no information on this

can you please assist how to fix this

kent.mcneill

kent.mcneill

2021-12-01 08:10

reporter   ~0066055

the issue had to do with records in the mantis_custom_field_project_table that referenced field_id values that didn’t exist in the mantis_custom_field_table - this is presumably some sort of missing RFI in the Mantis schema… but the simple solution was simply to delete these invalid mappings from the association table.

no idea how the orphaned mappings got in there in the first place.

dregad

dregad

2021-12-01 09:00

developer   ~0066056

Thanks for the feedback. I'll resolve this as "no change required" then.