Anonymous | Login | Signup for a new account | 2012-09-13 19:33 PDT |
Main | Blog | My View | View Issues | Change Log | Roadmap | IRC Chat | Repositories | Scrum Board |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
162 | Source Integration | [All Projects] General | public | 2010-06-16 10:03 | 2011-04-07 09:29 | ||||||
Reporter | mmokluk | ||||||||||
Assigned To | |||||||||||
Priority | normal | Severity | block | Reproducibility | always | ||||||
Status | new | Resolution | open | ||||||||
Product Version | |||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 162: APPLICATION ERROR #2503 Upgrading the plugin schema failed in block #0. | ||||||||||
Description | I get this error when attempting to install Source Control Integration 0.16.1 on a 1.2.1 release of MantisBT. Then when I click on the plugin link, I see all kinds of errors like: APPLICATION WARNING 100: Configuration option "plugin_Source_remote_checkin" not found. APPLICATION WARNING 100: Configuration option "plugin_Source_checkin_urls" not found. APPLICATION WARNING 100: Configuration option "plugin_Source_remote_imports" not found. APPLICATION WARNING 100: Configuration option "plugin_Source_import_urls" not found. and also a Fatal error: Class 'SourceVCS' not found in /var/www/tracking-upgrade/plugins/Source/pages/manage_config_page.php on line 173 | ||||||||||
Steps To Reproduce | Install Source Control Integration 0.16.1 on a 1.2.1 release of MantisBT. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
|
mmokluk (reporter) 2010-06-28 13:31 |
This no longer occurs for me after downloading and installing the latest snapshot. |
mmokluk (reporter) 2010-06-28 14:36 |
Actually, I take that back. I think it was a database server configuration change. I need to isolate further. |
mmokluk (reporter) 2010-07-20 08:04 |
It seems this was caused by having my mantis database located on a VM (Oracle Virtual Box). I could run Mantis, but the plugin would not install properly. I moved the database off to a non-VM machine and the problem disappeared. |
Karl Reichert (reporter) 2011-04-07 09:29 |
This is a duplicate of 171 I faced the same error (Upgrading the plugin schema failed in block #0.) but I know how to fix it! First, you should uninstall the plugin, if installed, via the Manage Plugins page in Mantis. Then, you should change line 22 in file Mantis\plugins\Source\Source.php to the Mantis version you are using: 'MantisCore' => '1.2.5', (However, this step seems to be not really necessary, but will prevent Mantis to report a need for update at Manage plugins page.) After that, make sure your Mantis _DatabaseUser_ (which you specified when you installed Mantis the first time) has _full_ rights to the bugtracker database. It normally needs only SELECT, INSERT, UPDATE and DELETE rights (see http://docs.mantisbt.org/master/en/administration_guide.html#ADMIN.INSTALL [^]), but you must temporary enable him to have all rights to the database. Now you can install the plugin via the Manage Plugins page in Mantis. You will not be faced with any error messages. After successful installation, you can now reduce the right of Mantis database user as it was before (SELECT, INSERT, UPDATE and DELETE rights to bugtracker database will be sufficient). I hope this will be fixed by John in the next plugin version! |
![]() |
|||
Date Modified | Username | Field | Change |
2010-06-16 10:03 | mmokluk | New Issue | |
2010-06-28 13:31 | mmokluk | Note Added: 228 | |
2010-06-28 14:36 | mmokluk | Note Added: 229 | |
2010-07-20 08:04 | mmokluk | Note Added: 233 | |
2011-04-07 09:29 | Karl Reichert | Note Added: 282 |
Copyright © 2000 - 2012 MantisBT Group
Time: 0.1513 seconds. memory usage: 8,396 KB |