Yeah sorry. That exception also occurred to me, before this change: https://we.phorge.it/transactions/detail/PHID-XACT-TASK-tuchgj42nb2ujtc/
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 12 2024
I could not even reproduce but get an informative error instead:
Thanks avivey. Added this:
Look into the "is creation xaction" - we had a similar diff recently about creating Revision from raw diff that had a similar behavior.
Mar 11 2024
Mar 4 2024
Mar 2 2024
Feb 23 2024
In T15719#15304, @Tgr wrote:Given how it's displayed on the Gmail UI, IMO unsubscribing from all emails or at least all emails of the given type (e.g. all Maniphest emails if it's a Maniphest notification) is the only thing that makes sense. If I mark an email as spam, and then use the unsubscribe option instead, I would not expect to continue getting identical email from all the other tasks.
No idea how (or if) other email clients handle the header, though.
Jan 24 2024
In T15719#15280, @avivey wrote:I'm left wondering when a "list-unsubscribe" header is appropriate - looks like anything that would need it will also need the one-click?
In T15719#15280, @avivey wrote:This suggests to me that there isn't a third category - everything is either promotional or transactional.
I'd argue that none of our emails are "marketing" or "promotional" (or "commercial"), even if it's hard to claim they are "transactional".
But as long as 98%[1] of the users agree that our mails aren't commercial, we don't need the one-click solution.
Do all messages require one-click unsubscribe?
No. One-click unsubscribe is required only for marketing and promotional messages. Transactional messages are excluded from this requirement. ...
In T15719#15272, @avivey wrote:
- Would adding List-Unsubscribe: https://we.phorge.it/settings/panel/emailpreferences/ header be enough to solve this?
Jan 23 2024
In T15719#15276, @Dzahn wrote:@phab1004:/srv/phab/phabricator/bin# ./mail volume Killed
In T15719#15272, @avivey wrote:using bin/mail volume, to see if they need to worry about this. It just collects all mails created in the last N days and counts them by user.
This is promising, from the Email sender guidelines FAQ:
Re: 1), the doc makes it sound like not, but I'm not entirely sure.
- Would adding List-Unsubscribe: https://we.phorge.it/settings/panel/emailpreferences/ header be enough to solve this?
Dec 31 2023
Dec 8 2023
there is a presentation from eric brechner, who was in microsofts xbox development, about kanban. he does it on whiteboard, extremely sinple:
https://www.youtube.com/watch?v=CD0y-aU1sXo
Nov 24 2023
Obviously, any fixes should be in ManiphestTransactionEditor and not spill into generic parent PhabricatorApplicationTransactionEditor.
Historical references: rP69eab4196de462e42b07b60e2b52071631f4a3c8 and rP4041a7e0f66406dbaa31faa3807d50833b7c7efd (which didn't help much).
Nov 22 2023
Nov 20 2023
Nov 14 2023
Oct 25 2023
Partially related to
Sep 4 2023
Here is the homepage feed after I created this task. Nothing indicates that there was a task creation, just a triage:
Aug 1 2023
clicking such a link w/javascript disabled will do nothing. Changing it to #123 and no JS will do something....
Implicitly, Phorge generally works fine for browsers where Javascript is completely disabled.
- Why these nice URLs are set in these links, if nobody visit them?
Less priority of course, since this Task I authored is super-stupid
OK I've done my best :D I admit it helped me psychologically.
If this is a feature request, then add all the things needed for a feature request - as in, "why would this feature be needed" and "what problem you're trying to solve".
Is this a bug or a feature request?
Why would it need to be a that?
Is this a bug or a feature request?
OK this was easy, but it really cannot be improved more than this in Legalpad or Phame. And this deserves a dedicated fix.
Increasing priority to normal since this feature is supposed to help to collaborate with others, but at the moment you only collaborate with yourself as default
Jul 31 2023
I'm quite sure we have to set PhabricatorApplicationTransaction.php::setIgnoreOnNoEffect(bool) somewhere but I don't know where ihih
Jun 28 2023
Jun 22 2023
Jun 20 2023
Jun 16 2023
Somehow "Normal" in 2023 I think - at least in Maniphest. But probably not so important.
Jun 15 2023
Jun 14 2023
Jun 13 2023
May 28 2023
Fixed thanks aklapper
@valerio.bozzolan F267558 in the task description is not attached, thus it cannot be seen by others.
May 9 2023
May 1 2023
It's unclear to me whenever Wikimedia needs this. If yes, feel free to also mark as Affects-Wikimedia. This is probably their use case: https://phabricator.wikimedia.org/T332639
Apr 30 2023
Apr 27 2023
Apr 25 2023
Apr 7 2023
Hi @Higgs are you still sure that this thing ever really worked?
Thank you!
The image is not attached.
In T15192#5962, @valerio.bozzolan wrote:Feel free to test that on my platform that always is up to date:
Feel free to test that on my platform that always is up to date:
In T15192#5960, @valerio.bozzolan wrote:What?
What?