View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0032953mantisbtmigrationpublic2023-09-19 11:482023-10-06 06:52
Reporterjmelendez Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2.25.7 
Summary0032953: migration from mantis version 2.22.0 to 2.25.7
Description

In a test environment I have been migrating Mantisbt versions and when I go to migrate to version 2.25.7 I encounter an error as an administrator user in the Manage Custom Fields part, the errors are the following, Attachment screenshot:

SYSTEM NOTICE: 'Undefined index: name' in 'C:\xampp\htdocs\mantisbt-2.25.7\core\utility_api.php' line 175

SYSTEM NOTICE: 'Undefined index: id' in 'C:\xampp\htdocs\mantisbt-2.25.7\manage_custom_field_page.php' line 96"
SYSTEM NOTICE: 'Undefined index: id' in 'C:\xampp\htdocs\mantisbt-2.25.7\manage_custom_field_page.php' line 98
SYSTEM NOTICE: 'Undefined index: type' in 'C:\xampp\htdocs\mantisbt-2.25.7\manage_custom_field_page.php' line 99
SYSTEM NOTICE: 'Undefined index: possible_values' in 'C:\xampp\htdocs\mantisbt-2.25.7\manage_custom_field_page.php' line 104
SYSTEM NOTICE: 'Undefined index: default_value' in 'C:\xampp\htdocs\mantisbt-2.25.7\manage_custom_field_page.php' line 105

I also ran /admin/check/index.php and it only gave me warnings. Could it be that some of those warnings gave me those errors? Attachment screenshot.

The only error that appears in this version is the one mentioned above; The rest of this version works perfectly. Do you have any idea what could be happening?

If you need any other information that can help us resolve this issue, let me know and I will send it to you.

TagsNo tags attached.
Attached Files
Error_2_25_7.jpg (205,793 bytes)   
Error_2_25_7.jpg (205,793 bytes)   
Error(2)_2_25_7.jpg (206,380 bytes)   
Error(2)_2_25_7.jpg (206,380 bytes)   

Activities

jmelendez

jmelendez

2023-09-19 11:59

reporter   ~0068124

By clicking on the link that gives me the error, the following appears:

Error(3)_2_25_7.jpg (46,947 bytes)   
Error(3)_2_25_7.jpg (46,947 bytes)   
jmelendez

jmelendez

2023-09-19 13:12

reporter   ~0068125

I add that I am using the following version of XAMPP:

  • Apache 2.4.46
    • MariaDB 10.4.14
    • PHP 7.2.34 (VC15 X86 64bit thread safe) + PEAR
    • phpMyAdmin 5.0.3
    • OpenSSL 1.1.0g
    • ADOdb 518a
    • Mercury Mail Transport System v4.63 (not included in the portable version)
    • FileZilla FTP Server 0.9.41 (not included in the portable version)
    • Webalizer 2.23-04 (not included in the portable version)
    • Strawberry Perl 5.32.0.1 Portable
    • Tomcat 7.0.106
    • XAMPP Control Panel Version 3.2.4.
dregad

dregad

2023-09-20 05:14

developer   ~0068126

By clicking on the link that gives me the error

I'm guessing you mean the link in the Custom Fields table's first row, name column (that opens manage_custom_field_edit_page.php),
If so, it would be good to know what actual value it being passed in the field_id parameter (should be an integer, but apparently it's not).

I think something's fishy with at least one of your custom field definitions.

Can you do add a var_dump($t_all_ids, $t_all_defs); at line 63 (just before the multi_sort() call).
Also check what you have in the custom_fields table.
jmelendez

jmelendez

2023-09-22 09:21

reporter   ~0068128

Dear friends, I was able to fix the error in the following way. I brought the custom_field_api.php file from the previous version and replaced it with the one from the current version (version 2.25.7), after refreshing the page the error disappeared. For some reason when making this file change no more error was reflected, I have been browsing all the Mantis tabs and it behaves perfectly. I assume there will be some function in that file that changes when I update the version. I think we can consider this Mantis closed. Thank you very much for your willingness and help. Best regards
dregad

dregad

2023-09-22 11:17

developer   ~0068129

Thanks for the feedback, good to hear you managed to fix the problem.