Thanks :)

@valerio.bozzolan Proposing to decline in favor of T15940: Update copy of external mimemailparser library / D25829: Update mimemailparser from May 2011 version to 8.0.4.
Let's not increase the diff to upstream (13 years difference) even more.

I'd prefer not to increase the diff to upstream (as a side effect of this very task) but instead to pull a more recent upstream version - see T15940.

(From Task description)

In diffusion repositories, Description and tags are hard to find or never shown (only show in Manage page).

In T15526#16806, @aklapper wrote:

Which exact page(s) is this ticket about?

Which exact page(s) is this ticket about?

Interesting. I see. Maybe expanding its controller that should be this one:

On it, thank you!

My friend, I think you are affected by this change, and this applies to whatever PHP version

I'm on the latest pull, commit f81e821abf2b275d1778d02a018a4d0af7208be8.
A bit off topic here :) but I'll quickly sum up the issue I'm having (and am in the middle of trying things to fix):

• Visiting https://[phorge instance]/auth/config/view/2/, where my Github auth item is, makes nginx dump a blank 502 page, no further info.
• First instinct is to check the /var/log/nginx/error.log, where I get a PHP stack trace concatenated into one line, and an nginx header length error (reformatted for readability. the PHP error is truncated):

Oh, totally possible that I forgot to update it :)

I'll take your word on it that it's supported, though the current installation guide says otherwise.
Further, I had a few roadbumps on a fresh install to a new server with PHP 8, that I suspect may relate to strlen(NULL) behavior, but I did need to set up PHP 7 to make sure that was or wasn't the case.
(I'm in the process of reproducing those and working out a possible cause or trace. Some manifested as warning banners, one as a 502 on my end in the GitHub auth provider.)

We already support PHP 8...

For others reading this thread: there's some discussion going on in the thread of the patch linked above, D25419.

Thanks Roberto, feel free to update D25420 to reflect your lovely screenshot.

Yeah, the dialog looks better then the extra notification...

I like so much this popup, thanks Roberto

In T15349#13341, @valerio.bozzolan wrote:

I don't know how to add a third button in a modal, but I would agree on that approach.

I don't know how to add a third button in a modal, but I would agree on that approach.

This might be a Good Starter Task, I think - you'll need to add a class for the config, and pull the config value in diffusion.

I think this is a Good Starter Task...

I think we are done with the logo as we have a graphical kit.

A friendlier UX might be to add a button/checkbox for "ignore this conflict".
This can be implemented in either the controller or in javascript, to act as if the user selected "ignore" in the drop-down).

It would be helpful to have reproducing steps here, but probably this was never reproduced by the reporter, just found from TranslateWiki

Phactory [will] also want an in-brand logo.