I agree that we should have a single wiki page set as "Project Wiki Home" or the like, set from Projects (with appropriate edit permissions), not from Phriction. Then, if someone wants a page to be "associated" with a project, but not the homepage, they simply add it beneath that main page (or link to it on the main page). That should resolve any confusion about what it means to 'associate a page'.

Broken link for Customizing Forms documentation. Should be to https://secure.phabricator.com/book/phabricator/article/forms/

After using Phriction for a while with these changes, I only noticed one major UI problem - the hamburger menu does not display hierarchy. This is really difficult when one has a particularly long or detailed Phriction document with three or four levels of headers, and makes it almost useless in those situations. One cannot quickly find what they're looking for.

If it's the version currently visible on this Phabricator (since I have high contrast turned on), it looks good to me. Having the border helps me track, personally. The option to override color schemes (i.e. dark theme) accounts for black-on-white issues that many dyslexic users might have.

So, it's a Schroedinbug. What fun.

I've updated the ignore rules, and will let you know if this continues. So, I can assume then that arc diff --skip-binaries doesn't actually skip binaries unless Git is configured to ignore the same files? Seems strange, but....OK. *Shrug*

*Sigh* Again, I don't want the .a and .o files. I'll check the VCS settings again.

Let's put it this way - that's on a four-file (as I said, small) project. We have projects that will be running closer to 400 files within a matter of months. 10x that amount in your calculation = 365,000MB, or about 365 GB, per year.

@epriestley, to answer the first question, we're looking at an average of 1MB total per Diff update, on a small project. With 2-5 diffs per day, you can imagine that adds up fast over several months. It is something we can handle right now, but it will obviously become a problem before long.

For whatever reason, binaries are still being uploaded when I pass --skip-binaries. So, the problem remains. I specifically need to remove the binaries already uploaded from old Differentials.

Hi @epriestley, thanks for the fix and the advice. I've switched to stable. All is well now.

