Using the Config application in Phabricator.
Nov 30 2019
Nov 26 2019
Nov 25 2019
Sep 3 2019
Aug 12 2019
Aug 11 2019
Aug 1 2019
Jun 23 2018
Jun 22 2018
Feb 15 2018
See PHI372 -- setting user.custom-field-definitions (or, probably, any similar config) to a string will pass validation but then fatal in use.
Feb 14 2018
Jan 31 2018
One attack is that you can override the content of email and then send invite or welcome mail that says whatever you want, whether the victim has a Phabricator account (welcome) or not (invite).
Aug 1 2017
Jul 31 2017
Jul 28 2017
This could also just go on the existing page at the bottom. We tell people to copy/paste it when submitting bug reports, but it's probably fine if they're including more information, especially since there is a nice walled garden moat around my personally having to deal with it.
See also PHI22.
Jul 9 2017
Jul 5 2017
One of our engineers is having a similar issue with slightly different error, running "arc install-certificate" would always fail with the following error:
Jun 27 2017
Apr 13 2017
Apr 12 2017
- PhabricatorSyntaxHighlightingConfigOptions defines this option.
- Change the type from wild to custom:SomeClassName to switch to a custom type validator.
- The new validator class should subclass PhabricatorConfigJSONOptionType.
- You can look at PhabricatorKeyringConfigOptionType for a (more complex) example of how to validate a value.
- Test by trying to change the value to something invalid, you should get an error.
- You can test a regexp is valid like this:
Apr 10 2017
Feb 6 2017
I think I'm just going to remove the "profile picture" text from the description to resolve this. The account.editable option is very old and I'd eventually like to remove it, but making the description more clear is an easier fix for now.
Jan 18 2017
Righty; I didn't want to create any extra noise. New ticket, ho.