I also get the same erro this morning ! Does one comit change the way elasticsearch must be configured ?

Thanks, it works! But now any search results still show nothing.

You may be able to run this command:

What we can do, to have quick up our system back?

Presuming this is resolved because the new feature is a superset of the old feature.

Type r and then part of a repository name, like:

You can select the search scope you prefer from the dropdown to the left of the input, including a custom query. For example, here's how I have mine set up so that it always searches for open tasks:

The bug reporting guide suggests this as a "Common Fix":

Where is the documentation?

Well, I guess an old version of PHUIObjectItemView.php, to be precise.

Specifically, APC cached an old version of PhabricatorSearchResultView.php, and restarting cleared the cache.

Well, that was embarrassing. Thanks.

Restart Apache (if using apache) or fpm (if using nginx + php-fpm), and let me know if that fixes it?

Nope, sorry.

@epriestley -- curious if you have a rough ETA on this? Thanks!

I think that use case is quite different: spaces provides some very high level isolation between various groups of users. These uses cases relate to projects/tasks/etc. within the same space.

T3820 is the main task you'll want to follow. I don't think we'd be likely to pursue any of these until we understand if they're needed after Spaces.

There are a few problems or use cases that would be solved by this:

Please describe the problem you are having in Phabricator.

We can eventually add some sort of temporary preferences for logged-out users to make this sticky for them.

I think we should keep it around but make it work, there's no reason the options can't function for logged-out users.

When I type a project or user name, I expect the dropdown not to suggest things I already added.

I have half a diff for this, but project slug lookup is a gigantic mess right now.

I think it's reasonable for #x y to mean "documents matching query y in project #x", but I don't think x y should mean this on its own.

I've marked D12509 as fixing this, although it really just obsoletes it. Specifically: it removes this behavior (we no longer default to the first query) and makes scope selection explicit instead (if you want to default to a specific query, just select it from the dropdown).

I'm going to merge this into T4103, although D12509 partially obsoletes it. Hopefully, the explicit control surfaced in D12509 resolves the confusion here on its own.

Damn you and your psychic powers!

~~ psychic powers ~~

whoops

It did :/ thats random (would not have thought of that)

Restart apache or php-fpm and let me know if that fixes it?

I have this partially implemented but am shifting off this for a bit and probably won't get back to it for a couple of days:

At HEAD, you can use the new "Browse" dialog to browse through a long list of similarly-named items -- you can try it on this install by clicking the new icon inside the tokenizer control:

This is not really limited to custom fields: all "Order By" options could benefit from an ASC/DESC toggle...

Sounds like a plan, need any more UI?

I'd get rid of the "top query returned" behavior if we adopt this, to make things simpler. "All" would always mean "all", never "top query among saved queries".

Yeah, I'd make the app search be something like "Current Application" and it works like "All" if you're in a weird application like Settings or Auth or whatever.

Alrighty, how this direction? It's a little more clear what you're searching (text instead of icons) and Advanced Search has been moved out.

Amazon's:

@qgil had mentioned once that people didn't understand how to get to advanced search, so added a link here which just takes you there. I see your point though.

Yeah, I mean sticky. This feels a lot more useful to me if it's sticky, but I'm not sure how "advanced search" and "search all" are different if it's sticky.

If you mean 'sticky', I'd say wait and see if it's needed.

I don't want to change the current behavior, so typing text and hitting enter would do the same it does today. The dropdown is just if you want the text to perform a more advanced, non global, search.

Is this a modal dropdown which persists across pages, or do I type my query first and then select an action from the dropdown?

In this, "Search All" is always the default and top item, in any application or on home. "Phriction Only" would only surface when inside Phriction, or "Maniphest Only" when inside Maniphest, but always as the 2nd item and not selected by default. Advanced Search always appears.

Thanks!