Bug 22744 - https://ml.mageia.org is unusable
Summary: https://ml.mageia.org is unusable
Status: RESOLVED FIXED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Others (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-11 16:18 CET by Frédéric "LpSolit" Buclin
Modified: 2018-04-05 11:21 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frédéric "LpSolit" Buclin 2018-03-11 16:18:25 CET 
https://ml.mageia.org no longer permits to see ML archives, even when logged in. Moreover, the UI is completely broken.

Sorry if this was already discussed in a mailing list, but as the archives are no longer accessible...
Comment 1 Thomas Backlund 2018-03-11 17:54:18 CET 
ah, seems I uploaded wrong list config... will fix that tomorrow...

As for the UI, belive it or not, it's the default sympa UI as I have disabled our customizations as they need  to be rewritten for new sympa...

I'll see if I have time to fix that too tomorrow...

Assignee: sysadmin-bugs => tmb
CC: (none) => tmb

Comment 2 Frédéric "LpSolit" Buclin 2018-03-11 18:16:52 CET 
(In reply to Thomas Backlund from comment #1)
> As for the UI, belive it or not, it's the default sympa UI

It's so ugly. Is there no better alternative to sympa? Something more friendly?
Comment 3 Thomas Backlund 2018-03-11 18:24:03 CET 
Yeah, I'm not going to switch mailinglist software, however sympa is highly customizable, so one can make it look pretty much any way one wants...

There is also documentation about it, so it should not be that hard... I just need the time to actually do it :)
Comment 4 Thomas Backlund 2018-03-14 23:37:48 CET 
Archive access restored.

web interface look still TODO++
Comment 5 Frédéric "LpSolit" Buclin 2018-04-05 11:21:05 CEST 
The UI is much better with Sympa 6.2.30. Thanks!

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.