Mantis Bug Tracker - Forums

Is there a way to use a regular expression to parse the email subject line in order to put the new Mantis ticket into the correct Project automatically when the email is parsed? Instead of using a new email address for EVERY project we have, we would like to use a single email address and have the p...

In this settings screen: Issue reporter configuration options Use only default reporter user for issues created by email [?] Yes No Enable fallback to default reporter [?] Yes No The default / fallback reporter user for issues created by email [?] Signup new users automatically (possible security ri...

Windows Server 2012 R2 PHP 5.6 Mantis 2.7.0 Created new directory for new version, installed archive, copied over config files including custom_ files in config directory and after minor config tweaks everything seems to be working great, except some of the tickets show @##@ where "##" is ...

After installation you browse to to test your installation and one of those items says to get rid of directories you don't need.

SOLVED! The issue was that the directions for installing MantisBT say to remove the api directory if you aren't using SOAP so I deleted that directory. It appears that the EmailReporting plugin needs code in that directory. I suggest that the documentation for the plugin be updated to indicate that ...

Image of error screen is below. The Mantis user for SQL access has proper permissions because when I click the [Install] button to install the plugin, and after the error I go look at the database, it has created the emailreporting plugin table. So unless there is some other permission it needs, the...

Sorry. Windows Server 2012R2. EmailReporting plugin version is the latest available 0.10.0. This was an upgrade of Mantis from 1.3.5 to 2.7.0 in production, after I had upgraded our development server from 1.5.3 to 2.6.0 previously, and we tested it for weeks. The plugin was NOT installed in our pro...

PHP 5.6 Mantis 2.7.0 APPLICATION ERROR #2503 Upgrading the plugin schema failed in block #1. Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click a...

Also check your browser console for any error messages.

Has anyone attempted (or successfully) integrated Orchestrator with mantis? Ref: https://msdn.microsoft.com/en-us/library/hh921667.aspx just wondering so I won't have to reinvent wheels...thanks!

Fully solved. It was an extension in Chrome: Win 7 Scrollbars available in the Store even. Not updated since 2014, apparently it really messes with Chrome internals. I removed it and now have zero console errors. Just putting all this info in the thread in case it helps someone later!

One more thing I had to do was edit the web.config file in the base program directory and add the following sections: <fileExtensions> <add fileExtension=".svg" allowed="true" /> <add fileExtension=".woff" allowed="true" /> <add fileExtension=".woff2"...

HOWEVER I'm still getting errors in the Chrome console, any ideas on these? I think it has something to do with the default theme: my_view_page.php:1 Refused to load the image 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAABCAIAAAC32dI2AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAChJR...

Figured it out! Because the new Mantis requires at least version 5.5 of PHP, I upgraded from 5.3 but failed to enable LDAP support, which is a separate operation it seems. Good grief. That's what I get for not being a PHP coder...everything seems to be working great now. I have no clue about the CSP...

So I'm a bit closer. In Chrome's developer window it said there are 13 errors. I opened an incognito browser tab and loaded the page, and it said I had only 4 errors. So I'm thinking there's some browser extension causing errors on the page, but still not sure why the previous version of Mantis didn...