Mantis Bug Tracker - Forums

Vielen Dank allen für eure Hinweise. Ich glaube, ich hab's wieder im Griff. Es waren ein paar .htaccess-Rechts zu stramm.

Liebe Leute,
ich habe heute meinen alten mantisBT 1.3.x zur Seite gelegt, ein neues Mantis installiert, meine /config/config_inc.php rüberkopiert und die Datenbank erfolgreich aktualisiert. Der neue mantisBT zeigt mir alles an, aber anscheinend ohne jegliches CSS, obwohl im Source der Seiten alles ...

I now have moved the /core, /lang, and /library folders outside the web root and have adjusted the /config/config_inc.php accordlingy:

$g_core_path = '/<somewhereOutsideWebRoot>/share/MantisBT/core/';
$g_class_path = '/<somewhereOutsideWebRoot>/share/MantisBT/core/classes/';
$g_library_path ...

Thank you for your quick reply, but it doesn't help me much.

When you check the warning texts, they are kind of irritating:
core_path configuration option is set to a path outside the web root
For increased security it is recommended that you move the core_path directory outside the web root ...

Now that I have successfully switched to mantis 1.3, I get some warnings which I wasn't aware of before:

Paths
core_path configuration option is set to a path outside the web root
For increased security it is recommended that you move the core_path directory outside the web root.

class_path ...

I have opened a dispute on Trustwave's scan report and marked this issue to be "false positive". Still waiting for their reply.

I run Mantis (v1.2.8, Schema 183) on a website which is scanned regularly by Trustwave due to security reasons for credit card handling. Everytime the scan fails because of this issue:

Virtual Hosts: http://www.dsd.net
Session Cookie: MANTIS_secure_session
URL: /bugs/login.php

Details:
Ruby on ...

I am now checking all files against my previous version and found an issue in /core/cfdefs/cfdef_standard.php:

It misses the closing PHP tag ?> at the very end. I am quite sure this is a minor issue, but didn't anyone else note this?

So here is the solution:

NEVER simply copy old files over new files. :(

After I have checked my files, I saw that the /core/ folder contained some outdated subfolders, like /adodb/, which has been moved to the /library/ folder somewhen in the past by the developers.

After I had removed these ...

This issue seems to be silly, as it seems to be caused by a hard-coded version string in /core/adodb/adodb.inc.php:
$ADODB_vers = 'V4.94 23 Jan 2007 (c) 2000-2007 John Lim (jlim#natsoft.com.my). All rights reserved. Released BSD & LGPL.';

This string seems to be compared with my current version ...

Maybe my note wasn't clear for others:

I'd like to know how I can get rid of the warning that the adodb version seems to be inappropriate. Any hints?

I am running Mantis 1.2.8 on a current Ubuntu server. When I call <myMantis>/admin/check.php, it tells me:

Checking your installation
Checking adodb version...
V4.94 23 Jan 2007 (c) 2000-2007 John Lim (jlim#natsoft.com.my). All rights reserved. Released BSD & LGPL. WARN
Database Type (adodb) mysql ...

I believe you won't get more than a fix for Mantis 1.0.6 as the developers are busy switching to a general UTF solution for all languages (which is really neccessary).

Try and convert your strings_<language>.txt file into real UTF format and change the variable $s_charset into "UTF-8".

I guess ...

@psv: I looked for a solution to the same question like you did. - But now I found a rather simple one:

Review your Mantis database in MySQL and take a look at the table 'mantis_project_version_table'. You will see your version entries there. There are used sorted by DATE in the 'Change Log' pages ...