Does any command line argument work? For example: ./bin/config list should show you all config variables.

First of all thanks for your prompt replies.....i am running oracle enterprise linux with non root privileges. 64 bit.

Was Phabricator installed from our installation guide or another guide (or source) ? What system are you running (os/php)?

I have uploaded the screenshots

Sorry, we don't offer support for custom development. See Support Resources and Contributing Bug Reports for details.

This now reproduces in Chrome/iOS as of Chrome 48 (they now use WKWebView like Safari does).

Well it was mandatory.

This is almost certainly something that is only confusing to entirely new users who aren't yet familiar. I'm not surprised you're not confused if you've used phabricator for a non-trivial amount of time.

I've have several thousand or so diffs in Phabricator throughout the years, can't say I've ever mistaken something I planned changes to as landable.

That would be more clear. Even better would probably be to say what is is in fact *in*. Such as:

In the 1960s, the CIA spent over $20 million attempting to train cats to spy on the Kremlin.

In D15124#173386, @avivey wrote:

See D12198, T9785, and T10038.

In T8434#151667, @Krenair wrote:

I think one of the issues was people making a public task, and then deciding they should change it to security, but not having the permissions to do so?

See D12198, T9785, and T10038.

Yes it would. I might be more explicit and say which state it actually is in.

Would this phrasing be more clear?

See also T10229 for a similar Safari/Diff Render issue.

(I think we're happy with the feature-space here)

Maaaybe an issue with how we detect and decide to use the 1-up renderer? cc @epriestley

I think this is a duplicate of T9969. Basically between Safari 9.1 and 9.2 somewhere, it now reports a "diff" page to us as a desktop page, where if we normally detect being on a phone or tablet, we do not trigger tooltips, hovers, etc.

In T10229#155876, @chad wrote:

I can't say I have tried every button, but the same behaviour affects even buttons without tooltips.

Do you mind testing other buttons, by other buttons I mean any form anywhere on Phabricator that is not on the "diff" page.

I can't say I have tried every button, but the same behaviour affects even buttons without tooltips.

In T10229#155874, @aljungberg wrote:

I can't say I have tried every button, but the same behaviour affects even buttons without tooltips.

Is this report on all buttons in Phabricator or just ones that contain tooltips?

Please see Planning. We update tasks when new information is available, we don't have a secret shadow tracker with lots of juicy secrets that we aren't sharing.

Thank you for your help, it is working now.

Please copy and paste the exact commands you ran and the exact error.

Any update here? As far as I can tell it's also impossible to use any of the differential API endpoints using OAuth .

@chr86: Yes, I was able to solve this a while ago. If I remember correctly, I have just used the following instructions and, perhaps, restarted the server once or twice: https://secure.phabricator.com/book/phabricator/article/notifications. Hope this helps. I think I wrote down the solution steps, but couldn't find that document at the moment (maybe I didn't write anything down) - please let me know, if you are successful in that.

@ablekh : Were you able to solve this issue in the end? We're experiencing the same problem and are not using any proxy server.

Is it currently possible to configure number of levels to be displayed for wiki document hierarchy in Phriction? The current default seems to be equal to '2'. I have seen {D8061}, which is not resolved. Perhaps, I have missed other relevant info.

It's per object. So when you create an object, like a task, assign it to a space under Viewable By:

To manage who can seen an object, use the object's policy controls, Spaces (see Spaces User Guide) and Custom Forms (see User Guide: Customizing Forms).

Thanks for your great work too :)

Thanks for digging into this more @clippit.

There is no cache mechanism which would be cleared by adjusting configuration that is not also cleared by restarting the webserver and daemons, so it sounds like this was caused by evil spirits.

OK, dug in some more... I've eventually managed to get it sort of working. in src/future/http/HTTPSFuture.php, you have this code:

Sorry, I had locked the project field in the edit form for that user and it wasn't pulled through.

I can't reproduce this. https://secure.phabricator.com/T10224

You can also read up on T8434.

Objects do not inherit visibility rules by assigning Projects. You need to either set up Spaces or manually edit Policies on each task that you need to restrict visibility on,

Looking further, google auth works up until this URL is requested in my browser: https://phabricator.tvsquared.com/auth/login/google:google.com/?state=STATE&code=CODE