To actually add a remarkup rule, the basics are simple:

Unicode has a page of heiroglyphs but they don't seem to be supported yet on OSX.

Pretty sure it was copy pasted from something else at the time; I don't believe I would have actually picked a glyph.

To fix:

To fix this:

On the cache:

In this case, use the AphrontWriteGuard::beginScopedUnguardedWrites() method to surround the block -- you can grep for usage, but it will look like this:

I've got the endpoint and controller set up, but I get the following error when I call PhabricatorFile::newFromFileDownload:

Alright I've been able to narrow this down a little bit more. There's some error with how external/pear-figlet/Text/Figlet.php is smushing characters. Specifically lines 339-362 as well as the _rep($r) function. The equivalent function in the C code is here. I haven't been able to find an obvious discrepancy, but I suspect there's a subtle difference in how one of the regex functions is handling things or an error in one of the regexes themselves. This error also occurs with backticks and double-quotes:

D16465 has details on how to move forward here if anyone wants to steal it before @michaeljs1990 gets back to it.

This stuff is defined in PhabricatorUser->loadEditorLink(), which ain't great but probably not worth generalizing.

You're right! That probably makes is more feature request, less bug report. (extremely low priority FR)

I don't think this is preview related -- I think PhabricatorEditEngineConfigurationTransaction just doesn't implement hasChangeDetails() and some related methods to generate this link.

The goal is to provide an easy way for us to print messages like this:

In PhabricatorApplicationDatasource, do a PhabricatorApplication::isClassInstalledForViewer(...) test on each application and skip it if it is not installed. You can get the class name with get_class($application_object).

• Try to come up with a way that - can do something dangerous when injected into a CSS rule.
  • See D7274#47131 for a template of how to attack this.
  • If you can come up with any attacks, don't implement this.
• Adjust the regular expression in PhabricatorMonospacedFontSetting::filterMonospacedCSSRule() to include -.
• Adjust the error text in PhabricatorMonospacedFontSetting->validateTransactionValue() to say "..., hyphens, ..." or similar.

Found some shorter repro steps:

Ahh okay. I understand now. That did indeed happen automatically.

If you give a Phurl an "Alias", you can type ((thatalias)) in Remarkup to reference it. For example:

Also the ((alias)) syntax should use the most-preferred URI, although I think that will happen automatically.

That should really have been in a day 1 "spend 10 minutes doing this stuff first" document, I started collecting this stuff in T11561.

Also, are prototype applications enabled (phabricator.show-prototypes)? If not, Phurl won't actually be installed.

Alternate/simpler test is "does /phurl/ work".

Also, are prototype applications enabled (phabricator.show-prototypes)? If not, Phurl won't actually be installed.

Ah, okay. I'm not immediately sure, then -- did you restart Apache / is /config/edit/phurl.short-uri/ picking up the change?

I suppose we could link to /config/module/site/, which has a list of all Sites, but it's probably not intuitively obvious from there what's going on. It's also possible in some future world to reach this screen without running Phabricator at all (T1806), although probably unlikely.

Oh I left out the fact that I had already configured phurl.short-uri but still get the "Site Not Found" message.

First screen is good.

Just want to sanity check this before I continue. I set the ServerAlias and started getting this page when visiting short.url.com:

Ah, yeah. If you're using Apache with <VirtualHost /> directives, try something like this?

I'm unable to get URL shortening to work locally. Is there some apache configuration required to get it working?

I think you should already be able to add subscribers and projects (and take some other actions) with Herald, by writing a "Global" rule using the "Receiving email address" condition. Here's an example:

Oh! var_dump(...) or print_r(...) should send stuff to a big pink header on the page.

print_r($variable);
look at web page.

@epriestley PHP noob question: what do you do for debugging? I'm having a hard time just looking at the values of the variables involved here:

$pins = $request->getStrList('pin');
$pin = head($pins);
$app = id(new PhabricatorApplicationQuery())
  ->setViewer($viewer)
  ->withPHIDs(array($phid))
  ->executeOne();
if ($app) {
  $pin = get_class($app);
}

Ah, right -- I think those are both expected and that you're on the right track. You should be able to use $request->getStrList(...) instead of $request->getStr(...) to read the list, then head() to grab the first (item if it exists).

Alright I'm making a bit of progress here. Posting this update on the chance that there's something obvious I'm missing. The AphrontFormTokenizerControl behaves a little bit differently than the AphrontFormSelectControl. Specifically, this is what the form post data looks like the old way (SelectControl):

I was ultimately able to reproduce this, but it took some work and the instructions above definitely weren't sufficeient:

Alright, let me see if I can get anywhere with this.

I've tried a whole bunch of different post requests (after setting those config values and restarting apache) but I haven't been able to get that garbage yet.