Page MenuHomePhorge

Output from avivey script
ActivePublic

Authored by Ekubischta on Jun 23 2021, 22:38.
{
"%s (%s) has changed your Phabricator username.": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleUsernameMailEngine.php",
"line": 43
}
],
"types": [
null,
null
]
},
"%s You have not added authentication providers yet. Use \"%s\" to add a provider, which will let users register new Phabricator accounts and log in.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthListController.php",
"line": 55
}
],
"types": [
null,
null
]
},
"%s has invited you to join Phabricator.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthController.php",
"line": 261
},
{
"file": "/applications/people/controller/PhabricatorPeopleInviteSendController.php",
"line": 80
}
],
"types": [
null
]
},
"%s:\n\nThis email address was used to sign a Legalpad document in Phabricator:\n\n %s\n\nPlease verify you own this email address and accept the agreement by clicking this link:\n\n %s\n\nYour signature is not valid until you complete this verification step.\n\nYou can review the document here:\n\n %s\n": {
"uses": [
{
"file": "/applications/legalpad/controller/LegalpadDocumentSignController.php",
"line": 682
}
],
"types": [
null,
null,
null,
null
]
},
"(NOTE) **Looking for Phabricator documentation?** If you're looking for help and information about Phabricator, you can [[https://secure.phabricator.com/diviner/ | browse the public Phabricator documentation]] on the live site.\n\nDiviner is the documentation generator used to build the Phabricator documentation.\n\nYou haven't generated any Diviner documentation books yet, so there's nothing to show here. If you'd like to generate your own local copy of the Phabricator documentation and have it appear here, run this command:\n\n %s\n\n": {
"uses": [
{
"file": "/applications/diviner/controller/DivinerMainController.php",
"line": 51
}
],
"types": [
null
]
},
"**JIRA Instance Name**\n\nChoose a permanent name for this instance of JIRA. Phabricator uses this name internally to keep track of this instance of JIRA, in case the URL changes later.\n\nUse lowercase letters, digits, and period. For example, `jira`, `jira.mycompany` or `jira.engineering` are reasonable names.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorJIRAAuthProvider.php",
"line": 200
}
],
"types": []
},
"**Post a comment** in the JIRA task, similar to the emails Phabricator sends.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorJIRAAuthProvider.php",
"line": 284
}
],
"types": []
},
"**Step 1 of 2 - Name Phabricator OAuth Instance**\n\nChoose a permanent name for the OAuth server instance of Phabricator. //This// instance of Phabricator uses this name internally to keep track of the OAuth server instance of Phabricator, in case the URL changes later.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 16
}
],
"types": []
},
"**Step 2 of 2 - Configure Phabricator OAuth Instance**\n\nTo configure Phabricator OAuth, create a new application here:\n\n%s/oauthserver/client/create/\n\nWhen creating your application, use these settings:\n\n - **Redirect URI:** Set this to: `%s`\n\nAfter completing configuration, copy the **Client ID** and **Client Secret** to the fields above. (You may need to generate the client secret by clicking 'New Secret' first.)": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 32
}
],
"types": [
null,
null
]
},
"**Step 2 of 2**: In this step, you will configure JIRA.\n\n**Create a JIRA Application**: Log into JIRA and go to **Administration**, then **Add-ons**, then **Application Links**. Click the button labeled **Add Application Link**, and use these settings to create an application:\n\n - **Server URL**: `%s`\n - Then, click **Next**. On the second page:\n - **Application Name**: `Phabricator`\n - **Application Type**: `Generic Application`\n - Then, click **Create**.\n\n**Configure Your Application**: Find the application you just created in the table, and click the **Configure** link under **Actions**. Select **Incoming Authentication** and click the **OAuth** tab (it may be selected by default). Then, use these settings:\n\n - **Consumer Key**: Set this to the \"Consumer Key\" value in the form above.\n - **Consumer Name**: `Phabricator`\n - **Public Key**: Set this to the \"Public Key\" value in the form above.\n - **Consumer Callback URL**: `%s`\nClick **Save** in JIRA. Authentication should now be configured, and this provider should work correctly.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorJIRAAuthProvider.php",
"line": 27
}
],
"types": [
null,
null
]
},
"**Why do bot accounts need an email address?**\n\nAlthough bots do not normally receive email from Phabricator, they can interact with other systems which require an email address. Examples include:\n\n - If the account takes actions which //send// email, we need an address to use in the //From// header.\n - If the account creates commits, Git and Mercurial require an email address for authorship.\n - If you send email //to// Phabricator on behalf of the account, the address can identify the sender.\n - Some internal authentication functions depend on accounts having an email address.\n\n\nThe address will automatically be verified, so you do not need to be able to receive mail at this address, and can enter some invalid or nonexistent (but correctly formatted) address like `bot@yourcompany.com` if you prefer.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleNewController.php",
"line": 203
}
],
"types": []
},
"Add one or more subscribers to the object. You can add users by providing their usernames, or add projects by adding their hashtags. For example, use `%s` to add the user `alincoln` and the project with hashtag `#ios` as subscribers.\n\nSubscribers which are invalid or unrecognized will be ignored. This command has no effect if you do not specify any subscribers.\n\nUsers who are CC'd on the email itself are also automatically subscribed if Phabricator knows which accounts are linked to their email addresses.": {
"uses": [
{
"file": "/applications/subscriptions/command/PhabricatorSubscriptionsSubscribeEmailCommand.php",
"line": 20
}
],
"types": [
null
]
},
"Advises Phabricator to look for new commits in a repository as soon as possible. This advice is most useful if you have just pushed new commits to that repository.": {
"uses": [
{
"file": "/applications/diffusion/conduit/DiffusionLookSoonConduitAPIMethod.php",
"line": 16
}
],
"types": []
},
"After completing this build step Harbormaster can continue the build normally, or it can pause the build and wait for a message. If you are using this build step to trigger some work in an external system, you may want to have Phabricator wait for that system to perform the work and report results back.\n\nIf you select **Continue Build Normally**, the build plan will proceed once this step finishes.\n\nIf you select **Wait For Message**, the build plan will pause indefinitely once this step finishes. To resume the build, an external system must call `harbormaster.sendmessage` with the build target PHID, and either `\"pass\"` or `\"fail\"` to indicate the result for this step. After the result is recorded, the build plan will resume.": {
"uses": [
{
"file": "/applications/harbormaster/customfield/HarbormasterBuildStepCoreCustomField.php",
"line": 30
}
],
"types": []
},
"After configuring Phabricator to process inbound mail, you can interact with objects (like tasks and revisions) over email. For information on configuring Phabricator, see **[[ %s | Configuring Inbound Email ]]**.\n\nIn most cases, you can reply to email you receive from Phabricator to leave comments. You can also use **mail commands** to take a greater range of actions (like claiming a task or requesting changes to a revision) without needing to log in to the web UI.\n\nMail commands are keywords which start with an exclamation point, like `!claim`. Some commands may take parameters, like `!assign alincoln`.\n\nTo use mail commands, write one command per line at the beginning or end of your mail message. For example, you could write this in a reply to task email to claim the task:\n\n```\n!claim\n\nI'll take care of this.\n```\n\n\nWhen Phabricator receives your mail, it will process any commands first, then post the remaining message body as a comment. You can execute multiple commands at once:\n\n```\n!assign alincoln\n!close\n\nI just talked to @alincoln, and he showed me that he fixed this.\n```\n": {
"uses": [
{
"file": "/applications/meta/controller/PhabricatorApplicationEmailCommandsController.php",
"line": 38
}
],
"types": [
null
]
},
"After editing the PHP configuration, <strong>restart Phabricator for the changes to take effect</strong>. For help with restarting Phabricator, see %s in the documentation.": {
"uses": [
{
"file": "/applications/config/view/PhabricatorSetupIssueView.php",
"line": 463
}
],
"types": [
null
]
},
"After installing new PHP extensions, <strong>restart Phabricator for the changes to take effect</strong>. For help with restarting Phabricator, see %s in the documentation.": {
"uses": [
{
"file": "/applications/config/view/PhabricatorSetupIssueView.php",
"line": 98
}
],
"types": [
null
]
},
"After you have set a password, you can log in to Phabricator in the future by going here:": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleWelcomeMailEngine.php",
"line": 86
}
],
"types": []
},
"After you set up your account, you can log in to Phabricator in the future by going here:": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleWelcomeMailEngine.php",
"line": 94
}
],
"types": []
},
"Allow %s to access this Phabricator install?": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleApproveController.php",
"line": 55
}
],
"types": [
null
]
},
"Allow Phabricator to use a single mailbox for all replies.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 279
}
],
"types": []
},
"Allow users to link account credentials for this provider to existing Phabricator accounts. There is normally no reason to disable this unless you are trying to move away from a provider and want to stop users from creating new account links.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthEditController.php",
"line": 251
}
],
"types": []
},
"Allow users to register new Phabricator accounts using this provider. If you disable registration, users can still use this provider to log in to existing accounts, but will not be able to create new accounts.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthEditController.php",
"line": 241
}
],
"types": []
},
"Allow users to unlink account credentials for this provider from existing Phabricator accounts. If you disable this, Phabricator accounts will be permanently bound to provider accounts.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthEditController.php",
"line": 260
}
],
"types": []
},
"Allows you to edit, add, or remove the task statuses available in Maniphest,\nlike \"Open\", \"Resolved\" and \"Invalid\". The configuration should contain a map\nof status constants to status specifications (see defaults below for examples).\n\nThe constant for each status should be 1-12 characters long and contain only\nlowercase letters and digits. Valid examples are \"open\", \"closed\", and\n\"invalid\". Users will not normally see these values.\n\nThe keys you can provide in a specification are:\n\n - `name` //Required string.// Name of the status, like \"Invalid\".\n - `name.full` //Optional string.// Longer name, like \"Closed, Invalid\". This\n appears on the task detail view in the header.\n - `name.action` //Optional string.// Action name for email subjects, like\n \"Marked Invalid\".\n - `closed` //Optional bool.// Statuses are either \"open\" or \"closed\".\n Specifying `true` here will mark the status as closed (like \"Resolved\" or\n \"Invalid\"). By default, statuses are open.\n - `special` //Optional string.// Mark this status as special. The special\n statuses are:\n - `default` This is the default status for newly created tasks. You must\n designate one status as default, and it must be an open status.\n - `closed` This is the default status for closed tasks (for example, tasks\n closed via the \"!close\" action in email or via the quick close button in\n Maniphest). You must designate one status as the default closed status,\n and it must be a closed status.\n - `duplicate` This is the status used when tasks are merged into one\n another as duplicates. You must designate one status for duplicates,\n and it must be a closed status.\n - `transaction.icon` //Optional string.// Allows you to choose a different\n icon to use for this status when showing status changes in the transaction\n log. Please see UIExamples, Icons and Images for a list.\n - `transaction.color` //Optional string.// Allows you to choose a different\n color to use for this status when showing status changes in the transaction\n log.\n - `silly` //Optional bool.// Marks this status as silly, and thus wholly\n inappropriate for use by serious businesses.\n - `prefixes` //Optional list<string>.// Allows you to specify a list of\n text prefixes which will trigger a task transition into this status\n when mentioned in a commit message. For example, providing \"closes\" here\n will allow users to move tasks to this status by writing `Closes T123` in\n commit messages.\n - `suffixes` //Optional list<string>.// Allows you to specify a list of\n text suffixes which will trigger a task transition into this status\n when mentioned in a commit message, after a valid prefix. For example,\n providing \"as invalid\" here will allow users to move tasks\n to this status by writing `Closes T123 as invalid`, even if another status\n is selected by the \"Closes\" prefix.\n - `keywords` //Optional list<string>.// Allows you to specify a list\n of keywords which can be used with `!status` commands in email to select\n this status.\n - `disabled` //Optional bool.// Marks this status as no longer in use so\n tasks can not be created or edited to have this status. Existing tasks with\n this status will not be affected, but you can batch edit them or let them\n die out on their own.\n - `claim` //Optional bool.// By default, closing an unassigned task claims\n it. You can set this to `false` to disable this behavior for a particular\n status.\n - `locked` //Optional string.// Lock tasks in this status. Specify \"comments\"\n to lock comments (users who can edit the task may override this lock).\n Specify \"edits\" to prevent anyone except the task owner from making edits.\n - `mfa` //Optional bool.// Require all edits to this task to be signed with\n multi-factor authentication.\n\nStatuses will appear in the UI in the order specified. Note the status marked\n`special` as `duplicate` is not settable directly and will not appear in UI\nelements, and that any status marked `silly` does not appear if Phabricator\nis configured with `phabricator.serious-business` set to true.\n\nExamining the default configuration and examples below will probably be helpful\nin understanding these options.\n": {
"uses": [
{
"file": "/applications/maniphest/config/PhabricatorManiphestConfigOptions.php",
"line": 154
}
],
"types": []
},
"Alternative URIs that can access Phabricator.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 99
}
],
"types": []
},
"An administrator has placed Phabricator into read-only mode.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 19
}
],
"types": []
},
"Anyone who can browse to this Phabricator install will be able to register an account. To add email domain restrictions, configure %s.": {
"uses": [
{
"file": "/applications/auth/guidance/PhabricatorAuthProvidersGuidanceEngineExtension.php",
"line": 56
}
],
"types": [
null
]
},
"Are you completely sure you really want to permanently destroy all storage for Phabricator data on host \"%s\"? This operation can not be undone and your data will not be recoverable if you proceed.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementDestroyWorkflow.php",
"line": 49
}
],
"types": [
null
]
},
"Attempting to compare a password saved with the \"%s\" hash. No such hasher is known to Phabricator.": {
"uses": [
{
"file": "/infrastructure/util/password/PhabricatorPasswordHasher.php",
"line": 309
}
],
"types": [
null
]
},
"Attempting to use a panel in a way that requires an implementation, but the panel implementation (\"%s\") is unknown to Phabricator.": {
"uses": [
{
"file": "/applications/dashboard/storage/PhabricatorDashboardPanel.php",
"line": 98
}
],
"types": [
null
]
},
"Authentication providers allow users to register accounts and log in to Phabricator.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideInstallModule.php",
"line": 68
}
],
"types": []
},
"Because Phragment generates files (such as ZIP archives and patches) as they are requested, it requires that you configure the `%s` option. This option on it's own will also provide additional security when serving files across Phabricator.": {
"uses": [
{
"file": "/applications/phragment/controller/PhragmentController.php",
"line": 210
}
],
"types": [
null
]
},
"Before running storage upgrades, you should take down the Phabricator web interface and stop any running Phabricator daemons (you can disable this warning with %s).": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementUpgradeWorkflow.php",
"line": 48
}
],
"types": [
null
]
},
"Before you can use Phabricator, you need to add multi-factor authentication to your account. Multi-factor authentication helps secure your account by making it more difficult for attackers to gain access or take sensitive actions.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthNeedsMultiFactorController.php",
"line": 205
}
],
"types": []
},
"Builtin Project Images that ship with Phabricator.": {
"uses": [
{
"file": "/applications/uiexample/examples/PhabricatorProjectBuiltinsExample.php",
"line": 10
}
],
"types": []
},
"By default, Phabricator allows users to add multi-factor authentication to\ntheir accounts, but does not require it. By enabling this option, you can\nforce all users to add at least one authentication factor before they can use\ntheir accounts.\n\nAdministrators can query a list of users who do not have MFA configured in\n{nav People}:\n\n - **[[ %s | %s ]]**": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSecurityConfigOptions.php",
"line": 69
}
],
"types": [
null,
null
]
},
"By default, Phabricator generates unique reply-to addresses and sends a separate\nemail to each recipient when you enable reply handling. This is more secure than\nusing \"From\" to establish user identity, but can mean users may receive multiple\nemails when they are on mailing lists. Instead, you can use a single, non-unique\nreply to address and authenticate users based on the \"From\" address by setting\nthis to 'true'. This trades away a little bit of security for convenience, but\nit's reasonable in many installs. Object interactions are still protected using\nhashes in the single public email address, so objects can not be replied to\nblindly.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 144
}
],
"types": []
},
"By default, Phabricator includes some flavor text in the UI, like a prompt to \"Weigh In\" rather than \"Add Comment\" in Maniphest. If you'd prefer more traditional UI strings like \"Add Comment\", you can set this flag to disable most of the extra flavor.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 167
}
],
"types": []
},
"By default, Phabricator links object names in Remarkup fields to the corresponding object. This regex can be used to modify this behavior; object names that match this regex will not be linked.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 192
}
],
"types": []
},
"By default, Phabricator serves files from the same domain the application is served from. This is convenient, but presents a security risk.\n\nYou should configure a CDN or alternate file domain to mitigate this risk. Configuring a CDN will also improve performance. See [[ %s | %s ]] for instructions.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSecurityConfigOptions.php",
"line": 90
}
],
"types": [
null,
null
]
},
"Choose which language you would like the Phabricator UI to use.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorTranslationSetting.php",
"line": 26
}
],
"types": []
},
"Completely Break Phabricator": {
"uses": [
{
"file": "/applications/meta/controller/PhabricatorApplicationUninstallController.php",
"line": 103
}
],
"types": []
},
"Condolences on forgetting your password. You can use this link to reset it:\n\n %s\n\nAfter you set a new password, consider writing it down on a sticky note and attaching it to your monitor so you don't forget again! Choosing a very short, easy-to-remember password like \"cat\" or \"1234\" might also help.\n\nBest Wishes,\nPhabricator\n": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleEmailLoginMailEngine.php",
"line": 80
}
],
"types": [
null
]
},
"Config option '%s' is invalid. The URI must NOT have a path, e.g. '%s' is OK, but '%s' is not. Phabricator must be installed on an entire domain; it can not be installed on a path.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSecurityConfigOptions.php",
"line": 328
},
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 308
}
],
"types": [
null,
null,
null
]
},
"Configure **Repository Automation** to allow Phabricator to write to this repository.\n\nIMPORTANT: This feature is new, experimental, and not supported. Use it at your own risk.": {
"uses": [
{
"file": "/applications/diffusion/editor/DiffusionRepositoryEditEngine.php",
"line": 220
}
],
"types": []
},
"Configure Phabricator": {
"uses": [
{
"file": "/applications/config/application/PhabricatorConfigApplication.php",
"line": 34
},
{
"file": "/applications/guides/module/PhabricatorGuideInstallModule.php",
"line": 81
}
],
"types": []
},
"Configure Phabricator to run on a cluster of hosts.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorClusterConfigOptions.php",
"line": 11
}
],
"types": []
},
"Configure a connection to an LDAP server so that users can use their LDAP credentials to log in to Phabricator.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorLDAPAuthProvider.php",
"line": 13
}
],
"types": []
},
"Configure the Phabricator UI, including colors.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorUIConfigOptions.php",
"line": 11
}
],
"types": []
},
"Confirm the link with this %s account. This account will be able to log in to your Phabricator account.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthConfirmLinkController.php",
"line": 56
}
],
"types": [
null
]
},
"Content source type \"%s\" is not known to Phabricator!": {
"uses": [
{
"file": "/infrastructure/contentsource/PhabricatorContentSource.php",
"line": 45
}
],
"types": [
null
]
},
"Continue to Phabricator": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorEmailVerificationController.php",
"line": 47
},
{
"file": "/applications/auth/controller/PhabricatorEmailVerificationController.php",
"line": 58
}
],
"types": []
},
"Control how Phabricator renders user names in mail.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 288
}
],
"types": []
},
"Controls whether Phabricator sends email \"From\" users.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 241
}
],
"types": []
},
"Controls whether Phabricator sends one email with multiple recipients in the \"To:\" line, or multiple emails, each with a single recipient in the \"To:\" line.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 229
}
],
"types": []
},
"Cookies set for x.com are also sent for y.x.com. Assuming Phabricator instances are running on both domains, this will create a collision preventing you from logging in.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 125
}
],
"types": []
},
"Create a standard user account. These users can log in to Phabricator, use the web interface and API, and receive email.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleCreateController.php",
"line": 27
}
],
"types": []
},
"Create documents and track signatures. Can also be re-used in other areas of Phabricator, like CLAs.": {
"uses": [
{
"file": "/applications/legalpad/query/LegalpadDocumentSearchEngine.php",
"line": 188
}
],
"types": []
},
"Credential management for re-use in other areas of Phabricator or general storage of shared secrets.": {
"uses": [
{
"file": "/applications/passphrase/query/PassphraseCredentialSearchEngine.php",
"line": 127
}
],
"types": []
},
"Customize the logo image and text which appears in the main site header:\n\n - **Logo Image**: Upload a new 80 x 80px image to replace the Phabricator logo in the site header.\n\n - **Wordmark**: Choose new text to display next to the logo. By default, the header displays //Phabricator//.\n\n": {
"uses": [
{
"file": "/applications/config/option/PhabricatorUIConfigOptions.php",
"line": 61
}
],
"types": []
},
"Customized settings for Phabricator applications.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 254
}
],
"types": []
},
"DarkConsole is a debugging console for developing and troubleshooting Phabricator applications. After enabling DarkConsole, press the {nav `} key on your keyboard to toggle it on or off.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorDarkConsoleSetting.php",
"line": 29
}
],
"types": []
},
"DarkConsole is a development and profiling tool built into Phabricator's web interface. You should leave it disabled unless you are developing or debugging Phabricator.\n\nOnce you activate DarkConsole for the install, **you need to enable it for your account before it will actually appear on pages.** You can do this in Settings > Developer Settings.\n\nDarkConsole exposes potentially sensitive data (like queries, stack traces, and configuration) so you generally should not turn it on in production.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorDeveloperConfigOptions.php",
"line": 33
}
],
"types": []
},
"Data can not be exported to Excel because the PHPExcel library is not\ninstalled. This software component is required for Phabricator to create\nExcel files.\n\nYou can install PHPExcel from GitHub:\n\n> https://github.com/PHPOffice/PHPExcel\n\nBriefly:\n\n - Clone that repository somewhere on the sever\n (like `/path/to/example/PHPExcel`).\n - Update your PHP `%s` setting (in `php.ini`) to include the PHPExcel\n `Classes` directory (like `/path/to/example/PHPExcel/Classes`).": {
"uses": [
{
"file": "/infrastructure/export/format/PhabricatorExcelExportFormat.php",
"line": 34
}
],
"types": [
null
]
},
"Database host \"%s\" is configured as a master, but is replicating another host. This is dangerous and can mangle or destroy data. Only replicas should be replicating. Stop replication on the host or reconfigure Phabricator.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorDatabaseSetupCheck.php",
"line": 177
}
],
"types": [
null
]
},
"Database host \"%s\" is configured with a very small %s (%s). This may cause poor database performance and lock exhaustion.\n\nThere are no hard-and-fast rules to setting an appropriate value, but a reasonable starting point for a standard install is something like 40%% of the total memory on the machine. For example, if you have 4GB of RAM on the machine you have installed Phabricator on, you might set this value to %s.\n\nYou can read more about this option in the MySQL documentation to help you make a decision about how to configure it for your use case. There are no concerns specific to Phabricator which make it different from normal workloads with respect to this setting.\n\nTo adjust the setting, add something like this to your %s file (in the %s section), replacing %s with an appropriate value for your host and use case. Then restart %s:\n\n%s\nIf you're satisfied with the current setting, you can safely ignore this setup warning.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorMySQLSetupCheck.php",
"line": 271
}
],
"types": [
null,
null,
null,
null,
null,
null,
null,
null,
null
]
},
"Database host \"%s\" is using the builtin stopword file for building search indexes. This can make Phabricator's search feature less useful.\n\nStopwords are common words which are not indexed and thus can not be searched for. The default stopword file has about 500 words, including various words which you are likely to wish to search for, such as 'various', 'likely', 'wish', and 'zero'.\n\nTo make search more useful, you can use an alternate stopword file with fewer words. Alternatively, if you aren't concerned about searching for common words, you can ignore this warning. If you later plan to configure Elasticsearch, you can also ignore this warning: this stopword file only affects MySQL fulltext indexes.\n\nTo choose a different stopword file, add this to your %s file (in the %s section) and then restart %s:\n\n%s\n(You can also use a different file if you prefer. The file suggested above has about 50 of the most common English words.)\n\nFinally, run this command to rebuild indexes using the new rules:\n\n%s": {
"uses": [
{
"file": "/applications/config/check/PhabricatorMySQLSetupCheck.php",
"line": 153
}
],
"types": [
null,
null,
null,
null,
null,
null
]
},
"Default address used as a \"From\" or \"To\" email address when an address is\nrequired but no meaningful address is available.\n\nIf you configure inbound mail, you generally do not need to set this:\nPhabricator will automatically generate and use a suitable mailbox on the\ninbound mail domain.\n\nOtherwise, this option should be configured to point at a valid mailbox which\ndiscards all mail sent to it. If you point it at an invalid mailbox, mail sent\nby Phabricator and some mail sent by users will bounce. If you point it at a\nreal user mailbox, that user will get a lot of mail they don't want.\n\nFor further guidance, see **[[ %s | %s ]]** in the documentation.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 190
}
],
"types": [
null,
null
]
},
"Define a Phabricator cluster by providing a whitelist of host addresses that are part of the cluster.\n\nHosts on this whitelist have special powers. These hosts are permitted to bend security rules, and misconfiguring this list can make your install less secure. For more information, see **[[ %s | %s ]]**.\n\nDefine a list of CIDR blocks which whitelist all hosts in the cluster and no additional hosts. See the examples below for details.\n\nWhen cluster addresses are defined, Phabricator hosts will also reject requests to interfaces which are not whitelisted.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorClusterConfigOptions.php",
"line": 58
}
],
"types": [
null,
null
]
},
"Defines a database service for use in a Phabricator cluster.": {
"uses": [
{
"file": "/applications/almanac/servicetype/AlmanacClusterDatabaseServiceType.php",
"line": 18
}
],
"types": []
},
"Defines a repository service for use in a Phabricator cluster.": {
"uses": [
{
"file": "/applications/almanac/servicetype/AlmanacClusterRepositoryServiceType.php",
"line": 18
}
],
"types": []
},
"Destroying objects may cause related objects to stop working, and may leave scattered references to objects which no longer exist. In most cases, it is much better to disable or archive objects instead of destroying them. This risk is greatest when deleting complex or highly connected objects like repositories, projects and users.\n\nThese tattered edges are an expected consequence of destroying objects, and the Phabricator upstream will not help you fix them. We strongly recommend disabling or archiving objects instead.": {
"uses": [
{
"file": "/applications/system/management/PhabricatorSystemRemoveDestroyWorkflow.php",
"line": 104
}
],
"types": []
},
"Disable %s? They will no longer be able to access Phabricator or receive email.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleDisableController.php",
"line": 93
}
],
"types": [
null
]
},
"Do not install Phabricator on an instance class with burstable CPU.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 105
}
],
"types": []
},
"Do you want to authorize the external application \"%s\" to access your Phabricator account data, including your primary email address?": {
"uses": [
{
"file": "/applications/oauthserver/controller/PhabricatorOAuthServerAuthController.php",
"line": 250
}
],
"types": [
null
]
},
"Do you want to enable this provider? Users will be able to log in to Phabricator using linked accounts.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthDisableController.php",
"line": 56
}
],
"types": []
},
"Do you want to enable this provider? Users will be able to use their existing external accounts to register new Phabricator accounts and log in using linked accounts.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthDisableController.php",
"line": 51
}
],
"types": []
},
"Either the Phabricator schema for Elasticsearch has changed or Elasticsearch created the index automatically. Use the following command to rebuild the index.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorElasticsearchSetupCheck.php",
"line": 72
}
],
"types": []
},
"Elasticsearch is configured (with the %s setting) but Phabricator encountered an exception when trying to test the index.\n\n%s": {
"uses": [
{
"file": "/applications/config/check/PhabricatorElasticsearchSetupCheck.php",
"line": 37
}
],
"types": [
null,
null
]
},
"Empower %s as an administrator? They will be able to create users, approve users, make and remove administrators, delete accounts, and perform other administrative functions on this Phabricator install.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleEmpowerController.php",
"line": 54
}
],
"types": [
null
]
},
"Enable %s? They will be able to access Phabricator and receive email again.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleDisableController.php",
"line": 103
}
],
"types": [
null
]
},
"Enable Phabricator's debugging console.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorDeveloperConfigOptions.php",
"line": 30
}
],
"types": []
},
"Expected \"newInternalCursorFromExternalCursor()\" to return an object of class \"PhabricatorQueryCursor\", but got \"%s\" (in class \"%s\").": {
"uses": [
{
"file": "/infrastructure/query/policy/PhabricatorCursorPagedPolicyAwareQuery.php",
"line": 189
}
],
"types": [
null,
null
]
},
"Expected \"newTransactionWarning()\" to return an object of class \"PhabricatorTransactionWarning\", got something else (\"%s\") from transaction of class \"%s\".": {
"uses": [
{
"file": "/applications/transactions/response/PhabricatorApplicationTransactionWarningResponse.php",
"line": 58
}
],
"types": [
null,
null
]
},
"Expected a list of PhabricatorRepositorySymbol objects from external symbol source \"%s\".": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionSymbolController.php",
"line": 106
}
],
"types": [
null
]
},
"Expected valid JSON response from Phabricator %s request.": {
"uses": [
{
"file": "/applications/auth/adapter/PhutilPhabricatorAuthAdapter.php",
"line": 92
}
],
"types": [
null
]
},
"Explicit S3 endpoint to use. This should be the endpoint which corresponds to the region you have selected in `amazon-s3.region`. Phabricator can not determine the correct endpoint automatically because some endpoint locations are irregular.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorAWSConfigOptions.php",
"line": 43
}
],
"types": []
},
"Extending Phabricator": {
"uses": [
{
"file": "/applications/config/option/PhabricatorExtendingPhabricatorConfigOptions.php",
"line": 7
}
],
"types": []
},
"Flood the queue with test tasks. This command is intended for use when developing and debugging Phabricator.": {
"uses": [
{
"file": "/infrastructure/daemon/workers/management/PhabricatorWorkerManagementFloodWorkflow.php",
"line": 12
}
],
"types": []
},
"For custom domains to work, this Phabricator instance must be configured to allow the public access policy. Configure this setting %s, or ask an administrator to configure this setting. The domain can be specified later once this setting has been changed.": {
"uses": [
{
"file": "/applications/phame/storage/PhameBlog.php",
"line": 157
}
],
"types": [
null
]
},
"Generate a new quickstart database dump. This command is mostly useful when developing Phabricator.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementQuickstartWorkflow.php",
"line": 12
}
],
"types": []
},
"Generated by Phabricator": {
"uses": [
{
"file": "/applications/metamta/controller/PhabricatorMetaMTAMailViewController.php",
"line": 431
}
],
"types": []
},
"Get Well Soon,\nPhabricator": {
"uses": [
{
"file": "/applications/people/storage/PhabricatorUserEmail.php",
"line": 198
}
],
"types": []
},
"Group sections of a codebase into packages for re-use in other areas of Phabricator, like Herald rules.": {
"uses": [
{
"file": "/applications/owners/query/PhabricatorOwnersPackageSearchEngine.php",
"line": 171
}
],
"types": []
},
"IMPORTANT: Feed hooks are deprecated and have been replaced by Webhooks.\n\nYou can configure Webhooks in Herald. This configuration option will be removed\nin a future version of Phabricator.\n\n(This legacy option may be configured with a list of URIs; feed stories will\nsend to these URIs.)": {
"uses": [
{
"file": "/applications/feed/config/PhabricatorFeedConfigOptions.php",
"line": 23
}
],
"types": []
},
"IMPORTANT: The upstream does not provide support for prototype applications.\n\nPhabricator includes prototype applications which are in an **early stage of development**. By default, prototype applications are not installed, because they are often not yet developed enough to be generally usable. You can enable this option to install them if you're developing Phabricator or are interested in previewing upcoming features.\n\nTo learn more about prototypes, see [[ %s | %s ]].\n\nAfter enabling prototypes, you can selectively uninstall them (like normal applications).": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 141
}
],
"types": [
null,
null
]
},
"Identify the component in your webserver configuration which is decompressing or mangling requests and disable it. Phabricator will not work properly until you do.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 354
}
],
"types": []
},
"If the web server responds to both HTTP and HTTPS requests but you want users to connect with only HTTPS, you can set this to `true` to make Phabricator redirect HTTP requests to HTTPS.\n\nNormally, you should just configure your server not to accept HTTP traffic, but this setting may be useful if you originally used HTTP and have now switched to HTTPS but don't want to break old links, or if your webserver sits behind a load balancer which terminates HTTPS connections and you can not reasonably configure more granular behavior there.\n\nIMPORTANT: Phabricator determines if a request is HTTPS or not by examining the PHP `%s` variable. If you run Apache/mod_php this will probably be set correctly for you automatically, but if you run Phabricator as CGI/FCGI (e.g., through nginx or lighttpd), you need to configure your web server so that it passes the value correctly based on the connection type.\n\nIf you configure Phabricator in cluster mode, note that this setting is ignored by intracluster requests.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSecurityConfigOptions.php",
"line": 120
}
],
"types": [
null
]
},
"If those commands don't work, try Google. The process of installing PHP extensions is not specific to Phabricator, and any instructions you can find for installing them on your system should work. On Mac OS X, you might want to try Homebrew.": {
"uses": [
{
"file": "/applications/config/view/PhabricatorSetupIssueView.php",
"line": 92
}
],
"types": []
},
"If you accept Phabricator SSH traffic on a different host from web traffic (for example, if you use different SSH and web load balancers), you can set the SSH hostname here. This is an advanced option.": {
"uses": [
{
"file": "/applications/diffusion/config/PhabricatorDiffusionConfigOptions.php",
"line": 153
}
],
"types": []
},
"If you are developing Phabricator, these errors usually indicate that your schema specifications do not agree with the schemata your code actually builds.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 865
}
],
"types": []
},
"If you are not developing Phabricator itself, report this issue to the upstream.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 861
}
],
"types": []
},
"If you change your primary address, Phabricator will send all email to %s.": {
"uses": [
{
"file": "/applications/settings/panel/PhabricatorEmailAddressesSettingsPanel.php",
"line": 401
}
],
"types": [
null
]
},
"If you disable **Email Notifications**, Phabricator will never send email to notify you about events. This preference overrides all your other settings.\n\n//You will still receive some administrative email, like password reset email.//": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorEmailNotificationsSetting.php",
"line": 25
}
],
"types": []
},
"If you disable **Self Actions**, Phabricator will not notify you about actions you take.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorEmailSelfActionsSetting.php",
"line": 25
}
],
"types": []
},
"If you enable `%s`, Phabricator uses \"From\" to authenticate users. You can\nadditionally enable this setting to try to authenticate with 'Reply-To'. Note\nthat this is completely spoofable and insecure (any user can set any 'Reply-To'\naddress) but depending on the nature of your install or other deliverability\nconditions this might be okay. Generally, you can't do much more by spoofing\nReply-To than be annoying (you can write but not read content). But this is\nstill **COMPLETELY INSECURE**.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 123
}
],
"types": [
null
]
},
"If you have difficulty reading the Phabricator UI, this setting may make Phabricator more accessible.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorAccessibilitySetting.php",
"line": 22
}
],
"types": []
},
"If you have multiple Phabricator environments (like a development/staging environment for working on testing Phabricator, and a production environment for deploying it), set the production environment URI here so that emails and other durable URIs will always generate with links pointing at the production environment. If unset, defaults to `%s`. Most installs do not need to set this option.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 88
}
],
"types": [
null
]
},
"If you set this to true, Phabricator will attach patches to Differential mail (as text attachments). This will not work if you are using SendGrid as your mail adapter.": {
"uses": [
{
"file": "/applications/differential/config/PhabricatorDifferentialConfigOptions.php",
"line": 231
}
],
"types": []
},
"If you want to import only part of a repository, like `trunk/`, you can set a path in **Import Only**. Phabricator will ignore commits which do not affect this path.": {
"uses": [
{
"file": "/applications/diffusion/editor/DiffusionRepositoryEditEngine.php",
"line": 236
}
],
"types": []
},
"If you want to link an existing Phabricator account to this external account, do not continue. Instead: log in to your existing account, then go to \"Settings\" and link the account in the \"External Accounts\" panel.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 177
}
],
"types": []
},
"If you want to use a single mailbox for Phabricator reply mail, you can use this\nand set a common prefix for reply addresses generated by Phabricator. It will\nmake use of the fact that a mail-address such as\n`phabricator+D123+1hjk213h@example.com` will be delivered to the `phabricator`\nuser's mailbox. Set this to the left part of the email address and it will be\nprepended to all generated reply addresses.\n\nFor example, if you want to use `phabricator@example.com`, this should be set\nto `phabricator`.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 157
}
],
"types": []
},
"If you're new to Phabricator, these optional steps can help you learn the basics. Conceptually, Phabricator is structured as a graph, and repositories, tasks, and projects are all independent from each other. Feel free to set up Phabricator for how you work best, and explore these features at your own pace.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideQuickStartModule.php",
"line": 175
}
],
"types": []
},
"Imported events can not be edited in Phabricator.": {
"uses": [
{
"file": "/applications/calendar/codex/PhabricatorCalendarEventPolicyCodex.php",
"line": 74
}
],
"types": []
},
"Improve Mobile Experience for Phabricator": {
"uses": [
{
"file": "/applications/uiexample/examples/PHUIHovercardUIExample.php",
"line": 42
}
],
"types": []
},
"Information about Phabricator events and event listeners.": {
"uses": [
{
"file": "/applications/console/plugin/DarkConsoleEventPlugin.php",
"line": 10
}
],
"types": []
},
"Install Phabricator": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideInstallModule.php",
"line": 10
}
],
"types": []
},
"Installing the \"APCu\" PHP extension will improve performance. This extension is strongly recommended. Without it, Phabricator must rely on a very inefficient disk-based cache.": {
"uses": [
{
"file": "/applications/cache/spec/PhabricatorDataCacheSpec.php",
"line": 72
}
],
"types": []
},
"Invite the rest of your team to get started on Phabricator.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideQuickStartModule.php",
"line": 162
}
],
"types": []
},
"Lead Developer of Phabricator": {
"uses": [
{
"file": "/applications/uiexample/examples/PHUIBadgeExample.php",
"line": 114
}
],
"types": []
},
"Learn how to configure mail and other options in Phabricator.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideInstallModule.php",
"line": 98
}
],
"types": []
},
"List Phabricator databases.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementDatabasesWorkflow.php",
"line": 10
}
],
"types": []
},
"List inbound messages received by Phabricator.": {
"uses": [
{
"file": "/applications/metamta/management/PhabricatorMailManagementListInboundWorkflow.php",
"line": 9
}
],
"types": []
},
"List outbound messages sent by Phabricator.": {
"uses": [
{
"file": "/applications/metamta/management/PhabricatorMailManagementListOutboundWorkflow.php",
"line": 9
}
],
"types": []
},
"Log In with Phabricator": {
"uses": [
{
"file": "/applications/oauthserver/application/PhabricatorOAuthServerApplication.php",
"line": 26
}
],
"types": []
},
"Log in to Phabricator": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthOneTimeLoginController.php",
"line": 162
}
],
"types": []
},
"Love,\nPhabricator": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleWelcomeMailEngine.php",
"line": 128
}
],
"types": []
},
"Mail.app on OS X Lion won't respect threading headers unless the subject is\nprefixed with \"Re:\". If you enable this option, Phabricator will add \"Re:\" to\nthe subject line of all mail which is expected to thread. If you've set\n'metamta.one-mail-per-recipient', users can override this setting in their\npreferences.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 105
}
],
"types": []
},
"Make Phabricator even cooler!": {
"uses": [
{
"file": "/applications/config/option/PhabricatorExtendingPhabricatorConfigOptions.php",
"line": 11
}
],
"types": []
},
"Manage Phabricator Daemons": {
"uses": [
{
"file": "/applications/daemon/application/PhabricatorDaemonsApplication.php",
"line": 10
}
],
"types": []
},
"Many text editors can be configured as URI handlers for special protocols like `editor://`. If you have installed and configured such an editor, Phabricator can generate links that you can click to open files locally.\n\nProvide a URI pattern for building external editor URIs in your environment. For example, if you use TextMate on macOS, the pattern for your machine may look something like this:\n\n```name=\"Example: TextMate on macOS\"\n%s\n```\n\n\nFor complete instructions on editor configuration, see **[[ %s | %s ]]**.\n\nSee the tables below for a list of supported variables and protocols.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorEditorSetting.php",
"line": 22
}
],
"types": [
null,
null,
null
]
},
"NOTE: Amazon **requires** HTTPS, but your Phabricator install does not use HTTPS. **You will not be able to add Amazon as an authentication provider until you configure HTTPS on this install**.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorAmazonAuthProvider.php",
"line": 17
}
],
"types": []
},
"NOTE: Any user who can browse to this install's login page will be able to register a Phabricator account. To restrict who can register an account, configure [[ %s | %s ]].": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthEditController.php",
"line": 222
}
],
"types": [
null,
null
]
},
"Newly registered Phabricator accounts can either be placed into a manual approval queue for administrative review, or automatically activated immediately. The approval queue is enabled by default because it gives you greater control over who can register an account and access Phabricator.\n\nIf your install is completely public, or on a VPN, or users can only register with a trusted provider like LDAP, or you've otherwise configured Phabricator to prevent unauthorized registration, you can disable the queue to reduce administrative overhead.\n\nNOTE: Before you disable the queue, make sure @{config:auth.email-domains} is configured correctly for your install!": {
"uses": [
{
"file": "/applications/config/option/PhabricatorAuthenticationConfigOptions.php",
"line": 47
}
],
"types": []
},
"No REMOTE_ADDR is available, so Phabricator cannot determine the origin address for requests. This will prevent Phabricator from performing important security checks. This most often means you have a mistake in your preamble script. Consult the documentation (%s) and double-check that the script is written correctly.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPConfigSetupCheck.php",
"line": 24
}
],
"types": [
null
]
},
"No permission to run \"SHOW SLAVE STATUS\". Grant this user \"REPLICATION CLIENT\" permission to allow Phabricator to monitor replica health.": {
"uses": [
{
"file": "/infrastructure/cluster/PhabricatorDatabaseRef.php",
"line": 354
}
],
"types": []
},
"Normally, Differential revisions remain on the dashboard when they are \"Accepted\", and the author then commits the changes to \"Close\" the revision and move it off the dashboard.\n\nIf you have an unusual workflow where Differential is used for post-commit review (normally called \"Audit\", elsewhere in Phabricator), you can set this flag to treat the \"Accepted\" state as a \"Closed\" state and end the review workflow early.\n\nThis sort of workflow is very unusual. Very few installs should need to change this option.": {
"uses": [
{
"file": "/applications/differential/config/PhabricatorDifferentialConfigOptions.php",
"line": 208
}
],
"types": []
},
"Normally, Phabricator automatically updates repositories based on how much time has elapsed since the last commit. This helps reduce load if you have a large number of mostly inactive repositories, which is common.": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionRepositoryEditUpdateController.php",
"line": 48
}
],
"types": []
},
"Normally, Phabricator issues HTTP redirects after a successful POST. This can make it difficult to debug things which happen while processing the POST, because service and profiling information are lost. By setting this configuration option, Phabricator will show a page instead of automatically redirecting, allowing you to examine service and profiling information. It also makes the UX awful, so you should only enable it when debugging.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorDeveloperConfigOptions.php",
"line": 94
}
],
"types": []
},
"Normally, Phabricator profiles pages only when explicitly requested via DarkConsole. However, it may be useful to profile some pages automatically.\n\nSet this option to a positive integer N to profile 1 / N pages automatically. For example, setting it to 1 will profile every page, while setting it to 1000 will profile 1 page per 1000 requests (i.e., 0.1%% of requests).\n\nSince profiling is slow and generates a lot of data, you should set this to 0 in production (to disable it) or to a large number (to collect a few samples, if you're interested in having some data to look at eventually). In development, it may be useful to set it to 1 in order to debug performance problems.\n\nNOTE: You must install XHProf for profiling to work.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorDeveloperConfigOptions.php",
"line": 109
}
],
"types": []
},
"On database host \"%s\", the global \"sql_mode\" setting does not include the \"STRICT_ALL_TABLES\" mode. Enabling this mode is recommended to generally improve how MySQL handles certain errors.\n\nWithout this mode enabled, MySQL will silently ignore some error conditions, including inserts which attempt to store more data in a column than actually fits. This behavior is usually undesirable and can lead to data corruption (by truncating multibyte characters in the middle), data loss (by discarding the data which does not fit into the column), or security concerns (for example, by truncating keys or credentials).\n\nPhabricator is developed and tested in \"STRICT_ALL_TABLES\" mode so you should normally never encounter these situations, but may run into them if you interact with the database directly, run third-party code, develop extensions, or just encounter a bug in the software.\n\nEnabling \"STRICT_ALL_TABLES\" makes MySQL raise an explicit error if one of these unusual situations does occur. This is a safer behavior and prevents these situations from causing secret, subtle, and potentially serious issues later on.\n\nYou can find more information about this mode (and how to configure it) in the MySQL manual. Usually, it is sufficient to add this to your \"my.cnf\" file (in the \"[mysqld]\" section) and then restart \"mysqld\":\n\n%s\nNote that if you run other applications against the same database, they may not work in strict mode.\n\nIf you can not or do not want to enable \"STRICT_ALL_TABLES\", you can safely ignore this warning. Phabricator will work correctly with this mode enabled or disabled.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorMySQLSetupCheck.php",
"line": 57
}
],
"types": [
null,
null
]
},
"Only documents with signature type \"individual\" may require signing to use Phabricator.": {
"uses": [
{
"file": "/applications/legalpad/editor/LegalpadDocumentEditor.php",
"line": 103
}
],
"types": []
},
"Options for Phabricator developers, including debugging.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorDeveloperConfigOptions.php",
"line": 11
}
],
"types": []
},
"PHP is currently configured to honor requests from any MySQL server it connects to for the content of any local file.\n\nThis capability supports MySQL \"LOAD DATA LOCAL INFILE\" queries, but allows a malicious MySQL server read access to the local disk: the server can ask the client to send the content of any local file, and the client will comply.\n\nAlthough it is normally difficult for an attacker to convince Phabricator to connect to a malicious MySQL server, you should disable this option: this capability is unnecessary and inherently dangerous.\n\nTo disable this option, set: %s": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPConfigSetupCheck.php",
"line": 128
}
],
"types": [
null
]
},
"PHP is currently using the older MySQL external driver instead of the newer MySQL native driver. The older driver lacks options and features (like support for query timeouts) which allow Phabricator to interact better with the database.\n\nPhabricator will work with the older driver, but upgrading to the native driver is recommended.\n\nYou may be able to install the native driver with a command like: %s": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPConfigSetupCheck.php",
"line": 97
}
],
"types": [
null
]
},
"PHP is currently using the very old \"mysql\" extension to interact with the database. You should install the newer \"mysqli\" extension to improve behaviors (like error handling and query timeouts).\n\nPhabricator will work with the older extension, but upgrading to the newer extension is recommended.\n\nYou may be able to install the extension with a command like: %s": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPConfigSetupCheck.php",
"line": 75
}
],
"types": [
null
]
},
"PID \"%d\" is not a known Phabricator daemon PID.": {
"uses": [
{
"file": "/applications/daemon/management/PhabricatorDaemonManagementWorkflow.php",
"line": 582
}
],
"types": [
null
]
},
"Path \"%s\" is not known to Phabricator.": {
"uses": [
{
"file": "/applications/repository/management/PhabricatorRepositoryManagementCacheWorkflow.php",
"line": 50
}
],
"types": [
null
]
},
"Phabricator": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 10
},
{
"file": "/applications/config/custom/PhabricatorCustomLogoConfigType.php",
"line": 111
},
{
"file": "/applications/metamta/engine/PhabricatorMailEmailEngine.php",
"line": 244
},
{
"file": "/applications/metamta/engine/PhabricatorMailEmailEngine.php",
"line": 512
},
{
"file": "/view/page/menu/PhabricatorMainMenuView.php",
"line": 337
}
],
"types": []
},
"Phabricator (%s) MFA Code: %s": {
"uses": [
{
"file": "/applications/auth/factor/PhabricatorSMSAuthFactor.php",
"line": 391
}
],
"types": [
null,
null
]
},
"Phabricator Account \"%s\" Approved": {
"uses": [
{
"file": "/applications/people/xaction/PhabricatorUserApproveTransaction.php",
"line": 25
}
],
"types": [
null
]
},
"Phabricator Base URI": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 185
}
],
"types": []
},
"Phabricator Cluster: Database": {
"uses": [
{
"file": "/applications/almanac/servicetype/AlmanacClusterDatabaseServiceType.php",
"line": 13
}
],
"types": []
},
"Phabricator Cluster: Repository": {
"uses": [
{
"file": "/applications/almanac/servicetype/AlmanacClusterRepositoryServiceType.php",
"line": 13
}
],
"types": []
},
"Phabricator Configuation": {
"uses": [
{
"file": "/applications/config/controller/PhabricatorConfigConsoleController.php",
"line": 59
},
{
"file": "/applications/config/controller/PhabricatorConfigConsoleController.php",
"line": 75
}
],
"types": []
},
"Phabricator Configuration": {
"uses": [
{
"file": "/applications/config/editor/PhabricatorConfigEditor.php",
"line": 11
}
],
"types": []
},
"Phabricator Daemons Are Not Running": {
"uses": [
{
"file": "/applications/config/check/PhabricatorDaemonsSetupCheck.php",
"line": 50
}
],
"types": []
},
"Phabricator Form": {
"uses": [
{
"file": "/applications/nuance/source/NuancePhabricatorFormSourceDefinition.php",
"line": 7
}
],
"types": []
},
"Phabricator Instance Name": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 164
},
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 178
}
],
"types": []
},
"Phabricator Mail": {
"uses": [
{
"file": "/applications/metamta/constants/MetaMTAReceivedMailStatus.php",
"line": 24
}
],
"types": []
},
"Phabricator PHP 7 Compatibility Information": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPPreflightSetupCheck.php",
"line": 34
}
],
"types": []
},
"Phabricator Setup Error": {
"uses": [
{
"file": "/applications/config/response/PhabricatorConfigResponse.php",
"line": 24
}
],
"types": []
},
"Phabricator User": {
"uses": [
{
"file": "/applications/uiexample/examples/PHUIBadgeExample.php",
"line": 59
}
],
"types": []
},
"Phabricator Version Information": {
"uses": [
{
"file": "/applications/config/controller/PhabricatorConfigConsoleController.php",
"line": 134
}
],
"types": []
},
"Phabricator allows you to set the visibility of objects (like repositories and tasks) to 'Public', which means **anyone on the internet can see them, without needing to log in or have an account**.\n\nThis is intended for open source projects. Many installs will never want to make anything public, so this policy is disabled by default. You can enable it here, which will let you set the policy for objects to 'Public'.\n\nEnabling this setting will immediately open up some features, like the user directory. Anyone on the internet will be able to access these features.\n\nWith this setting disabled, the 'Public' policy is not available, and the most open policy is 'All Users' (which means users must have accounts and be logged in to view things).": {
"uses": [
{
"file": "/applications/policy/config/PhabricatorPolicyConfigOptions.php",
"line": 40
}
],
"types": []
},
"Phabricator already does not trust OAuth client \"%s\".": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementUntrustOAuthClientWorkflow.php",
"line": 49
}
],
"types": [
null
]
},
"Phabricator already trusts OAuth client \"%s\".": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementTrustOAuthClientWorkflow.php",
"line": 49
}
],
"types": [
null
]
},
"Phabricator appears to be installed on a very small EC2 instance (of class \"%s\") with burstable CPU. This is strongly discouraged. Phabricator regularly needs CPU, and these instances are often choked to death by CPU throttling. Use an instance with a normal CPU instead.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 94
}
],
"types": [
null
]
},
"Phabricator base URI is required.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 119
}
],
"types": []
},
"Phabricator base URI should include protocol (like \"%s\").": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 125
}
],
"types": [
null
]
},
"Phabricator can deliver notifications in real-time with WebSockets.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideInstallModule.php",
"line": 151
}
],
"types": []
},
"Phabricator can highlight PHP by default and use Pygments for other languages if enabled. You can provide a custom highlighter engine by extending class %s.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSyntaxHighlightingConfigOptions.php",
"line": 34
}
],
"types": [
null
]
},
"Phabricator can highlight a few languages by default, but installing and enabling Pygments (a third-party highlighting tool) will add syntax highlighting for many more languages. \n\nFor instructions on installing and enabling Pygments, see the %s configuration option.\n\nIf you do not want to install Pygments, you can ignore this issue.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPygmentSetupCheck.php",
"line": 67
}
],
"types": [
null
]
},
"Phabricator can not process this mail because no application knows how to handle it. Check that the address you sent it to is correct.\n\n(No concrete, enabled subclass of PhabricatorMailReceiver can accept this mail.)": {
"uses": [
{
"file": "/applications/metamta/storage/PhabricatorMetaMTAReceivedMail.php",
"line": 273
}
],
"types": []
},
"Phabricator can send real-time notifications to your web browser or to your desktop. Select where you want to receive these real-time updates.": {
"uses": [
{
"file": "/applications/settings/panel/PhabricatorNotificationsSettingsPanel.php",
"line": 149
}
],
"types": []
},
"Phabricator can serve repositories over HTTP, using HTTP basic auth.\n\nBecause HTTP basic auth is less secure than SSH auth, it is disabled by default. You can enable it here if you'd like to use it anyway. There's nothing fundamentally insecure about it as long as Phabricator uses HTTPS, but it presents a much lower barrier to attackers than SSH does.\n\nConsider using SSH for authenticated access to repositories instead of HTTP.": {
"uses": [
{
"file": "/applications/diffusion/config/PhabricatorDiffusionConfigOptions.php",
"line": 110
}
],
"types": []
},
"Phabricator can use less-secure but mailing list friendly public reply addresses.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 274
}
],
"types": []
},
"Phabricator daemons no longer use PID files.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 544
}
],
"types": []
},
"Phabricator does not support HTTP access to Subversion repositories.": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionServeController.php",
"line": 424
}
],
"types": []
},
"Phabricator has %s available in %s, but the binary exited with an error code when run as %s. Check that it is installed correctly.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPygmentSetupCheck.php",
"line": 45
}
],
"types": [
null,
null,
null
]
},
"Phabricator has application policies which can dictate whether users can take certain actions, such as creating new users. \n\nThis setting allows for \"locking\" these policies such that no further edits can be made on a per-policy basis.": {
"uses": [
{
"file": "/applications/policy/config/PhabricatorPolicyConfigOptions.php",
"line": 62
}
],
"types": []
},
"Phabricator has been successfully installed. These next guides will take you through configuration and new user orientation. These steps are optional, and you can go through them in any order. If you want to get back to this guide later on, you can find it in {icon globe} **Applications** under {icon map-o} **Guides**.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideInstallModule.php",
"line": 164
}
],
"types": []
},
"Phabricator has consistently been unable to reach the writable (\"master\") database while processing recent requests.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 73
}
],
"types": []
},
"Phabricator instance name is required.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 109
}
],
"types": []
},
"Phabricator instance name must contain only lowercase letters, digits, and periods.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 113
}
],
"types": []
},
"Phabricator is configured in cluster mode and the address this request was received on (\"%s\") is not whitelisted as a cluster address.": {
"uses": [
{
"file": "/aphront/configuration/AphrontApplicationConfiguration.php",
"line": 434
}
],
"types": [
null
]
},
"Phabricator is configured in cluster mode, with multiple database hosts. Use \"--host\" to specify which host you want to operate on.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 50
}
],
"types": []
},
"Phabricator is configured to operate in cluster mode, but %s is not defined in the request context. Your webserver configuration needs to forward %s to PHP so Phabricator can reject requests received on external interfaces.": {
"uses": [
{
"file": "/aphront/configuration/AphrontApplicationConfiguration.php",
"line": 422
}
],
"types": [
null,
null
]
},
"Phabricator is configured to use a notification server, but is not able to connect to it.": {
"uses": [
{
"file": "/applications/notification/setup/PhabricatorAphlictSetupCheck.php",
"line": 29
}
],
"types": []
},
"Phabricator is configured to use a notification server, but is unable to connect to it. You should resolve this issue or disable the notification server. It may be helpful to double check your configuration or restart the server using the command below.\n\n%s": {
"uses": [
{
"file": "/applications/notification/setup/PhabricatorAphlictSetupCheck.php",
"line": 10
}
],
"types": [
null
]
},
"Phabricator is configured with an email domain whitelist (in %s), so only users with a verified email address at one of these %s allowed domain(s) will be able to register an account: %s": {
"uses": [
{
"file": "/applications/auth/guidance/PhabricatorAuthProvidersGuidanceEngineExtension.php",
"line": 45
}
],
"types": [
null,
"number",
null
]
},
"Phabricator is configured with multiple master databases, but master \"%s\" is missing a \"partition\" configuration key to define application partitioning.": {
"uses": [
{
"file": "/infrastructure/cluster/PhabricatorDatabaseRefParser.php",
"line": 93
}
],
"types": [
null
]
},
"Phabricator is currently configured in silent mode, so it will not publish webhooks. To adjust this setting, see @{config:phabricator.silent} in Config.": {
"uses": [
{
"file": "/applications/herald/controller/HeraldWebhookViewController.php",
"line": 56
}
],
"types": []
},
"Phabricator is currently configured to serve user uploads directly from the same domain as other content. This is a security risk.\n\nConfigure a CDN (or alternate file domain) to eliminate this risk. Using a CDN will also improve performance. See the guide below for instructions.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorSecuritySetupCheck.php",
"line": 64
}
],
"types": []
},
"Phabricator is currently configured with no writable (\"master\") database, so it can not write new information anywhere. Phabricator will run in read-only mode until an administrator reconfigures it with a writable database.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 38
}
],
"types": []
},
"Phabricator is currently in read-only mode. Use --force to override this mode.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 101
}
],
"types": []
},
"Phabricator is hosting this repository.": {
"uses": [
{
"file": "/applications/diffusion/management/DiffusionRepositoryURIsManagementPanel.php",
"line": 135
}
],
"types": []
},
"Phabricator is in read-only mode (major interruption).": {
"uses": [
{
"file": "/infrastructure/env/PhabricatorEnv.php",
"line": 564
}
],
"types": []
},
"Phabricator is in read-only mode (no writable database is configured).": {
"uses": [
{
"file": "/infrastructure/env/PhabricatorEnv.php",
"line": 557
}
],
"types": []
},
"Phabricator is in read-only mode (unreachable master).": {
"uses": [
{
"file": "/infrastructure/env/PhabricatorEnv.php",
"line": 561
}
],
"types": []
},
"Phabricator is in read-only mode.": {
"uses": [
{
"file": "/infrastructure/env/PhabricatorEnv.php",
"line": 567
}
],
"types": []
},
"Phabricator is not configured in cluster mode.": {
"uses": [
{
"file": "/applications/config/controller/services/PhabricatorConfigClusterDatabasesController.php",
"line": 210
}
],
"types": []
},
"Phabricator is not configured to allow any editor protocols.": {
"uses": [
{
"file": "/applications/settings/panel/PhabricatorExternalEditorSettingsPanel.php",
"line": 132
}
],
"types": []
},
"Phabricator is not configured to serve cluster requests. Set `cluster.addresses` in the configuration to whitelist cluster hosts before sending requests that use a cluster authentication mechanism.": {
"uses": [
{
"file": "/infrastructure/env/PhabricatorEnv.php",
"line": 887
}
],
"types": []
},
"Phabricator is not currently configured to accept inbound mail. You won't be able to interact with objects over email until inbound mail is set up.": {
"uses": [
{
"file": "/applications/meta/controller/PhabricatorApplicationEmailCommandsController.php",
"line": 125
}
],
"types": []
},
"Phabricator is running in silent mode.": {
"uses": [
{
"file": "/applications/doorkeeper/worker/DoorkeeperFeedWorker.php",
"line": 161
}
],
"types": []
},
"Phabricator is running in silent mode. See `%s` in the configuration to change this setting.": {
"uses": [
{
"file": "/applications/metamta/engine/PhabricatorMailEmailEngine.php",
"line": 169
}
],
"types": [
null
]
},
"Phabricator is running in silent mode; declining to mirror.": {
"uses": [
{
"file": "/applications/repository/engine/PhabricatorRepositoryMirrorEngine.php",
"line": 19
}
],
"types": []
},
"Phabricator no longer shows reply hints in mail.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 395
}
],
"types": []
},
"Phabricator no longer supports global customization of monospaced fonts.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 286
}
],
"types": []
},
"Phabricator normally shows diffs in a side-by-side layout on large screens and automatically switches to a unified view on small screens (like mobile phones). If you prefer unified diffs even on large screens, you can select them for use on all displays.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorUnifiedDiffsSetting.php",
"line": 25
}
],
"types": []
},
"Phabricator now always sends transaction mail with \"Precedence: bulk\" to improve deliverability.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 409
}
],
"types": []
},
"Phabricator now automatically discovers available search engines at runtime.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 416
}
],
"types": []
},
"Phabricator now automatically discovers available storage engines at runtime.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 386
}
],
"types": []
},
"Phabricator now automatically selects the best available MySQL implementation.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 472
}
],
"types": []
},
"Phabricator now has application-level management of partitioning and replicas.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 476
}
],
"types": []
},
"Phabricator now has meaningful global access controls. See `%s`.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 349
}
],
"types": [
null
]
},
"Phabricator now manages typeahead strategies automatically.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 359
}
],
"types": []
},
"Phabricator now supports arbitrarily large files. Consult the documentation for configuration details.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 389
}
],
"types": []
},
"Phabricator occasionally shells out to other binaries on the server. An example of this is the `%s` command, used to syntax-highlight code written in languages other than PHP. By default, it is assumed that these binaries are in the %s of the user running Phabricator (normally 'apache', 'httpd', or 'nobody'). Here you can add extra directories to the %s environment variable, for when these binaries are in non-standard locations.\n\nNote that you can also put binaries in `%s` (for example, by symlinking them).\n\nThe current value of PATH after configuration is applied is:\n\n lang=text\n %s": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 203
}
],
"types": [
null,
null,
null,
null,
null
]
},
"Phabricator provides a local disk storage engine, which just writes files to some directory on local disk. The webserver must have read/write permissions on this directory. This is straightforward and suitable for most installs, but will not scale past one web frontend unless the path is actually an NFS mount, since you'll end up with some of the files written to each web frontend and no way for them to share. To use the local disk storage engine, specify the path to a directory here. To disable it, specify null.": {
"uses": [
{
"file": "/applications/files/config/PhabricatorFilesConfigOptions.php",
"line": 184
}
],
"types": []
},
"Phabricator puts databases in a namespace, which defaults to 'phabricator' -- for instance, the Differential database is named 'phabricator_differential' by default. You can change this namespace if you want. Normally, you should not do this unless you are developing Phabricator and using namespaces to separate multiple sandbox datasets.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMySQLConfigOptions.php",
"line": 44
}
],
"types": []
},
"Phabricator received an \"X-Mod-Pagespeed\" or \"X-Page-Speed\" HTTP header on this request, which indicates that you have enabled \"mod_pagespeed\" on this server. This module is not compatible with Phabricator. You should disable it.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 19
}
],
"types": []
},
"Phabricator sent itself a request with \"Accept-Encoding: gzip\", but received an uncompressed response.\n\nThis may indicate that your webserver is not configured to compress responses. If so, you should enable compression. Compression can dramatically improve performance, especially for clients with less bandwidth.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 124
}
],
"types": []
},
"Phabricator sent itself a test request and expected to get a bare JSON response back. It received a JSON response, but the response had extra whitespace at the beginning or end.\n\nThis usually means you have edited a file and left whitespace characters before the opening %s tag, or after a closing %s tag. Remove any leading whitespace, and prefer to omit closing tags.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 176
}
],
"types": [
null,
null
]
},
"Phabricator sent itself a test request that was compressed with \"Content-Encoding: gzip\", but received different bytes than it sent.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 323
}
],
"types": []
},
"Phabricator sent itself a test request with an \"Authorization\" HTTP header, and expected those credentials to be transmitted. However, they were absent or incorrect when received. Phabricator sent username \"%s\" with password \"%s\"; received username \"%s\" and password \"%s\".\n\nYour webserver may not be configured to forward HTTP basic authentication. If you plan to use basic authentication (for example, to access repositories) you should reconfigure it.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 202
}
],
"types": [
null,
null,
null,
null
]
},
"Phabricator sent itself a test request with an HTTP GET parameter, but the parameter was not transmitted. Sent \"%s\" with value \"%s\", got \"%s\" with value \"%s\".\n\nYour webserver is configured incorrectly and large parts of Phabricator will not work until this issue is corrected.\n\n(This problem can be caused by a missing \"QSA\" in your RewriteRule.)": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 261
}
],
"types": [
null,
null,
null,
null
]
},
"Phabricator sent itself a test request with an unusual path, to test if your webserver is rewriting paths correctly. The path was not transmitted correctly.\n\nPhabricator sent a request to path \"%s\", and expected the webserver to decode and rewrite that path so that it received a request for \"%s\". However, it received a request for \"%s\" instead.\n\nVerify that your rewrite rules are configured correctly, following the instructions in the documentation. If path encoding is not working properly you will be unable to access files with unusual names in repositories, among other issues.\n\n(This problem can be caused by a missing \"B\" in your RewriteRule.)": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 225
}
],
"types": [
null,
null,
null
]
},
"Phabricator sent itself a test request with the \"X-Phabricator-SelfCheck\" header and expected to get a valid JSON response back. Instead, the response begins:\n\n%s\n\nSomething is misconfigured or otherwise mangling responses.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 166
}
],
"types": [
null
]
},
"Phabricator stamps mail with labels like `actor(alice)` which can be used to\nwrite client mail rules to organize mail. By default, these stamps are sent\nin an `X-Phabricator-Stamps` header.\n\nIf you use a client which can not use headers to route mail (like Gmail),\nyou can also include the stamps in the message body so mail rules based on\nbody content can route messages.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorEmailStampsSetting.php",
"line": 24
}
],
"types": []
},
"Phabricator supports Git LFS, a Git extension for storing large files alongside a repository. Activate this setting to allow the extension to store file data in Phabricator.": {
"uses": [
{
"file": "/applications/diffusion/config/PhabricatorDiffusionConfigOptions.php",
"line": 129
}
],
"types": []
},
"Phabricator supports syntax highlighting a few languages by default, but you can install Pygments (a third-party syntax highlighting tool) to provide support for many more languages.\n\nTo install Pygments, visit [[ http://pygments.org | pygments.org ]] and follow the download and install instructions.\n\nOnce Pygments is installed, enable this option (`pygments.enabled`) to make Phabricator use Pygments when highlighting source code.\n\nAfter you install and enable Pygments, newly created source code (like diffs and pastes) should highlight correctly. You may need to clear Phabricator's caches to get previously existing source code to highlight. For instructions on managing caches, see [[ %s | Managing Caches ]].": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSyntaxHighlightingConfigOptions.php",
"line": 48
}
],
"types": [
null
]
},
"Phabricator thinks you are using %s, but your client is convinced that it is using %s. This is a serious misconfiguration with subtle, but significant, consequences.": {
"uses": [
{
"file": "/view/page/PhabricatorStandardPageView.php",
"line": 279
}
],
"types": [
null,
null
]
},
"Phabricator users can make requests to other services from the Phabricator host in some circumstances (for example, by creating a repository with a remote URL or having Phabricator fetch an image from a remote server).\n\nThis may represent a security vulnerability if services on the same subnet will accept commands or reveal private information over unauthenticated HTTP GET, based on the source IP address. In particular, all hosts in EC2 have access to such a service.\n\nThis option defines a list of netblocks which Phabricator will decline to connect to. Generally, you should list all private IP space here.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSecurityConfigOptions.php",
"line": 251
}
],
"types": []
},
"Phabricator uses unicode glyphs in page titles to provide a compact representation of the current application. You can substitute plain text instead if these glyphs do not display on your system.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorTitleGlyphsSetting.php",
"line": 25
}
],
"types": []
},
"Phabricator was unable to connect to the writable (\"master\") database while handling this request, and automatically degraded into read-only mode.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 55
}
],
"types": []
},
"Phabricator will automatically login with this provider if it is the only available provider.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthEditController.php",
"line": 274
}
],
"types": []
},
"Phabricator will host this repository.": {
"uses": [
{
"file": "/applications/diffusion/management/DiffusionRepositoryURIsManagementPanel.php",
"line": 133
}
],
"types": []
},
"Phabricator will not push or pull any changes to this URI.": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepositoryURI.php",
"line": 520
}
],
"types": []
},
"Phabricator will not retain a copy of the private key.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthSSHKeyGenerateController.php",
"line": 108
}
],
"types": []
},
"Phabricator will observe a remote repository.": {
"uses": [
{
"file": "/applications/diffusion/management/DiffusionRepositoryURIsManagementPanel.php",
"line": 142
}
],
"types": []
},
"Phabricator will observe changes to this URI and copy them.": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepositoryURI.php",
"line": 504
}
],
"types": []
},
"Phabricator will periodically retry the connection and recover once service is restored. Most causes of persistent service interruption will require administrative intervention in order to restore service.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 79
}
],
"types": []
},
"Phabricator will push a copy of any changes to this URI.": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepositoryURI.php",
"line": 512
}
],
"types": []
},
"Phabricator will serve a read-only copy of the repository from this URI.": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepositoryURI.php",
"line": 528
}
],
"types": []
},
"Phabricator will serve a read/write copy of the repository from this URI.": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepositoryURI.php",
"line": 537
}
],
"types": []
},
"Phabricator will skip email verification for accounts registered through this provider.": {
"uses": [
{
"file": "/applications/auth/controller/config/PhabricatorAuthEditController.php",
"line": 268
}
],
"types": []
},
"PhabricatorMetaMTAApplication": {
"uses": [
{
"file": "/applications/metamta/editor/PhabricatorMetaMTAApplicationEmailEditor.php",
"line": 7
}
],
"types": []
},
"PhabricatorSpacesApplication": {
"uses": [
{
"file": "/applications/spaces/editor/PhabricatorSpacesNamespaceEditor.php",
"line": 7
}
],
"types": []
},
"Phacility High Command": {
"uses": [
{
"file": "/applications/uiexample/examples/PHUIBadgeExample.php",
"line": 22
}
],
"types": []
},
"Process text through remarkup in Phabricator context.": {
"uses": [
{
"file": "/applications/remarkup/conduit/RemarkupProcessConduitAPIMethod.php",
"line": 14
}
],
"types": []
},
"Read-only mode was enabled by the explicit action of a human administrator, so you can get more information about why it has been turned on by rolling your chair away from your desk and yelling \"Hey! Why is Phabricator in read-only mode??!\" using your very loudest outside voice.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 24
}
],
"types": []
},
"Really disable the %s OAuth application? Users will no longer be able to authenticate against it, nor access Phabricator using tokens generated by this application.": {
"uses": [
{
"file": "/applications/oauthserver/controller/client/PhabricatorOAuthClientDisableController.php",
"line": 45
}
],
"types": [
null
]
},
"Receiver '%s' accepts mail to '%s', but is not a subclass of PhabricatorObjectMailReceiver.": {
"uses": [
{
"file": "/applications/metamta/management/PhabricatorMailManagementReceiveTestWorkflow.php",
"line": 154
}
],
"types": [
null,
null
]
},
"Recover access to an account if you have locked yourself out of Phabricator.": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementRecoverWorkflow.php",
"line": 12
}
],
"types": []
},
"Remove %s as an administrator? They will no longer be able to perform administrative functions on this Phabricator install.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleEmpowerController.php",
"line": 46
}
],
"types": [
null
]
},
"Repository \"%s\" exists on more than one device, but no device has any repository version information. Phabricator can not guess which copy of the existing data is authoritative. Promote a device or see \"Ambiguous Leaders\" in the documentation.": {
"uses": [
{
"file": "/applications/diffusion/protocol/DiffusionRepositoryClusterEngine.php",
"line": 275
}
],
"types": [
null
]
},
"Restarting Phabricator": {
"uses": [
{
"file": "/applications/config/view/PhabricatorSetupIssueView.php",
"line": 611
}
],
"types": []
},
"See all the applications included in Phabricator.": {
"uses": [
{
"file": "/applications/guides/module/PhabricatorGuideQuickStartModule.php",
"line": 135
}
],
"types": []
},
"Send \"Welcome to Phabricator\" email with login instructions.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleNewController.php",
"line": 188
}
],
"types": []
},
"Send as Phabricator": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 237
}
],
"types": []
},
"Sent by Phabricator": {
"uses": [
{
"file": "/applications/metamta/controller/PhabricatorMetaMTAMailViewController.php",
"line": 122
}
],
"types": []
},
"Set Phabricator to not trust an OAuth client. Phabricator redirects to trusted OAuth clients that users have authorized without user intervention.": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementUntrustOAuthClientWorkflow.php",
"line": 12
}
],
"types": []
},
"Set Phabricator to trust an OAuth client. Phabricator redirects to trusted OAuth clients that users have authorized without user intervention.": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementTrustOAuthClientWorkflow.php",
"line": 12
}
],
"types": []
},
"Set a '%s' in your Phabricator configuration!": {
"uses": [
{
"file": "/infrastructure/util/PhabricatorHash.php",
"line": 25
}
],
"types": [
null
]
},
"Set a string Phabricator should use to prefix cookie names.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 122
}
],
"types": []
},
"Set the URI where Phabricator is installed. Setting this improves security by preventing cookies from being set on other domains, and allows daemons to send emails with links that have the correct domain.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 78
}
],
"types": []
},
"Sets the default color scheme of Phabricator.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorUIConfigOptions.php",
"line": 54
}
],
"types": []
},
"Should Phabricator use Pygments to highlight code?": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSyntaxHighlightingConfigOptions.php",
"line": 40
}
],
"types": []
},
"Show old methods which will be deleted in a future version of Phabricator.": {
"uses": [
{
"file": "/applications/conduit/query/PhabricatorConduitSearchEngine.php",
"line": 90
}
],
"types": []
},
"Signature Required to use Phabricator": {
"uses": [
{
"file": "/applications/legalpad/editor/LegalpadDocumentEditEngine.php",
"line": 134
}
],
"types": []
},
"Some of these errors are caused by access control problems. The user you are connecting with does not have permission to see all of the database or tables that Phabricator uses. You need to GRANT the user more permission, or use a different user.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 845
}
],
"types": []
},
"Some of these errors are caused by surplus schemata (extra tables or columns which Phabricator does not expect). These are not serious. For information on resolving these issues, see the \"Surplus Schemata\" section in the \"Managing Storage Adjustments\" article in the documentation.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 853
}
],
"types": []
},
"Specified version control system must be a VCS recognized by Phabricator. Valid systems are: %s.": {
"uses": [
{
"file": "/applications/repository/xaction/PhabricatorRepositoryVCSTransaction.php",
"line": 50
}
],
"types": [
null
]
},
"Specify a system user to run the daemons as. Primarily, this user will own the working copies of any repositories that Phabricator imports or manages. This option is new and experimental.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorPHDConfigOptions.php",
"line": 51
}
],
"types": []
},
"Start the standard configured collection of Phabricator daemons. This is appropriate for most installs. Use **%s** to customize which daemons are launched.": {
"uses": [
{
"file": "/applications/daemon/management/PhabricatorDaemonManagementStartWorkflow.php",
"line": 11
}
],
"types": [
null
]
},
"Start typing to autocomplete on commit title, or give a Phabricator commit identifier like rFOO1234.": {
"uses": [
{
"file": "/applications/releeph/controller/request/ReleephRequestEditController.php",
"line": 266
}
],
"types": []
},
"Stop Phabricator from sending any email, etc.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 265
}
],
"types": []
},
"Stop all daemon processes on this host, even if they belong to another Phabricator instance.": {
"uses": [
{
"file": "/applications/daemon/management/PhabricatorDaemonManagementRestartWorkflow.php",
"line": 26
},
{
"file": "/applications/daemon/management/PhabricatorDaemonManagementStopWorkflow.php",
"line": 23
}
],
"types": []
},
"Stores a reference to file data which has been uploaded to Phabricator.": {
"uses": [
{
"file": "/applications/harbormaster/artifact/HarbormasterFileArtifact.php",
"line": 13
}
],
"types": []
},
"The \"%s\" setting is currently disabled in your PHP configuration, but Phabricator is running in development mode. This option should normally be enabled in development so you do not need to restart anything after making changes to the code.": {
"uses": [
{
"file": "/applications/cache/spec/PhabricatorOpcodeCacheSpec.php",
"line": 87
}
],
"types": [
null
]
},
"The \"feed.http-hooks\" option is deprecated in favor of Webhooks. This option will be removed in a future version of Phabricator.\n\nYou can configure Webhooks in Herald.\n\nTo resolve this issue, remove all URIs from \"feed.http-hooks\".": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 192
}
],
"types": []
},
"The '%s' binary could not be found. Set the webserver's %s environmental variable to include the directory where it resides, or add that directory to '%s' in the Phabricator configuration.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBinariesSetupCheck.php",
"line": 169
}
],
"types": [
null,
null,
null
]
},
"The '%s' binary could not be found. Symlink it into '%s', or set the webserver's %s environmental variable to include the directory where it resides, or add that directory to '%s' in the Phabricator configuration.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBinariesSetupCheck.php",
"line": 177
}
],
"types": [
null,
null,
null,
null
]
},
"The '%s' extension has support for only some image types. Phabricator will be unable to process images of the missing types until you build '%s' with support for them. Supported types: %s. Missing types: %s.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorGDSetupCheck.php",
"line": 43
}
],
"types": [
null,
null,
null,
null
]
},
"The '%s' extension is not installed. Without '%s', support, Phabricator may not be able to determine the MIME types of uploaded files.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorFileinfoSetupCheck.php",
"line": 12
}
],
"types": [
null,
null
]
},
"The '%s' extension is not installed. Without '%s', support, Phabricator will not be able to process or resize images (for example, to generate thumbnails). Install or enable '%s'.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorGDSetupCheck.php",
"line": 12
}
],
"types": [
null,
null,
null
]
},
"The APC or APCu PHP extensions are installed, but not enabled in your PHP configuration. Enabling these extensions will improve Phabricator performance. Edit the \"%s\" setting to enable these extensions.": {
"uses": [
{
"file": "/applications/cache/spec/PhabricatorCacheSpec.php",
"line": 98
}
],
"types": [
null
]
},
"The Multimeter application collects performance samples. You can use this data to help you understand what Phabricator is spending time and resources doing, and to identify problematic access patterns.\n\nThis option controls how frequently sampling activates. Set it to some positive integer N to sample every 1 / N pages.\n\nFor most installs, the default value (1 sample per 1000 pages) should collect enough data to be useful without requiring much storage or meaningfully impacting performance. If you're investigating performance issues, you can adjust the rate in order to collect more data.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorDeveloperConfigOptions.php",
"line": 130
}
],
"types": []
},
"The PHID of the repository in Phabricator.": {
"uses": [
{
"file": "/applications/differential/storage/DifferentialDiff.php",
"line": 552
},
{
"file": "/applications/repository/storage/PhabricatorRepositoryCommit.php",
"line": 679
}
],
"types": []
},
"The PHP \"Zend OPcache\" extension is installed, but not enabled in your PHP configuration. Enabling it will dramatically improve Phabricator performance. Edit the \"%s\" setting to enable the extension.": {
"uses": [
{
"file": "/applications/cache/spec/PhabricatorOpcodeCacheSpec.php",
"line": 175
}
],
"types": [
null
]
},
"The PHP 'openssl' extension is not installed. You must install this extension in order to add a JIRA authentication provider, because JIRA OAuth requests use the RSA-SHA1 signing algorithm. Install the 'openssl' extension, restart Phabricator, and try again.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorJIRAAuthProvider.php",
"line": 169
}
],
"types": []
},
"The Phabricator daemons are not running, so Phabricator will not be able to perform background processing (including sending email, rebuilding search indexes, importing commits, cleaning up old data, and running builds).\n\nUse %s to start daemons. See %s for more information.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorDaemonsSetupCheck.php",
"line": 33
}
],
"types": [
null,
null
]
},
"The URI where the OAuth server instance of Phabricator is installed. For example: %s": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorPhabricatorAuthProvider.php",
"line": 190
}
],
"types": [
null
]
},
"The account you are attempting to register with has an invalid email address (%s). This Phabricator install only allows registration with specific email addresses:": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 124
}
],
"types": [
null
]
},
"The application search engine \"%s\" is not known to Phabricator!": {
"uses": [
{
"file": "/applications/dashboard/paneltype/PhabricatorDashboardQueryPanelType.php",
"line": 197
}
],
"types": [
null
]
},
"The base URI for this install is not configured, and major features will not work properly until you configure it.\n\nYou should set the base URI to the URI you will use to access Phabricator, like \"http://phabricator.example.com/\".\n\nInclude the protocol (http or https), domain name, and port number if you are using a port other than 80 (http) or 443 (https).\n\nBased on this request, it appears that the correct setting is:\n\n%s\n\nTo configure the base URI, run the command shown below.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBaseURISetupCheck.php",
"line": 75
}
],
"types": [
null
]
},
"The callsign of the repository in Phabricator.": {
"uses": [
{
"file": "/applications/differential/storage/DifferentialDiff.php",
"line": 550
},
{
"file": "/applications/repository/storage/PhabricatorRepositoryCommit.php",
"line": 677
}
],
"types": []
},
"The configuration option '%s' is not recognized. It may be misspelled, or it might have existed in an older version of Phabricator. It has no effect, and should be corrected or deleted.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 41
}
],
"types": [
null
]
},
"The configuration value \"%s\" is locked (so it can not be edited from the web UI), but has a database value. Usually, this means that it was previously not locked, you set it using the web UI, and it later became locked.\n\nYou should copy this configuration value to a local configuration source (usually by using %s) and then remove it from the database with the command below.\n\nFor more information on locked and hidden configuration, including details about this setup issue, see %s.\n\nThis database value is currently respected, but a future version of Phabricator will stop respecting database values for locked configuration options.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorExtraConfigSetupCheck.php",
"line": 145
}
],
"types": [
null,
null,
null
]
},
"The configured PATH includes a component which is not usable. Phabricator will be unable to find or execute binaries located here:\n\n%s\n\nThe user that the webserver runs as must be able to read all the directories in PATH in order to make use of them.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPathSetupCheck.php",
"line": 122
}
],
"types": [
null
]
},
"The current Phabricator configuration has these %d value(s):": {
"uses": [
{
"file": "/applications/config/view/PhabricatorSetupIssueView.php",
"line": 252
}
],
"types": [
null
]
},
"The default location in which to store working copies and other data about repositories. Phabricator will control and manage data here, so you should **not** choose an existing directory full of data you care about.": {
"uses": [
{
"file": "/applications/repository/config/PhabricatorRepositoryConfigOptions.php",
"line": 30
}
],
"types": []
},
"The directory for local repositories (%s) does not exist, or is not readable by the webserver. Phabricator uses this directory to store information about repositories. If this directory does not exist, create it:\n\n%s\nIf this directory exists, make it readable to the webserver. You can also edit the configuration below to use some other directory.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorRepositoriesSetupCheck.php",
"line": 47
}
],
"types": [
null,
null
]
},
"The email address (\"%s\") associated with the external account is already in use by an existing Phabricator account. Multiple Phabricator accounts may not have the same email address, so you can not use this email address to register a new Phabricator account.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 164
}
],
"types": [
null
]
},
"The email address associated with this account (\"%s\") is already in use by an application and can not be used to register a new Phabricator account. Choose a different, valid address.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 103
}
],
"types": [
null
]
},
"The email address associated with this external account (\"%s\") is not a valid email address and can not be used to register a Phabricator account. Choose a different, valid address.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 85
}
],
"types": [
null
]
},
"The environmental variable %s is empty. Phabricator needs to execute some system commands, like `%s`, `%s`, `%s`, and `%s`. To execute these commands, the binaries must be available in the webserver's %s. You can set additional paths in Phabricator configuration.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPathSetupCheck.php",
"line": 21
}
],
"types": [
null,
null,
null,
null,
null,
null
]
},
"The environmental variable %s is empty. Phabricator will not be able to execute some commands.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPathSetupCheck.php",
"line": 16
}
],
"types": [
null
]
},
"The external account (\"%s\") you just authenticated with is not configured to allow account linking on this Phabricator install. An administrator may have recently disabled it.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthLoginController.php",
"line": 151
}
],
"types": [
null
]
},
"The external account (\"%s\") you just authenticated with is not configured to allow logins on this Phabricator install. An administrator may have recently disabled it.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthLoginController.php",
"line": 83
}
],
"types": [
null
]
},
"The external account (\"%s\") you just authenticated with is not configured to allow registration on this Phabricator install. An administrator may have recently disabled it.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthLoginController.php",
"line": 112
}
],
"types": [
null
]
},
"The external account (\"%s\") you just used to log in is already associated with another Phabricator user account. Log in to the other Phabricator account and unlink the external account before linking it to a new Phabricator account.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthLoginController.php",
"line": 97
}
],
"types": [
null
]
},
"The external account you are registering with has an email address that is already in use (\"%s\") by an existing Phabricator account. Choose a new, valid email address to register a new Phabricator account.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 189
}
],
"types": [
null
]
},
"The external account you just logged in with is not associated with a valid Phabricator user.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthLoginController.php",
"line": 171
}
],
"types": []
},
"The mapping from VCS users to Phabricator users has changed and must be rebuilt.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorManualActivitySetupCheck.php",
"line": 87
}
],
"types": []
},
"The namespace that Phabricator databases should use.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMySQLConfigOptions.php",
"line": 41
}
],
"types": []
},
"The object being edited does not implement any standard interfaces (like PhabricatorSubscribableInterface) which allow CCs to be generated automatically. Override the \"getMailCC()\" method and generate CCs explicitly.": {
"uses": [
{
"file": "/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php",
"line": 3413
}
],
"types": []
},
"The public key corresponding to the given private key is not yet known to Phabricator. Associate the public key with an Almanac device in the web interface before registering hosts with it.": {
"uses": [
{
"file": "/applications/almanac/management/AlmanacManagementRegisterWorkflow.php",
"line": 150
}
],
"types": []
},
"The request body Phabricator received began:": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 349
}
],
"types": []
},
"The request body Phabricator sent began:": {
"uses": [
{
"file": "/applications/config/check/PhabricatorWebServerSetupCheck.php",
"line": 345
}
],
"types": []
},
"The timezone Phabricator should use.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 112
}
],
"types": []
},
"The version of %s on this system is out of date and contains a major, widely disclosed vulnerability (the \"Shellshock\" vulnerability).\n\nUpgrade %s to a patched version.\n\nTo learn more about how this issue affects Phabricator, see %s.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorSecuritySetupCheck.php",
"line": 28
}
],
"types": [
null,
null,
null
]
},
"The way Phabricator attributes VCS activity to Phabricator users has changed. There is a new indirection layer between the strings that appear as VCS authors and committers (such as \"John Developer <johnd@bigcorp.com>\") and the Phabricator user that gets associated with VCS commits. This is to support situations where users are incorrectly associated with commits by Phabricator making bad guesses about the identity of the corresponding Phabricator user. This also helps with situations where existing repositories are imported without having created accounts for all the committers to that repository. Until you rebuild these repository identities, you are likely to encounter problems with future Phabricator features which will rely on the existence of these identities.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorManualActivitySetupCheck.php",
"line": 93
}
],
"types": []
},
"The working copy for this repository (\"%s\") has not been cloned yet on this machine (\"%s\"). Make sure you havestarted the Phabricator daemons. If this problem persists for longer than a clone should take, check the daemon logs (in the Daemon Console) to see if there were errors cloning the repository. Consult the \"Diffusion User Guide\" in the documentation for help setting up repositories.": {
"uses": [
{
"file": "/applications/diffusion/request/DiffusionRequest.php",
"line": 563
}
],
"types": [
null,
null
]
},
"These alternative URIs will be able to access 'normal' pages on your Phabricator install. Other features such as OAuth won't work. The major use case for this is moving installs across domains.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 102
}
],
"types": []
},
"This Phabricator install is configured as \"%s\", but you are using the domain name \"%s\" to access a page which is trying to set a cookie. Access Phabricator on the configured primary domain or a configured alternate domain. Phabricator will not set cookies on other domains for security reasons.": {
"uses": [
{
"file": "/aphront/AphrontRequest.php",
"line": 590
}
],
"types": [
null,
null
]
},
"This Phabricator install is not configured with any enabled authentication providers which can be used to log in. If you have accidentally locked yourself out by disabling all providers, you can use `%s` to recover access to an account.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthStartController.php",
"line": 93
}
],
"types": [
null
]
},
"This application (\"%s\") is authorized to use your Phabricator credentials. Continue to complete the authentication workflow.": {
"uses": [
{
"file": "/applications/oauthserver/controller/PhabricatorOAuthServerAuthController.php",
"line": 212
}
],
"types": [
null
]
},
"This application also requested additional unrecognized permissions. These permissions may have existed in an older version of Phabricator, or may be from a future version of Phabricator. They will not be granted.": {
"uses": [
{
"file": "/applications/oauthserver/controller/PhabricatorOAuthServerAuthController.php",
"line": 272
}
],
"types": []
},
"This application cannot be uninstalled, because it is required for Phabricator to work.": {
"uses": [
{
"file": "/applications/meta/controller/PhabricatorApplicationUninstallController.php",
"line": 117
}
],
"types": []
},
"This application is required for Phabricator to operate, so all users must have access to it.": {
"uses": [
{
"file": "/applications/base/PhabricatorApplication.php",
"line": 560
}
],
"types": []
},
"This application will no longer be able to access Phabricator on your behalf.": {
"uses": [
{
"file": "/applications/oauthserver/panel/PhabricatorOAuthServerAuthorizationsSettingsPanel.php",
"line": 71
}
],
"types": []
},
"This browser has been granted permission to send desktop notifications for this Phabricator instance.": {
"uses": [
{
"file": "/applications/settings/panel/PhabricatorNotificationsSettingsPanel.php",
"line": 86
}
],
"types": []
},
"This browser has denied permission to send desktop notifications for this Phabricator instance. Consult your browser settings / documentation to figure out how to clear this setting, do so, and then re-visit this page to grant permission.": {
"uses": [
{
"file": "/applications/settings/panel/PhabricatorNotificationsSettingsPanel.php",
"line": 91
}
],
"types": []
},
"This browser has not yet granted permission to send desktop notifications for this Phabricator instance.": {
"uses": [
{
"file": "/applications/settings/panel/PhabricatorNotificationsSettingsPanel.php",
"line": 71
}
],
"types": []
},
"This configuration option is unknown. It may be misspelled, or have existed in a previous version of Phabricator.": {
"uses": [
{
"file": "/applications/config/controller/settings/PhabricatorConfigEditController.php",
"line": 20
}
],
"types": []
},
"This email address (%s) is no longer your primary email address. Going forward, Phabricator will send all email to your new primary email address (%s).": {
"uses": [
{
"file": "/applications/people/storage/PhabricatorUserEmail.php",
"line": 244
}
],
"types": [
null,
null
]
},
"This email was sent from an email address (\"%s\") that is not associated with a Phabricator account. To interact with Phabricator via email, add this address to your account.": {
"uses": [
{
"file": "/applications/metamta/storage/PhabricatorMetaMTAReceivedMail.php",
"line": 265
}
],
"types": [
null
]
},
"This factor has been removed from your device, so Phabricator can not send you a challenge. To continue, an administrator must strip this factor from your account.": {
"uses": [
{
"file": "/applications/auth/factor/PhabricatorDuoAuthFactor.php",
"line": 513
}
],
"types": []
},
"This is a terse test text message from Phabricator (%s).": {
"uses": [
{
"file": "/applications/auth/controller/contact/PhabricatorAuthContactNumberTestController.php",
"line": 42
}
],
"types": [
null
]
},
"This is an advanced feature which should normally be used only when building a Phabricator cluster. This feature is very dangerous if misused.": {
"uses": [
{
"file": "/applications/almanac/management/AlmanacManagementTrustKeyWorkflow.php",
"line": 69
}
],
"types": []
},
"This is now your primary email address (%s). Going forward, Phabricator will send all email here.": {
"uses": [
{
"file": "/applications/people/storage/PhabricatorUserEmail.php",
"line": 278
}
],
"types": [
null
]
},
"This is very unusual and will leave you without any content on the Phabricator home page. You should only do this if you are certain you know what you are doing.": {
"uses": [
{
"file": "/applications/meta/controller/PhabricatorApplicationUninstallController.php",
"line": 100
}
],
"types": []
},
"This mail is addressed to the public email address of an object (\"%s\"), but public replies are not enabled on this Phabricator install. An administrator may have recently disabled this setting, or you may have replied to an old message. Try replying to a more recent message instead.": {
"uses": [
{
"file": "/applications/metamta/receiver/PhabricatorObjectMailReceiver.php",
"line": 74
}
],
"types": [
null
]
},
"This may also indicate that a more serious failure has occurred. If this interruption does not resolve on its own, Phabricator will soon detect the persistent disruption and degrade into read-only mode until the issue is resolved.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 64
}
],
"types": []
},
"This may happen if there is a temporary network anomaly on the server side, like cosmic radiation or spooky ghosts. If this failure was caused by a transient service interruption, Phabricator will recover momentarily.": {
"uses": [
{
"file": "/applications/system/controller/PhabricatorSystemReadOnlyController.php",
"line": 59
}
],
"types": []
},
"This message is a response to another email message, and this recipient received the original email message, so we are not sending them this substantially similar message (for example, the sender used \"Reply All\" instead of \"Reply\" in response to mail from Phabricator).": {
"uses": [
{
"file": "/applications/metamta/query/PhabricatorMetaMTAActor.php",
"line": 142
}
],
"types": []
},
"This object is public and can be viewed by anyone, even if they do not have a Phabricator account.": {
"uses": [
{
"file": "/applications/policy/storage/PhabricatorPolicy.php",
"line": 250
}
],
"types": []
},
"This option allows you to stop Phabricator from sending data to most external\nservices: it will disable email, SMS, repository mirroring, remote builds,\nDoorkeeper writes, and webhooks.\n\nThis option is intended to allow a Phabricator instance to be exported, copied,\nimported, and run in a test environment without impacting users. For example,\nif you are migrating to new hardware, you could perform a test migration first\nwith this flag set, make sure things work, and then do a production cutover\nlater with higher confidence and less disruption.\n\nWithout making use of this flag to silence the temporary test environment,\nusers would receive duplicate email during the time the test instance and old\nproduction instance were both in operation.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 40
}
],
"types": []
},
"This option controls whether users can edit account email addresses and profile real names.\n\nIf you set up Phabricator to automatically synchronize account information from some other authoritative system, you can prevent users from making these edits to ensure information remains consistent across both systems.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorAuthenticationConfigOptions.php",
"line": 107
}
],
"types": []
},
"This panel has type \"%s\", but that panel type is not known to Phabricator.": {
"uses": [
{
"file": "/applications/dashboard/engine/PhabricatorDashboardPanelRenderingEngine.php",
"line": 143
}
],
"types": [
null
]
},
"This repository can not be protected from dangerous changes because Phabricator does not control what users are allowed to push to it.": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionRepositoryEditDangerousController.php",
"line": 25
}
],
"types": []
},
"This repository can not be protected from enormous changes because Phabricator does not control what users are allowed to push to it.": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionRepositoryEditEnormousController.php",
"line": 25
}
],
"types": []
},
"This repository is hosted remotely. Phabricator is observing it.": {
"uses": [
{
"file": "/applications/diffusion/management/DiffusionRepositoryURIsManagementPanel.php",
"line": 145
}
],
"types": []
},
"This repository request (for repository \"%s\") has been incorrectly routed to a cluster host (with device name \"%s\", and hostname \"%s\") which can not serve the request.\n\nThe Almanac device address for the correct device may improperly point at this host, or the \"device.id\" configuration file on this host may be incorrect.\n\nRequests routed within the cluster by Phabricator are always expected to be sent to a node which can serve the request. To prevent loops, this request will not be proxied again.\n\n%s": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepository.php",
"line": 1938
}
],
"types": [
null,
null,
null,
null
]
},
"This request did not include a \"Host\" header. This may mean that your webserver (like nginx or apache) is misconfigured so the \"Host\" header is not making it to Phabricator, or that you are making a raw request without a \"Host\" header using a tool or library.\n\nIf you are using a web browser, check your webserver configuration. If you are using a tool or library, check how the request is being constructed.\n\nIt is also possible (but very unlikely) that some other network device (like a load balancer) is stripping the header.\n\nRequests must include a valid \"Host\" header.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBaseURISetupCheck.php",
"line": 18
}
],
"types": []
},
"This request included an invalid \"Host\" header, with value \"%s\". Host headers must contain a dot (\".\"), like \"example.com\". This is required for some browsers to be able to set cookies.\n\nThis may mean the base URI is configured incorrectly. You must serve Phabricator from a base URI with a dot (like \"https://phabricator.mycompany.com\"), not a bare domain (like \"https://phabricator/\"). If you are trying to use a bare domain, change your configuration to use a full domain with a dot in it instead.\n\nThis might also mean that your webserver (or some other network device, like a load balancer) is mangling the \"Host\" header, or you are using a tool or library to issue a request manually and setting the wrong \"Host\" header.\n\nRequests must include a valid \"Host\" header.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBaseURISetupCheck.php",
"line": 36
}
],
"types": [
null
]
},
"This request originates from outside of the Phabricator cluster address range. Requests signed with cluster API tokens must originate from within the cluster.": {
"uses": [
{
"file": "/applications/conduit/controller/PhabricatorConduitAPIController.php",
"line": 367
}
],
"types": []
},
"This request originates from outside of the Phabricator cluster address range. Requests signed with trusted device keys must originate from within the cluster.": {
"uses": [
{
"file": "/applications/conduit/controller/PhabricatorConduitAPIController.php",
"line": 264
}
],
"types": []
},
"This rule was created with a newer version of Herald. You can not view or edit it in this older version. Upgrade your Phabricator deployment.": {
"uses": [
{
"file": "/applications/herald/controller/HeraldRuleController.php",
"line": 110
}
],
"types": []
},
"This token is automatically generated by Phabricator, and used to make requests between nodes in a Phabricator cluster. You can not use this token in external applications.": {
"uses": [
{
"file": "/applications/conduit/controller/PhabricatorConduitTokenEditController.php",
"line": 90
}
],
"types": []
},
"This workflow will send this user (\"%s\") a copy of the \"Welcome to Phabricator\" email that users normally receive when their accounts are created by an administrator.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleWelcomeController.php",
"line": 70
}
],
"types": [
null
]
},
"To access repositories hosted by Phabricator over HTTP, you must set a version control password. This password should be unique.\n\nThis password applies to all repositories available over HTTP.": {
"uses": [
{
"file": "/applications/diffusion/panel/DiffusionSetPasswordSettingsPanel.php",
"line": 117
}
],
"types": []
},
"To add custom hook scripts to this repository, add them to this directory.\n\nPhabricator will run any executables in this directory after running its own checks, as though they were normal hook scripts.": {
"uses": [
{
"file": "/applications/repository/engine/PhabricatorRepositoryPullEngine.php",
"line": 228
}
],
"types": []
},
"To configure GitHub OAuth, create a new GitHub Application here:\n\nhttps://github.com/settings/applications/new\n\nYou should use these settings in your application:\n\n - **URL:** Set this to your full domain with protocol. For this Phabricator install, the correct value is: `%s`\n - **Callback URL**: Set this to: `%s`\n\n\nOnce you've created an application, copy the **Client ID** and **Client Secret** into the fields above.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorGitHubAuthProvider.php",
"line": 15
}
],
"types": [
null,
null
]
},
"To configure WordPress.com OAuth, create a new WordPress.com Application here:\n\nhttps://developer.wordpress.com/apps/new/.\n\nYou should use these settings in your application:\n\n - **URL:** Set this to your full domain with protocol. For this Phabricator install, the correct value is: `%s`\n - **Redirect URL**: Set this to: `%s`\n\n\nOnce you've created an application, copy the **Client ID** and **Client Secret** into the fields above.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorWordPressAuthProvider.php",
"line": 15
}
],
"types": [
null,
null
]
},
"To enable the Phabricator SSH error log, specify a path. Errors occurring in contexts where Phabricator is serving SSH requests will be written to this log.\n\nIf not set, no log will be written.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorAccessLogConfigOptions.php",
"line": 124
}
],
"types": []
},
"To enable the Phabricator SSH log, specify a path. The access log can provide more detailed information about SSH access than a normal SSH log (for instance, it can show logged-in users, commands, and other application data).\n\nIf not set, no log will be written.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorAccessLogConfigOptions.php",
"line": 101
}
],
"types": []
},
"To enable the Phabricator access log, specify a path. The Phabricator access than normal HTTP access logs (for instance, it can show logged-in users, controllers, and other application data).\n\nIf not set, no log will be written.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorAccessLogConfigOptions.php",
"line": 76
}
],
"types": []
},
"To invite users to Phabricator, enter their email addresses below. Separate addresses with commas or newlines.": {
"uses": [
{
"file": "/applications/people/controller/PhabricatorPeopleInviteSendController.php",
"line": 177
}
],
"types": []
},
"To learn more about how Phabricator updates repositories, read %s in the documentation.": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionRepositoryEditUpdateController.php",
"line": 60
}
],
"types": [
null
]
},
"To log in to Phabricator, follow this link and set a password:": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleWelcomeMailEngine.php",
"line": 83
}
],
"types": []
},
"To manage prototypes, enable them by setting %s in your Phabricator configuration.": {
"uses": [
{
"file": "/applications/meta/controller/PhabricatorApplicationUninstallController.php",
"line": 40
}
],
"types": [
null
]
},
"To render more than %s levels of panels nested inside other panels, purchase a subscription to Phabricator Gold.": {
"uses": [
{
"file": "/applications/dashboard/engine/PhabricatorDashboardPanelRenderingEngine.php",
"line": 427
}
],
"types": [
"number"
]
},
"Trusting a public key gives anyone holding the corresponding private key complete, unrestricted access to all data in Phabricator. The private key will be able to sign requests that skip policy and security checks.": {
"uses": [
{
"file": "/applications/almanac/management/AlmanacManagementTrustKeyWorkflow.php",
"line": 63
}
],
"types": []
},
"URI where Phabricator is installed.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorCoreConfigOptions.php",
"line": 75
}
],
"types": []
},
"Unable to connect to MySQL!\n\n%s\n\nMake sure Phabricator and MySQL are correctly configured.": {
"uses": [
{
"file": "/applications/config/issue/PhabricatorSetupIssue.php",
"line": 29
}
],
"types": [
null
]
},
"Unable to determine the username to connect with when trying to proxy an SSH request within the Phabricator cluster.": {
"uses": [
{
"file": "/applications/diffusion/ssh/DiffusionSSHWorkflow.php",
"line": 119
}
],
"types": []
},
"Unable to determine the version number of \"%s\". Usually, this means the program changed its version format string recently and Phabricator does not know how to parse the new one yet, but might indicate that you have a very old (or broken) binary.\n\nBecause we can not determine the version number, checks against minimum and known-bad versions will be skipped, so we might fail to detect an incompatible binary.\n\nYou may be able to resolve this issue by updating Phabricator, since a newer version of Phabricator is likely to be able to parse the newer version string.\n\nIf updating Phabricator does not fix this, you can report the issue to the upstream so we can adjust the parser.\n\nIf you are confident you have a recent version of \"%s\" installed and working correctly, it is usually safe to ignore this warning.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBinariesSetupCheck.php",
"line": 202
}
],
"types": [
null,
null
]
},
"Unable to establish a write-mode connection (to application database \"%s\") because Phabricator is in read-only mode. Whatever you are trying to do does not function correctly in read-only mode.": {
"uses": [
{
"file": "/infrastructure/storage/lisk/PhabricatorLiskDAO.php",
"line": 140
}
],
"types": [
null
]
},
"Unable to read device private key while attempting to make authenticated method call within the Phabricator cluster. Use `%s` to register keys for this device. Exception: %s": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepository.php",
"line": 2222
}
],
"types": [
null,
null
]
},
"Unable to read device public key while attempting to make authenticated method call within the Phabricator cluster. Use `%s` to register keys for this device. Exception: %s": {
"uses": [
{
"file": "/applications/repository/storage/PhabricatorRepository.php",
"line": 2207
}
],
"types": [
null,
null
]
},
"Updated; Phabricator does not trust OAuth client %s.": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementUntrustOAuthClientWorkflow.php",
"line": 60
}
],
"types": [
null
]
},
"Updated; Phabricator trusts OAuth client %s.": {
"uses": [
{
"file": "/applications/auth/management/PhabricatorAuthManagementTrustOAuthClientWorkflow.php",
"line": 60
}
],
"types": [
null
]
},
"Upload a file from a host to Phabricator.": {
"uses": [
{
"file": "/applications/harbormaster/step/HarbormasterUploadArtifactBuildStepImplementation.php",
"line": 11
}
],
"types": []
},
"Use Phabricator Username": {
"uses": [
{
"file": "/applications/auth/factor/PhabricatorDuoAuthFactor.php",
"line": 136
}
],
"types": []
},
"Used if the \"From:\" address does not map to a user account. Setting a default author will allow anyone on the public internet to create objects in Phabricator by sending email to this address.": {
"uses": [
{
"file": "/applications/metamta/applicationpanel/PhabricatorMetaMTAApplicationEmailPanel.php",
"line": 265
}
],
"types": []
},
"Using the Phabricator OAuth Server": {
"uses": [
{
"file": "/applications/oauthserver/application/PhabricatorOAuthServerApplication.php",
"line": 40
}
],
"types": []
},
"WARNING: The \"Track Only\" feature is deprecated. Use \"Fetch Refs\" and \"Permanent Refs\" instead. This feature will be removed in a future version of Phabricator.": {
"uses": [
{
"file": "/applications/diffusion/editor/DiffusionRepositoryEditEngine.php",
"line": 257
}
],
"types": []
},
"WARNING: This is a prototype option and the description below is currently pure\nfantasy.\n\nThis option allows you to make Phabricator aware of database read replicas so\nit can monitor database health, spread load, and degrade gracefully to\nread-only mode in the event of a failure on the primary host. For help with\nconfiguring cluster databases, see **[[ %s | %s ]]** in the documentation.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorClusterConfigOptions.php",
"line": 24
}
],
"types": [
null,
null
]
},
"WARNING: This is a prototype option and the description below is currently pure fantasy.\n\nSwitch Phabricator to read-only mode. In this mode, users will be unable to write new data. Normally, the cluster degrades into this mode automatically when it detects that the database master is unreachable, but you can activate it manually in order to perform maintenance or test configuration.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorClusterConfigOptions.php",
"line": 115
}
],
"types": []
},
"WARNING: This is a very advanced option, and only useful for hosting providers running multi-tenant clusters.\n\nIf you provide an instance identifier here (normally by injecting it with a `%s`), Phabricator will pass it to subprocesses and commit hooks in the `%s` environmental variable.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorClusterConfigOptions.php",
"line": 100
}
],
"types": [
null,
null
]
},
"Welcome to Phabricator": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 598
},
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 610
},
{
"file": "/applications/auth/controller/PhabricatorAuthOneTimeLoginController.php",
"line": 154
}
],
"types": []
},
"Welcome to Phabricator!": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthController.php",
"line": 257
},
{
"file": "/applications/people/mail/PhabricatorPeopleWelcomeMailEngine.php",
"line": 63
}
],
"types": []
},
"When Phabricator creates tasks in Asana, it can add the tasks to Asana projects based on which application the corresponding object in Phabricator comes from. For example, you can add code reviews in Asana to a \"Differential\" project.\n\nNOTE: This feature is new and experimental.": {
"uses": [
{
"file": "/applications/doorkeeper/option/PhabricatorAsanaConfigOptions.php",
"line": 36
}
],
"types": []
},
"When a message is sent to multiple recipients (for example, several reviewers on\na code review), Phabricator can either deliver one email to everyone (e.g., \"To:\nalincoln, usgrant, htaft\") or separate emails to each user (e.g., \"To:\nalincoln\", \"To: usgrant\", \"To: htaft\"). The major advantages and disadvantages\nof each approach are:\n\n - One mail to everyone:\n - This violates policy controls. The body of the mail is generated without\n respect for object policies.\n - Recipients can see To/Cc at a glance.\n - If you use mailing lists, you won't get duplicate mail if you're\n a normal recipient and also Cc'd on a mailing list.\n - Getting threading to work properly is harder, and probably requires\n making mail less useful by turning off options.\n - Sometimes people will \"Reply All\", which can send mail to too many\n recipients. Phabricator will try not to send mail to users who already\n received a similar message, but can not prevent all stray email arising\n from \"Reply All\".\n - Not supported with a private reply-to address.\n - Mail messages are sent in the server default translation.\n - Mail that must be delivered over secure channels will leak the recipient\n list in the \"To\" and \"Cc\" headers.\n - One mail to each user:\n - Policy controls work correctly and are enforced per-user.\n - Recipients need to look in the mail body to see To/Cc.\n - If you use mailing lists, recipients may sometimes get duplicate\n mail.\n - Getting threading to work properly is easier, and threading settings\n can be customzied by each user.\n - \"Reply All\" will never send extra mail to other users involved in the\n thread.\n - Required if private reply-to addresses are configured.\n - Mail messages are sent in the language of user preference.\n": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 49
}
],
"types": []
},
"When a revision is updated, Phabricator attempts to bring inline comments on the older version forward to the new changes. You can disable this behavior if you prefer comments stay anchored in one place.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorOlderInlinesSetting.php",
"line": 25
}
],
"types": []
},
"When a user takes an action which generates an email notification (like\ncommenting on a Differential revision), Phabricator can either send that mail\n\"From\" the user's email address (like \"alincoln@logcabin.com\") or \"From\" the\n'%s' address.\n\nThe user experience is generally better if Phabricator uses the user's real\naddress as the \"From\" since the messages are easier to organize when they appear\nin mail clients, but this will only work if the server is authorized to send\nemail on behalf of the \"From\" domain. Practically, this means:\n\n - If you are doing an install for Example Corp and all the users will have\n corporate @corp.example.com addresses and any hosts Phabricator is running\n on are authorized to send email from corp.example.com, you can enable this\n to make the user experience a little better.\n - If you are doing an install for an open source project and your users will\n be registering via Facebook and using personal email addresses, you probably\n should not enable this or all of your outgoing email might vanish into SFP\n blackholes.\n - If your install is anything else, you're safer leaving this off, at least\n initially, since the risk in turning it on is that your outgoing mail will\n never arrive.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 23
}
],
"types": [
null
]
},
"When a user types their LDAP username and password into Phabricator, Phabricator can either bind to LDAP with those credentials directly (which is simpler, but not as powerful) or bind to LDAP with anonymous credentials, then search for record matching the supplied credentials (which is more complicated, but more powerful).\n\nFor many installs, direct binding is sufficient. However, you may want to search first if:\n\n - You want users to be able to log in with either their username or their email address.\n - The login/username is not part of the distinguished name in your LDAP records.\n - You want to restrict logins to a subset of users (like only those in certain departments).\n - Your LDAP server is configured in some other way that prevents direct binding from working correctly.\n\n**To bind directly**, enter the LDAP attribute corresponding to the login name into the **Search Attributes** box below. Often, this is something like `sn` or `uid`. This is the simplest configuration, but will only work if the username is part of the distinguished name, and won't let you apply complex restrictions to logins.\n\n lang=text,name=Simple Direct Binding\n sn\n\n**To search first**, provide an anonymous username and password below (or check the **Always Search** checkbox), then enter one or more search queries into this field, one per line. After binding, these queries will be used to identify the record associated with the login name the user typed.\n\nSearches will be tried in order until a matching record is found. Each query can be a simple attribute name (like `sn` or `mail`), which will search for a matching record, or it can be a complex query that uses the string `${login}` to represent the login name.\n\nA common simple configuration is just an attribute name, like `sn`, which will work the same way direct binding works:\n\n lang=text,name=Simple Example\n sn\n\nA slightly more complex configuration might let the user log in with either their login name or email address:\n\n lang=text,name=Match Several Attributes\n mail\n sn\n\nIf your LDAP directory is more complex, or you want to perform sophisticated filtering, you can use more complex queries. Depending on your directory structure, this example might allow users to log in with either their email address or username, but only if they're in specific departments:\n\n lang=text,name=Complex Example\n (&(mail=${login})(|(departmentNumber=1)(departmentNumber=2)))\n (&(sn=${login})(|(departmentNumber=1)(departmentNumber=2)))\n\nAll of the attribute names used here are just examples: your LDAP server may use different attribute names.": {
"uses": [
{
"file": "/applications/auth/provider/PhabricatorLDAPAuthProvider.php",
"line": 315
}
],
"types": []
},
"When an object (like a task) is edited, Phabricator creates a \"transaction\"\nand applies it. This list of transactions on each object is the basis for\nessentially all edits and comments in Phabricator. Reviewing the transaction\nrecord allows you to see who edited an object, when, and how their edit changed\nthings.\n\nOne common reason to call this method is that you're implmenting a webhook and\njust received a notification that an object has changed. See the Webhooks\ndocumentation for more detailed discussion of this use case.\n\nOne Object Type at a Time\n=========================\n\nThis API method can query transactions for any type of object which supports\ntransactions, but only one type of object can be queried per call. For example:\nyou can retrieve transactions affecting Tasks, or you can retrieve transactions\naffecting Revisions, but a single call can not retrieve both.\n\nThis is a technical limitation arising because (among other reasons) there is\nno global ordering on transactions.\n\nTo find transactions for a specific object (like a particular task), pass the\nobject PHID or an appropriate object identifier (like `T123`) as an\n`objectIdentifier`.\n\nTo find all transactions for an object type, pass the object type constant as\nan `objectType`. For example, the correct identifier for tasks is `TASK`. (You\ncan quickly find an unknown type constant by looking at the PHID of an object\nof that type.)\n\nConstraints\n===========\n\nThese constraints are supported:\n\n - `phids` //Optional list<phid>.// Find specific transactions by PHID. This\n is most likely to be useful if you're responding to a webhook notification\n and want to inspect only the related events.\n - `authorPHIDs` //Optional list<phid>.// Find transactions with particular\n authors.\n\nTransaction Format\n==================\n\nEach transaction has custom data describing what the transaction did. The\nformat varies from transaction to transaction. The easiest way to figure out\nexactly what a particular transaction looks like is to make the associated kind\nof edit to a test object, then query that object.\n\nNot all transactions have data: by default, transactions have a `null` \"type\"\nand no additional data. This API does not expose raw transaction data because\nsome of it is internal, oddly named, misspelled, confusing, not useful, or\ncould create security or policy problems to expose directly.\n\nNew transactions are exposed (with correctly spelled, comprehensible types and\nuseful, reasonable fields) as we become aware of use cases for them.\n": {
"uses": [
{
"file": "/applications/transactions/conduit/TransactionSearchConduitAPIMethod.php",
"line": 17
}
],
"types": []
},
"When creating objects in the web interface, you can use HTTP parameters to\nprefill fields in the form. This allows you to quickly create a link to a\nform with some of the fields already filled in with default values.\n\nTo prefill a form, start by finding the URI for the form you want to prefill.\nDo this by navigating to the relevant application, clicking the \"Create\" button\nfor the type of object you want to create, and then copying the URI out of your\nbrowser's address bar. It will usually look something like this:\n\n```\n%s\n```\n\nHowever, `your.install.com` will be the domain where your copy of Phabricator\nis installed, and `application/` will be the URI for an application. Some\napplications have multiple forms for creating objects or URIs that look a little\ndifferent than this example, so the URI may not look exactly like this.\n\nTo prefill the form, add properly encoded HTTP parameters to the URI. You\nshould end up with something like this:\n\n```\n%s?title=Platyplus&body=Ornithopter\n```\n\nIf the form has `title` and `body` fields of the correct types, visiting this\nlink will prefill those fields with the values \"Platypus\" and \"Ornithopter\"\nrespectively.\n\nThe rest of this document shows which parameters you can add to this form and\nhow to format them.\n\n\nSupported Fields\n----------------\n\nThis form supports these fields:\n": {
"uses": [
{
"file": "/applications/transactions/view/PhabricatorApplicationEditHTTPParameterHelpView.php",
"line": 56
}
],
"types": [
null,
null
]
},
"When email is sent, what format should Phabricator use for user's email\naddresses? Valid values are:\n\n - `short`: 'gwashington <gwashington@example.com>'\n - `real`: 'George Washington <gwashington@example.com>'\n - `full`: 'gwashington (George Washington) <gwashington@example.com>'\n\nThe default is `full`.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorMetaMTAConfigOptions.php",
"line": 170
}
],
"types": []
},
"When this diff was generated, it was not pushed to staging for an unknown reason (the status code was \"%s\"). Changes must be pushed to staging before they can be landed from the web. The server may be running an out-of-date version of Phabricator, and updating may provide more information about this error.": {
"uses": [
{
"file": "/applications/drydock/operation/DrydockLandRepositoryOperation.php",
"line": 432
}
],
"types": [
null
]
},
"When this diff was generated, the server was running an older version of Phabricator which did not support staging areas for this version control system, so the change was not pushed to staging. Changes must be pushed to staging before they can be landed from the web.": {
"uses": [
{
"file": "/applications/drydock/operation/DrydockLandRepositoryOperation.php",
"line": 402
}
],
"types": []
},
"When this diff was generated, the server was running an older version of Phabricator which did not support staging areas, so the change was not pushed to staging. Changes must be pushed to staging before they can be landed from the web.": {
"uses": [
{
"file": "/applications/drydock/operation/DrydockLandRepositoryOperation.php",
"line": 393
}
],
"types": []
},
"When users write comments which have URIs, they will be automatically turned into clickable links if the URI protocol appears in this set.\n\nThis set of allowed protocols is primarily intended to prevent security issues with \"javascript:\" and other potentially dangerous URI handlers.\n\nThis set is also used to enforce valid redirect URIs. Phabricator will refuse to issue a HTTP \"Location\" redirect to a URI with a protocol not on this set.\n\nUsually, \"http\" and \"https\" should be present in this set. If you remove one or both protocols, some Phabricator features which rely on links or redirects may not work.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorSecurityConfigOptions.php",
"line": 171
}
],
"types": []
},
"When you upload a file via drag-and-drop or the API, chunks must be buffered into memory before being written to permanent storage. Phabricator needs memory available to store these chunks while they are uploaded, but PHP is currently configured to severely limit the available memory.\n\nPHP processes currently have very little free memory available (%s). To work well, processes should have at least %s.\n\n(Note that the application itself must also fit in available memory, so not all of the memory under the memory limit is available for running workloads.)\n\nThe easiest way to resolve this issue is to set %s to %s in your PHP configuration, to disable the memory limit. There is usually little or no value to using this option to limit Phabricator process memory.\n\nYou can also increase the limit or ignore this issue and accept that you may encounter problems uploading large files and processing large requests.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorStorageSetupCheck.php",
"line": 84
}
],
"types": [
null,
null,
null,
null
]
},
"Without '%s', Phabricator can not test for the availability of other binaries.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBinariesSetupCheck.php",
"line": 18
}
],
"types": [
null
]
},
"Without '%s', Phabricator will not be able to generate or render diffs in multiple applications.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorBinariesSetupCheck.php",
"line": 30
}
],
"types": [
null
]
},
"You are creating a new Phabricator account linked to an existing external account from outside Phabricator.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthRegisterController.php",
"line": 160
}
],
"types": []
},
"You are running PHP version %s. Phabricator does not support PHP versions between 7.0 and 7.1.\n\nPHP removed signal handling features that Phabricator requires in PHP 7.0, and did not restore them until PHP 7.1.\n\nUpgrade to PHP 7.1 or newer (recommended) or downgrade to an older version of PHP 5 (discouraged).": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPPreflightSetupCheck.php",
"line": 18
}
],
"types": [
null
]
},
"You are trying to run a daemon as a nonstandard user, and `%s` was not able to `%s` to the correct user. \nPhabricator is configured to run daemons as \"%s\", but the current user is \"%s\". \nUse `%s` to run as a different user, pass `%s` to ignore this warning, or edit `%s` to change the configuration.": {
"uses": [
{
"file": "/applications/daemon/management/PhabricatorDaemonManagementWorkflow.php",
"line": 94
}
],
"types": [
null,
null,
null,
null,
null,
null,
null
]
},
"You are trying to save some data to Phabricator, but the request your browser made included an incorrect token. Reload the page and try again. You may need to clear your cookies.": {
"uses": [
{
"file": "/aphront/AphrontRequest.php",
"line": 357
}
],
"types": []
},
"You can also upload files by dragging and dropping them from your desktop onto this page or the Phabricator home page.": {
"uses": [
{
"file": "/applications/files/controller/PhabricatorFileUploadController.php",
"line": 48
}
],
"types": []
},
"You can link your Phabricator account to an external account to allow you to log in more easily in the future. To continue, choose an account to link below. If you prefer not to link your account, you can skip this step.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthSetExternalController.php",
"line": 45
}
],
"types": []
},
"You can not add JIRA issues (%s) to this revision because your Phabricator account is not linked to a JIRA account.": {
"uses": [
{
"file": "/applications/differential/customfield/DifferentialJIRAIssuesField.php",
"line": 168
}
],
"types": [
null
]
},
"You can not set a credential for builtin URIs which Phabricator hosts and serves. Phabricator does not fetch from these URIs or push to these URIs, and does not need credentials to authenticate any activity against them.": {
"uses": [
{
"file": "/applications/diffusion/controller/DiffusionRepositoryURICredentialController.php",
"line": 41
}
],
"types": []
},
"You can not unlink this account because the administrator has configured Phabricator to make links to \"%s\" accounts permanent.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthUnlinkController.php",
"line": 88
}
],
"types": [
null
]
},
"You can opt to receive plain text email from Phabricator instead of HTML email. Plain text email works better with some clients.": {
"uses": [
{
"file": "/applications/settings/setting/PhabricatorEmailFormatSetting.php",
"line": 25
}
],
"types": []
},
"You can rebuild repository identities while Phabricator is running.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorManualActivitySetupCheck.php",
"line": 107
}
],
"types": []
},
"You can rebuild the search index while Phabricator is running.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorManualActivitySetupCheck.php",
"line": 45
}
],
"types": []
},
"You can respond to various application events by installing listeners, which will receive callbacks when interesting things occur. Specify a list of classes which extend PhabricatorEventListener here.": {
"uses": [
{
"file": "/applications/config/option/PhabricatorExtendingPhabricatorConfigOptions.php",
"line": 34
}
],
"types": []
},
"You can use this link to reset your Phabricator password:\n\n %s\n": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleEmailLoginMailEngine.php",
"line": 75
}
],
"types": [
null
]
},
"You can use this login link to regain access to your Phabricator account:\n\n %s\n": {
"uses": [
{
"file": "/applications/people/mail/PhabricatorPeopleEmailLoginMailEngine.php",
"line": 93
}
],
"types": [
null
]
},
"You have '%s' enabled in your PHP configuration, but Phabricator will not run in safe mode. Safe mode has been deprecated in PHP 5.3 and removed in PHP 5.4.\n\nDisable safe mode to continue.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPPreflightSetupCheck.php",
"line": 42
}
],
"types": [
null
]
},
"You have '%s' enabled in your PHP configuration.\n\nThis option is not compatible with Phabricator. Disable '%s' in your PHP configuration to continue.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPPreflightSetupCheck.php",
"line": 110
}
],
"types": [
null,
null
]
},
"You have '%s' enabled in your PHP configuration.\n\nThis option is not compatible with Phabricator. Remove '%s' from your configuration to continue.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorPHPPreflightSetupCheck.php",
"line": 91
}
],
"types": [
null,
null
]
},
"You have an old version of MySQL (older than 5.5) which does not support the utf8mb4 character set. We strongly recommend upgrading to 5.5 or newer.\n\nIf you apply adjustments now and later update MySQL to 5.5 or newer, you'll need to apply adjustments again (and they will take a long time).\n\nYou can exit this workflow, update MySQL now, and then run this workflow again. This is recommended, but may cause a lot of downtime right now.\n\nYou can exit this workflow, continue using Phabricator without applying adjustments, update MySQL at a later date, and then run this workflow again. This is also a good approach, and will let you delay downtime until later.\n\nYou can proceed with this workflow, and then optionally update MySQL at a later date. After you do, you'll need to apply adjustments again.\n\nFor more information, see \"Managing Storage Adjustments\" in the documentation.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 183
}
],
"types": []
},
"You have not verified the email address for your account (\"%s\"). You must verify your email address before you can interact with Phabricator over email.": {
"uses": [
{
"file": "/applications/metamta/storage/PhabricatorMetaMTAReceivedMail.php",
"line": 578
}
],
"types": [
null
]
},
"You have surplus schemata (extra tables or columns which Phabricator does not expect). For information on resolving these issues, see the \"Surplus Schemata\" section in the \"Managing Storage Adjustments\" article in the documentation.": {
"uses": [
{
"file": "/infrastructure/storage/management/workflow/PhabricatorStorageManagementWorkflow.php",
"line": 829
}
],
"types": []
},
"You haven't configured mailers yet, so Phabricator won't be able to send outbound mail or receive inbound mail. See the configuration setting cluster.mailers for details.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorMailSetupCheck.php",
"line": 15
}
],
"types": []
},
"You must start the Phabricator daemons to send email, rebuild search indexes, and do other background processing.": {
"uses": [
{
"file": "/applications/config/check/PhabricatorDaemonsSetupCheck.php",
"line": 29
}
],
"types": []
},
"You must verify your email address to log in. You should have a new email message from Phabricator with verification instructions in your inbox (%s).": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorMustVerifyEmailController.php",
"line": 36
}
],
"types": [
null
]
},
"You will no longer be able to use your %s account to log in to Phabricator.": {
"uses": [
{
"file": "/applications/auth/controller/PhabricatorAuthUnlinkController.php",
"line": 125
}
],
"types": [
null
]
},
"Your '%s' client version is '%d', which is newer than the server version, '%d'. Upgrade your Phabricator install.": {
"uses": [
{
"file": "/applications/conduit/method/ConduitConnectConduitAPIMethod.php",
"line": 82
}
],
"types": [
null,
null,
null
]
},
"Your Phabricator account (%s) has been approved by %s. You can login here:": {
"uses": [
{
"file": "/applications/people/xaction/PhabricatorUserApproveTransaction.php",
"line": 31
}
],
"types": [
null,
null
]
},