View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0007077mantisbtbugtrackerpublic2006-05-12 05:422006-09-12 00:54
ReporterLuebbe Assigned Tovboctor  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionduplicate 
PlatformFirefox / XPOSSuse LinuxOS VersionApache 2
Product Version1.0.3 
Summary0007077: Application warning 403 when changing status to resolved
Description

When I change a bugs status from any status to resolved, I see an "APPLICATION WARNING #403: database field not found" error after entering the reason for resolving. No database field is given.

When I do this from the details view I get only that error. When I resolve from the list view, an "APPLICATION ERROR #18 please use the back button..." is shown below the menu.

The application warning 403 is only shown (briefly), when the status is changed to resolved. No warning is shown when the status changes from any status to any other status than resolved.

Steps To Reproduce

The default localization is German. When I switch to english, the warning changes to: "APPLICATION WARNING #403: Database field 'fixed_in_version' not found."

and the Application error changes to:

"APPLICATION ERROR #18

Page redirection error, ensure that there are no spaces outside the PHP block (<?php ?>) in configinc.php or custom*.php files."

I can't find any spaces outside the PHP block. Where else should I look?

Additional Information

Server is running Suse linux 9.2, apache 2.0, mysql 3.23.

I have upgraded from mantis 0.19.2 to 1.0.3 yesterday udsing the upgrade scripts, so I assume that the databas schema should be correct.

We are not using any custom field in the database.

TagsNo tags attached.

Relationships

duplicate of 0007027 closedvboctor Port: fixed_in_version is renamed to Fixed_in_version during database migration 

Activities

Luebbe

Luebbe

2006-05-12 05:51

reporter   ~0012820

I found it: In mantis_bug_table the field "fixed_in_version" is spelled "Fixed_in_version" with a capital "F".

I checked my dumpfile from the 19.2 release and the field name is spelled correctly there. This leads to the conclusion that the upgrade script has messed the field name up.

After fixing the field name, the application error is gone.
Luebbe

Luebbe

2006-05-15 06:24

reporter   ~0012835

Just noticed that this is probably a duplicate of 0007027