This control will replace the user's userid with their realname. If it is set to ON, and the real name field has been populated, the replacement will occur. It defaults to OFF. In addition to enabling this configuration option it is necessary to install an avatar plugin like the Gravatar plugin which is bundled out of the box.
Note that the threshold is related to the user for whom the avatar is being shown, rather than the user who is currently logged in. Default is 1 year. Allow users to opt for a 'permanent' cookie when logging in. Controls the display of the 'Remember my login in this browser' checkbox on the login page. Time to delay between page redirects in seconds. Users can override this setting in their user preferences. Default is 2 seconds.
This timeout is used by pages which does time consuming operations like upgrading the database. The default value of 0 disables timeout. Note that this timeout is specified in seconds. These variables control how the date is displayed. The default is ISO formatting. Please refer to the PHP manual for details on available formatting options.
Default is Y-m-d. Default is Y-m-d H:i. This format is used on the top of each page current time and the emails that are sent out. Default is Y-m-d H:i T. This format is used with the datetime picker widget.
The formatting convention for the DateTime picker is different from the one used for the other date settings described above; see Moment. Inconsistencies between these two settings, e.
Time Zone. This configuration is normally initialized when installing Mantis. It should be set to one of the values specified in the List of Supported Timezones. Correct configuration of this variable can be confirmed by running the administration checks.
Users can override the default timezone under user their preferences. These options are used to control the query that selects the news entries to be displayed. The default is OFF. The news feature is deprecated in favor of being moved to a plugin. The limit for the number of news entries to be displayed. Specifies the number of dates after which the news are not displayed. Specifies the access level required to view private news. Default Preferences.
Default value for bug description field used on bug report page. Default is empty description. Default value for bug additional info field used on bug report page.
Default is empty. Default value for bug steps to reproduce field used on bug report page. Threshold for viewing timeline information. If the timeline is turned off, the other widgets are displayed in a two column view. The minimum access level for a user to show up in the reminder user picker.
Note that this is the access level for the project for which the issue belongs. The resolution for a newly created issue. The default is OPEN. The severity for a newly created issue. The priority for a newly created issue. The reproducibility for a newly created issue. The projection for a newly created issue. The ETA for a newly created issue. Default global category to be used when an issue is moved from a project to another that doesn't have a category with a matching name.
The default is 1 which is the "General" category that is created in the default database. Highlight bugs that have changed during the last N hours. The default value is 6. Controls which issues will be displayed in the View Issues page. This is the delay between automatic refreshes of the View Issues page in minutes. Make sure refresh delay in user preferences isn't too short. If a users set their preferences to be lower then it is bumped back up to this minimum value.
The default value is 10 minutes. These settings are used as the default values for preferences for new users. Each user can override these settings through the user preferences form. This is for the bug listing pages. Default value is 30 minutes. Default delay before a user is redirected to a page after being prompted by a message eg: operational successful.
Default value is 2 seconds. This controls the time order in which bug notes are displayed. Default user preferences to enable receiving emails when a bug is set to the corresponding status. This option only has an effect if users have the required access level to receive such emails.
Default value is ON. Default user preferences to enable receiving emails when bugs are re-opened. Default user preferences to enable receiving emails when bugnotes are added to bugs. Default user preferences to enable receiving emails when status is changed. Default user preferences to enable receiving emails when priority is changed.
Default user preferences to enable filtering based on issue severity. Default is 'any'. Default user preference to enable filtering based on issue severity. See also: Section 7. These are the settings that are used to configuration options related to the Summary page.
This page contains statistics about the bugs in MantisBT. This is useful when there are dozens or hundreds of reporters. The default value is An array of date lengths to count bugs by in days for the summary by date. The default is to count for 1, 2, 3, 7, 30, 60, 90, , and Specifies whether category names should be preceded by project names eg: [Project] Category when the summary page is viewed for all projects.
This is useful in the case where category names are common across projects. Specifies the access level required to view the summary page. An array of multipliers which are used to determine the effectiveness of reporters based on the severity of bugs. Higher multipliers will result in an increase in reporter effectiveness.
The values are integers, typically in the range of 0 to If you would like for a severity to not count towards effectiveness, set the value to 0 for that severity. An array of multipliers which are used to determine the effectiveness of reporters based on the resolution of bugs. Higher multipliers will result in a decrease in reporter effectiveness. Resolutions not included here will be assumed to have a multiplier value of 0.
If you would like for a resolution to not count towards effectiveness, set the value to 0 for that resolution or remove it from the array completely. Note that these resolution multipliers are stacked on top of the severity multipliers. The default value is ASC. File Upload. MantisBT allows users to upload file attachments and associate them with bugs as well as projects. When bugs are uploaded to the webserver they are uploaded to the path that is configured in the project properties.
In case of problems getting the file upload feature to work, check the following resources: PHP Manual. Specify the location for uploading attachments. In case of DISK methods you need to provide the webserver with write access rights to the configured upload path configured in the project and temporary upload path used by PHP.
Maximum number of files that can be uploaded simultaneously. Default value is Maximum file size that can be uploaded. Default value is about 5 MiB. Files that are allowed. Separate items by commas. Files that are not allowed. It is recommended to disable all extensions that can be executed by your server. If the attachment size is smaller than the specified value, the attachment is previewed with the issue details.
The previewing can be disabled by setting this configuration to 0. An array of file extensions not including dots for text files that can be previewed inline.
An array of file extensions not including dots for image files that can be previewed inline. Specify the filename of the magic database file. Usually it is safe to leave this setting as the default blank as PHP is usually able to find this file by itself.
Enable support for sending files to users via a more efficient X-Sendfile method. The name of the X-Sendfile header to use. Each server tends to implement this functionality in a slightly different way and thus the naming conventions for the header differ between each server.
Lighttpd from v1. This is the list of HTML tags that are allowed. Do NOT include href or img tags here. Do NOT include tags that have parameters eg. The HTML code is allowed to enter the database as is. The package will automatically hyperlink properly formatted URLs eg. Specifies a file to be included at the bottom of each page. It can be used e. Specifies a file to be included at the top of each page. A flag that indicates whether to use CDN content delivery networks for loading javascript libraries and their associated CSS.
This improves performance for loading MantisBT pages. This can be disabled if it is desired that MantisBT doesn't reach out outside corporate network.
Default OFF. This option will add custom options to the main menu. It is an array of arrays listing the caption, access level required, and the link to be executed. Options will only be added to the menu if the current logged in user has the appropriate access level. Use icons from Font Awesome. Add "fa-" prefix to icon name. Access level is an optional field, and no check will be done if it is not set. Icon is an optional field, and 'fa-plug' will be used if it is not set.
Global authentication parameters. It should be one of the following values defaults to MD5 : MD5 - user's password is stored as a hash in the database. PLAIN - password is stored in plain, unencrypted text in the database. Note: you may not be able to easily switch encryption methods, so this should be carefully chosen at install time. However, MantisBT will attempt to "fall back" to older methods if possible. Determines whether MantisBT will require the user to re-authenticate before granting access to the Admin areas after timeout expiration.
Defaults to ON. Duration of the reauthentication timeout, in seconds. Defaults to 5 minutes. LDAP authentication method parameters. Port number is optional, and defaults to If this doesn't work, try using one of the following standard port numbers: ldaps ; for Active Directory Global Catalog forest-wide search, use ldap or ldaps. Multiple servers can be specified as a space-separated list.
An integer indicating the minimum version of the TLS protocol to allow. For security, a failure aborts the entire connection. The root distinguished name for LDAP searches. LDAP search filter for the organization. Defaults to '' empty string. If 0 , then the protocol version is not set, and you get whatever default the underlying LDAP library uses.
In almost all cases you should use 3. Defaults to 0 infinite. The distinguished name of the service account to use for binding to the LDAP server. Leave empty for anonymous binding. The password for the service account used to establish the connection to the LDAP server. For anonymous binding, leave empty. The LDAP field for e-mail address. Defaults to mail.
The LDAP field for the user's real name i. Defaults to cn. Defaults to OFF. This configuration option allows replacing the ldap server with a comma-delimited text file for development or testing purposes. No headers. On production systems, this option should be set to '' This is the default. Status Settings. Status to assign to the bug when feedback is required from the issue reporter. Default resolution to assign to a bug when it is resolved as being a duplicate of another issue.
Installations where assigned status is to be used when the defect is in progress, rather than just put in a person's queue should set it to OFF. For the status change to be effective, these conditions must be met: Bug has no handler, and a new handler is selected.
Bug is resolved, ready to be closed or reopened. Threshold resolution which denotes that a bug has been resolved and successfully fixed by developers. Threshold resolution which denotes that a bug has been resolved without being successfully fixed by developers. Resolutions above this threshold are considered to be resolved in an unsuccessful way.
For each existing status, you define which statuses you can go to from that status, e. The default is no workflow, where all states are accessible from any others.
This is the access level generally required to update the content of a bug. This is the access level generally required to be access level needed to be listed in the assign to field.
These settings control the access level required to promote a bug to a new status once the bug is opened. It defaults to blank. If set, the bug reporter is allowed to close their own bugs, regardless of their access level. If set, the bug reporter is allowed to reopen their own bugs once resolved, regardless of their access level.
This allows the reporter to disagree with the resolution. The default is ON. If set, no check is performed on the status of a bug's children, which allows the parent to be closed whether or not the children have been resolved. Controls the display of the filter pages.
This switch enables the use of AJAX to dynamically load and create filter form controls upon request. This method will reduce the amount of data that needs to be transferred upon each page load dealing with filters and thus will result in speed improvements and bandwidth reduction. The service to use to create a short URL.
See Wikipedia for more details about regular expressions. For testing regular expressions, use Rubular. Access level needed to show the list of users monitoring an issue. Access level needed to add other users to the list of users monitoring an issue. Access level needed to delete other users from the list of users monitoring an issue. Enable anonymous access to Mantis.
The default setting is OFF. Define the account which anonymous users will assume when using Mantis. This account is considered by Mantis to be protected from modification. Anonymous users will not be able to adjust preferences or change account settings like normal users can. When creating the account you should specify a password, email address and so forth in the same way you'd create any other account. The anonymous user account will not receive standard notifications and can not monitor issues.
If a number follows this tag it will create a link to a bug. Default is ' '. If a number follows this tag it will create a link to a bug note. Specifies whether to enable support for project documents or not. This feature is deprecated and is expected to be moved to a plugin in the future.
Threshold at which a user is considered to be a site administrator. These users have the highest level of access to your Mantis installation. This access level is required to change key Mantis settings such as server paths and perform other administrative duties. This is a potentially dangerous configuration option. With this access level, users can damage your installation of Mantis, destroy your database or have elevated access to your server. The threshold required for users to be able to manage configuration of a project.
This includes workflow, email notifications, columns to view, and others. Threshold for users to view the raw system configurations as stored in the database. Threshold for users to set the system configurations generically via MantisBT web interface. Users who have access to set configuration via the interface MUST be trusted. This is due to the fact that these users can leverage the interface to inject PHP code into the system, which is a potential security risk.
All scripts in this directory and its sub-directories will be able to access MantisBT cookies. It is recommended to set this to the actual MantisBT path. It applies to the cookies listed below. Their actual names are calculated by prepending the prefix, and it is not expected for the user to need to change these. Speed Optimisation. This option will be ignored in the following scenarios:.
The Windows version of PHP has built-in support for this extension. Use persistent database connections, setting this to ON will open the database once per connection, rather than once per page. There might be some scalability issues here and that is why it is defaulted to OFF. In the past, only selected users like the managers, or developers would get notified about bugs.
However, these people can not invite other people through MantisBT to look at or monitor these bugs. It avoid needing this person to do this manual outside MantisBT.
It also records the history of such reminders. The bugnote will still reflect that it is a reminder and list the names of users that got it. Specifies if users who receive reminders about a bug, should be automatically added to the monitor list of that bug.
Enables or disables the mentions feature. When a user is mentioned in an issue or a note, they receive an email notification to get their attention. Users can be mentioned using their username and not realname. This feature works with fields like summary, description, additional info, steps to reproduce and notes.
Bug History. Bug history is a feature where MantisBT tracks all modifications that are made to bugs. These include everything starting from its creation, till it is closed.
For each change, the bug history will record the time stamp, user who made the change, field that changed, old value, and new value. Independent of the these settings, MantisBT will always track the changes to a bug and add them to its history. If this option is not enabled, then the user will have to click on the Bug History link to see the bug history. Show bug history entries in ascending or descending order.
Default value is 'ASC'. These revisions are controlled by the following settings. Users can always see revisions for the issues and bugnotes they reported. The default os OFF. The minimum sponsorship amount that can be entered.
If the user enters a value less than this, an error will be flagged. The default is 5. The access level threshold needed to view the total sponsorship for an issue by all users.
The access level threshold needed to view the details of the sponsorship i. The access level threshold needed to allow user to sponsor issues. Note that sponsoring user must have their email set in their profile. The access level required to be able to handle sponsored issues.
Custom Fields. Access level needed to link a custom field to a project. This flag determines whether to start editing a custom field immediately after creating it, or return to the definition list.
The default is ON edit the custom field after creating. My View Settings. A box that is not to be shown can have its value set to 0. Default page to transfer to after Login or Set Project.
Relationship Graphs. MantisBT can display a graphical representation of the relationships between issues. Two types of interactive visualizations are available, dependencies and a full relationships graph. This feature relies on the external dot and neato tools from the GraphViz library, which must be installed separately. Most Linux distributions have a GraphViz package available for easy download and install.
Under Windows, the software needs to be installed manually. The following post-installation steps may be required for proper operations: Update the system PATH to point to GraphViz's bin directory. Initialize the graph engine by running dot -c from an Administrator command prompt.
Font name and size, as required by Graphviz. If Graphviz fails to run for you, you are probably using a font name that gd PHP extension can't find. On Linux, try the name of the font file without the extension. The default value is 'Arial'.
Default dependency orientation. If you have issues with lots of children or parents, leave as 'horizontal', otherwise, if you have lots of "chained" issue dependencies, change to 'vertical'.
Default is 'horizontal'. Max depth for relation graphs. This only affects relationship graphs, dependency graphs are drawn to the full depth. The default value is 2. If set to ON, clicking on an issue on the relationship graph will open the bug view page for that issue, otherwise, will navigate to the relationship graph for that issue.
The full path for the dot tool. The webserver must have execute permission to this program in order to generate relationship graphs. This configuration option is not relevant for Windows. The full path for the neato tool. Wiki Integration. The following Wiki Engine values are supported: dokuwiki : DokuWiki. Wiki namespace to be used as root for all pages relating to this MantisBT installation. Before turning this flag OFF, make sure all sub-projects are moved to top level projects, otherwise they won't be accessible.
The default value is ON. Whether sub-projects should inherit versions from parent projects. Whether sub-projects should inherit categories from parent projects. Field Visibility. Default value is OFF. The summary and description fields are always shown and do not need to be listed in this option.
Fields not listed above cannot be shown on the bug report page. An array of optional fields to show on the issue view page and other pages that include issue details.
Fields not listed above cannot be shown on the bug view page. Fields not listed above cannot be shown on the bug update page. System Logging and Debugging.
This section describes settings which can be used to troubleshoot MantisBT operations as well as assist during development. The page execution timer shows at the bottom of each page.
Used for debugging e-mail notifications. When it is '', the emails are sent normally. If set to an e-mail address, all messages are sent to it, with the original recipients To, Cc, Bcc included in the message body.
Errors Display Method. Defines what errors are displayed and how. Available options are:. Suppress the error no display. This is the default behavior for unspecified errors constants. The default settings are recommended for use in production, and will only display MantisBT fatal errors, suppressing output of all other error types. Shows a list of variables and their values whenever an error is triggered. Setting this to ON is a potential security hazard, as it can expose sensitive information.
Only enable this setting for debugging purposes when you really need it. Debug messages. If this option is turned OFF, page redirects will function if a non-fatal error occurs. For debugging purposes, you can set this to ON so that any non-fatal error will prevent page redirection, allowing you to see the errors.
The system logging interface is used to extract detailed debugging information for the MantisBT system. It can also serve as an audit trail for users' actions. This controls the type of logging information recorded.
Enables extra logging for troubleshooting internals of email queuing and sending. Each user id is listed as well as why they are added, or deleted from the recipient list. Multiple log channels can be combined using PHP bitwise operators , e. Specifies where the log data goes. Carousel Next. What is Scribd? Uploaded by Yesu Oscco Baca. Document Information click to expand document information Original Title base-datos. Did you find this document useful? Is this content inappropriate? Report this Document.
Flag for inappropriate content. Exception has occurred. Error: Node Sass does not yet support your current environment: Windows bit with Unsupported runtime 83 TypeError: client.
It is likely not a bug in Create React App, but something you need to fix locally. The pool is probably full. Are you missing a. Did you add it to NgModule. Failed to load jshint library cypress click link contains text winston logger creating particular log file for each level cypress check element have attribute adding a preloader in elementor Cannot read property 'classList' of undefined expect any function jest jest axios manual mock jest manual mock node module.
TypeError: Class constructor Model cannot be invoked without https error response with status angular gulp scss to css and minify passport.
This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of Consider using ReferenceHandler. Preserve on JsonSerializerOptions to support cycles. Please update to the latest version version [2]. Webpacker::Manifest::MissingEntryError in Users index error metro bundler process exited with code 1 react native lodash debounce how to use platform.
Consider upgrading your version of 'tslib'. AngularFireDatabase is not a observable?? Faut-il envoyer un rapport d'erreurs A fatal JavaScript error has occurred. Should we send an error report visual studio node. If this was intentional, convert the expression to 'unknown' first.
You cannot reuse a client. Uncaught TypeError: jQuery. JS is not loaded and no custom loader has been specified "enabled": false in elasticsearch mapping spring reactive web client throw exception test disable URL encoder javascript angular file upload app with django console.
Falling back to JS-based animation. It must result in a command name, a script block, or a CommandInfo object. Uncaught in promise : NotReadableError: Could not start video source divcontainer is null web3-react readonly provider error fix javascript fix errora sonarqube for angular application petShopIndex.
Please include this authority in the knownAuthorities config parameter.
0コメント