Also adding some on-platform documentation would be nice.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Fri, May 31
Screenshot taken at 702 x 495
I guess I should abandon this patch?
Sorry again for the confusion, I don't want to create extra work. I will create another patch as clarification. Unfortunate legacy situation.
Yup. I noticed that probably the method getNewUserBody() should be just moved from PhabricatorDashboardPanelListController to PhabricatorDashboardPanelSearchEngine. Additional details in T15844.
The test plan should be:
Just try to move the method in PhabricatorDashboardPanelSearchEngine as-is
Wow, this was super-interesting
Thu, May 30
Nice!
restore newline
Thanks for the upstream link
Tue, May 28
Sat, May 25
Well, I understand why this patch completely removes that joke.
Sun, May 19
Thanks asd
Sat, May 18
shot at line 1162
Thanks :3 Hoping to be useful I will amend with a minimal sed -i 's/QRbitrtream/QRbitstream/' externals/phpqrcode/phpqrcode.php
I tested this with the following snippet:
Thanks :3 It makes sense, and I've also tested that snippet in PHP 5.5 and PHP 8.1 obtaining same results (premising that each() is not available anymore in PHP 8 as already clarified)
It was probably confused with the internal API executeRemovePath
Uh? It seems in use to me, in legacy lines 142, 145, 154, 155, etc.
Uh! I like this.
Probably OK now
Fri, May 17
Thu, May 16
Wed, May 15
Interesting triage. In legacy upstream this was a "feature request 🌈" - https://secure.phabricator.com/T12438
Super-useful comment:
I don't know if the file is really related, but PhabricatorDocumentRenderingEngine can be seen in scene while surfing a Diffusion repository and playing with View Options.
Relevant old upstream comment (from an unrelated task) that describes this problem as "ghosts in the UI":
Tue, May 14
adjust strings as suggested, also, renamed classes from "subscriber" to "subscribers"
Help welcome.
PhabricatorFileTransform: add null check
Thanks again. Generally super-useful.
Uhm. Incredibly, it seems to work. I have good feelings.
In D25636#17842, @aklapper wrote:Ideally this would be done via validateTransactions using ->setFormErrors($errors) on a PHUIObjectBoxView but all seems quite broken for badges anyway, see T15827.
Mon, May 13
Damn celerity. Thanks.
Damn celerity
Fri, May 10
(Premising that this is an answer to your question. Please move this as comment to your question.)
Nice but please smaller :D
Thanks! I was able to test visiting a profile image, and inspecting phlog() in the webserver log.
Thanks. I was able to test that the thing is just a string, not an object with a toString(), so no nuclear implosions
(If it does not work you may still need to call .toString() before doing this)
Thu, May 9
For some reasons I cannot cleanly apply the patch anymore.