OK I just noticed this build plan as 2 duplicate steps (with the same 1.1 identifier)? That certainly shouldn't be the case. Did something get corrupted?

Unfortunately, no plans to pursue this. Mostly, it'd be inconsistent and surprising to most people to have one image format display one way and others display another way (and thus we'd bear that support and documentation cost). Settings isn't likely either, see T8227 for explanation.

This is correct. It is not an available filter for logged out users.

Yes, this should eliminate the need to sync/cron/do anything.

Would this eliminate most of the benefit from cron based "sync refs from the main repo" glue?

In case still interesting to OP:

I accidentally stumbled across the root cause for this and I think the fix is a one-liner, so it should work better after D15391.

The same problem occurred on my site with the latest Phabricator and the latest Mercurial 3.7.2 installed on both sides.

@chad does the Update clarify it? tnx in advance.

What are you trying to do, specifically? You can scale Phabricator in many ways.

Ok thanks. I found it very confusing.

https://www.w3.org/TR/capability-urls/ is relevant - Good Practices for Capability URLs.

(See also T6007). There should be a download button on lightboxed images as a workaround.

This is expected behavior, isn't it?

It's mainly the projects that I want to see as well. Although there has been talk of priorities etc. as well

In T10493#162973, @epriestley wrote:

It looks like the root problem in all of the downstream reports is that projects, specifically, are no longer readily available (although they previously weren't on emails deeper in the thread, either).

"implement Gmail in Phabricator"

asdasdasd

Well, sort of. Projects don't get set correctly with explicit column.

column should be a PHID.

Yeah, this was mostly-intentional while resolving T9527 / T7661.

T8153 possibly also related (detect someone broke the resource and destroy it so it gets recreated).

We don't have a secret internal Phabricator full of juicy status updates: if we make progress, we'll update this task. See Planning for details.

Any progress here? What about setting the hierachy limit in the wiki document itself? So you can say "show X levels in the document hierachy of this page" where X is inherited and has a default value of 2?

Thanks!

We already have this.

See Contributing Feature Requests.

Yeah, they're hard to separate -- available rules depend on configuration, installed/uninstalled applications, extensions, and version, and individual rule behaviors may depend on things like the presence of dependencies on the system (for example, whether cowsay works, and which cows are available).

In T10468#162641, @epriestley wrote:

which svn client do you use ?

If this depends on a particular client, you need to tell me that as part of your reproduction steps.

i saw you have the file on the same folder. can you try moving the files between differnt folders ?

That also works fine.

if it still working maybe we should upgrade phabricator.

Yes, we ask you to upgrade before reporting a bug. Many bug reports we receive have already been fixed. See Contributing Bug Reports.

which version of phabricator did you use ?

HEAD of master.

Can you oopen an instance at https://admin.phacility.com and do your testing here ?

I think using Aphlict, you have real time update on compherence ! (Maybe it is still work in progress for update, butyou will definitivly have a notification that a new message comes)

hehehhe