View Issue Details

IDProjectCategoryView StatusLast Update
0012885mantisbtadministrationpublic2014-12-08 02:07
Reporterdhx Assigned Todregad  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Product Version1.3.0dev 
Target Version1.3.0-beta.1 
Summary0012885: Reimplement obsolete configuration checks based on obsolete.php as part of new admin/check/ interface
Description

The rewritten check.php script (as a collection of checks in the admin/check/ directory) neglected to port across obsolete configuration checking from 1.2.x.

Configuration within the database (and perhaps also as defined in global PHP variables) needs to be validated against obsolete.php to notify the user if they're trying to use deprecated configuration options.

TagsNo tags attached.

Relationships

related to 0013435 closeddregad The obsolete checks should also verify configs in the db 
related to 0011576 closeddhx New and improved check.php for checking MantisBT installation settings/environment 
related to 0015721 closedgrangeway Functionality to consider porting to master-2.0.x 
related to 0012884 closeddhx Checks for obsolete config fails to report error 
related to 0015838 closedatrol new check.php does not check for obsolete config variables 

Activities

dregad

dregad

2011-11-19 17:12

developer   ~0030252

Implementation of check for configuration within the database (mantis_config_table) is tracked in 0013435.

grangeway

grangeway

2013-04-05 17:57

reporter   ~0036395

Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch

grangeway

grangeway

2013-05-12 08:07

reporter   ~0036834

Damien,

This needs a fix in the master branch - as per comment on the 2.x version in issue 0015838.

a) project_get_name can throw an exception breaking the script
b) database is not necessarily loaded at this point

dregad

dregad

2013-05-13 11:22

developer   ~0036851

You're confusing me. The whole point of this commit was to fix the issue in the master branch to begin with.

a) master branch does not use exceptions so that point is moot.
b) Just tried this; not sure where the problem is. If there is no DB connectivity, the checks will just fail "cleanly"

<pre>
Database

Can open connection to database bugtracker on host localhost with username root FAIL
</pre>

From my perspective, this works as designed.

dregad

dregad

2013-05-13 11:22

developer   ~0036852

Reminder sent to: grangeway

Related Changesets

MantisBT: master d1cd06cd

2011-10-23 12:30

dregad


Details Diff
Reimplement obsolete config checks in admin/check interface

The rewritten check.php scripts (as a collection of checks in the
admin/check/ directory), implemented per issue 0011576 in commit
ba97560b02d620569ad062d894284722f0acd890, neglected to port across
obsolete configuration checking from 1.2.x.

Fixes 0012885
Affected Issues
0011576, 0012885
mod - admin/check/check_config_inc.php Diff File
mod - core/config_api.php Diff File