I originally made the task, and then I happened to find the code responsible. Which would you prefer? (Frankly, I'd wager that the task is less useful.)

When I attempt to view any branch in Diffusion since this landed, I get the error message.

Unhandled Exception ("InvalidArgumentException")
Argument 2 passed to phutil_implode_html() must be of the type array, string given, called in /home/hawksnest/phab/phabricator/src/infrastructure/diff/view/PHUIDiffTableOfContentsItemView.php on line 277 and defined

Now we also have errors on ALL of our Phabricator-hosted Git repositories when you try to view a branch.

We now have TWO Differentials doing this - one that was just posted did the same thing.

If it's helpful, there was an entire debate on Stack Overflow about whether downvotes were useful. My conclusion (FWIW) it that downvotes only serve as an anonymous "I dislike this because I'm a jerk" for a lot of people, as they don't actually bother to read the tooltip "Not Useful".

It might be worth mentioning that Wiggio.com has this exact feature. For them, the person doing the scheduling specifies the days and times that the meeting could start on, and then everyone checks the boxes for the timeslots that they are available. Like you mentioned, not the most innovative UI, but it is very effective.

@Aronnax, ah, okay, my mistake.

@Aronnax, you need to download a fresh copy of the Git repository yourself, and then look under applications/phrequent.

Aww, sad panda is sad.

Ha ha, I know how to defuse flame wars, but I try not to start them. :3

It just hit my server. Excellent final result, @chad and @epriestley! Very clean. Thanks again for taking my suggestions seriously - I have my server running on dark high contrast, and it is much easier to read than the early draft. Bravo!

Ahhhhhh, after D13363 I can track more easily again. Thanks @chad and @epriestley!

@chad The dark header solution would be very helpful. Given that features generally take months to roll out (just due to the nature of software, it's the same at my place), you can understand why I'm concerned about the promise of T8614 post-redesign.

@epriestley I understand prioritization. However, if that's the case, is there a way that I can NOT get the UI update on my end? I spend a lot of time on my Phabricator server, since I'm the lead developer, and my eyes are already tired from being here.

@epriestley Yes, I do have difficulty. I prefer interfaces that don't use that color scheme. Even with textbooks, I have to use a colored plastic sheet to deal with the glaring white and black, otherwise I can't process what I read. For example, my code editor...

@epriestley, @chad
EDIT: Yes, Chad, exactly.

@chad, Comparing the new UI to the old one, I see quite the opposite. I'm just asking for the white to be toned down to a subtle off-white so as to make it usable to users like myself. I am having a VERY hard time on here right now.

@chad, SIGNIFICANTLY opposed only to the massive use of pure white. See my large above comment.

@epriestley @chad

Nothing is hard to read and the text contrast is great.

I'm dyslexic, and I have to admit that the new layout can be a bit hard to use for me - it uses far more whitespace, much lighter grey, and less separators, so it is harder for me to track (read). Color settings would be nice, honestly, or at least make it a little less...white?

I'm still rusty on my PHP, but we might be able to work together and pull it off. I think it would be fantastic to get that on Phabricator so this task can be marked as done! We might just need to message each other on Conpherence if I get stuck on implementing your patch.

Hi @witrin, I just had an issue this week with someone who really needed to edit a time entry that got mangled. Would you mind reviewing your add/edit code given the latest codebase in Phrequent, and creating a new diff? Perhaps it'll get accepted, plus I can at least patch it in to my own copy. (I hope the rest of ya'll don't mind my saying that, but I'm pretty darned desperate for this.)

Ah, okay, well that explains that. I'm still getting my bearings around here, as my own workflows are muscle memory. Thank you!

(I'm near totally unfamiliar with Git. I always use SVN.) I ran arc land 'master' as instructed at the top, and it failed with

Ah, thanks for the clarification. I knew something wasn't right.

Added shebang to file, as requested...?

(Thanks @chad, I couldn't find this...)

At my company, we use Ponder very MUCH like Stack Overflow. When there are multiple answers, the voting is essential for determining which one is the "best answer" by group consensus. Removing the voting increases signal noise, and basically makes it like Phriction. If we simply wanted a single group-edited answer, we'd put it on Phriction in the first place.

Nevermind, Guido's Time Machine at work here. (My server updates Phabricator automatically every morning, but the fix hit somewhere after 8am PST.) Sorry!

It was a case of operator error in this situation in following workaround T2465: Context not available for revisions created on Windows by @raman.rathod. (The path has to be in double-quotes, and spaces were omitted in "Program Files (x86). Simple case of everybody knows, so nobody knows.

Actually, I have to agree with merging this into Fact, otherwise we wind up with duplicates of common code.

I appreciate that, but I know it isn't the server that is the problem, as the problem is isolated to Windows, and all the staff using Linux is sending diffs to the repositories without a problem. (It also worked in the past from Windows, and the only server changes have been Phabricator's updates.)

Default shell (cmd), though that shouldn't really make a difference, you're right.

Here is the requested output. I put <SERVER> in place of the actual domain name.

I put <SERVER> in place of the actual server URL, for security reasons. Again, she used to be able to send diffs just fine from Windows.

Yes, I had her run arc upgrade before her second attempt.

I'll ask my employee to do that on a test commit, and I'll let you know.

Hi @btrahan, seeing as I'm waist-deep in writing a game engine that can run on 256MB RAM, I have absolutely no need to hold this task in memory. Feel free to deallocate and reclaim, ha ha. (Can you tell what part of that game engine I'm writing?)

Waiting is fine by me. I will say, I currently have a "general chat" area for the entire staff, and that isn't linked to a project for obvious reasons.

(Ahh, thanks for the merge, @epriestley.)

Well, hey, I can claim this. No guarantee on WHEN I can get to it exactly (writing the lexer for our in-house language), but I'll put it on my list.

FWIW, I can confirm this as well. My team is having this issue too, though I'm attempting to make Ubuntu our official development platform, so hopefully I will resolve that BEFORE this is fixed.

Hm. How far out would you estimate v2 to be?

Hi @witrin, while I can't account for any of the above, I will say one thing in response to your last statement - transaction history is VERY important to managers, especially where keeping weekly time logs is concerned.

Well, Project-based Conpherences would certainly be wonderful, but I still say it would be a good idea to remove the pictures altogether until then. (I have a former staff member's face on 80% of the group chats by sheer coincidence.)

The other option, of course, is to do away with the chat image altogether, as it is rather confusing to have the face of ONE person on a group chat, especially if that person already left.

It isn't, so I'll patch this to my own and leave the rest alone. I appreciate the explanation, as mute "won't fix, don't fix" stances are rather disconcerting, as you might guess. Thanks.

As with T7243: Office Hours/Default "Available" or "Closed", I really need this, so I'll do it myself.