[HyperKitty] #71: My Name at top right nav
by HyperKitty
#71: My Name at top right nav
------------------------+--------------------------
Reporter: langdon | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
I think the name at the top right should be either: 1) my first name (i
hate things showing my full name because it makes me paranoid) or 2) my
fedoraproject mail address. What I see is my redirect address from my FAS
profile which seems weird.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/71>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
9 years
[HyperKitty] #72: 500 error after timeout
by HyperKitty
#72: 500 error after timeout
--------------------+--------------------------
Reporter: langdon | Owner:
Type: defect | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
--------------------+--------------------------
I am guessing a bit here, but:
1) login to hyperkitty
2) wait a long time
3) go to your profile
4) make a change (the one I made was tz)
5) "update"
6) receive 500, but, oddly, information was still saved
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/72>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
9 years
[HyperKitty] #31: Admin interface
by HyperKitty
#31: Admin interface
------------------------+--------------------------
Reporter: abompard | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Add admin interface to do the following tasks:
* delete a post from the archives
* move a post between lists
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/31>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
9 years
[HyperKitty] #70: Not marking read
by HyperKitty
#70: Not marking read
--------------------+--------------------------
Reporter: langdon | Owner:
Type: defect | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
--------------------+--------------------------
I am not sure if this is a bug or a feature request (not being overly
familiar with the requirements). I would expect hyperkitty to be tracking
read/unread for (at least) threads to help me keep track of where I am.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/70>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
9 years
Integration with Postorius, etc
by Adam Clark
I'm trying to build a Mailman 3 front-end, integrating Postorius and HyperKitty into an existing Django system. I'm assuming from the docs and various components of HyperKitty (eg. the postorius_info context processor) that this is an anticipated use case, but it seems unnecessarily difficult.
I suppose the first question is whether this is wholly premature. I realize that all these components are still in beta, but on their own they seem relatively full-featured so it doesn't seem like a stretch to try to stitch them together, but perhaps there was some decision to punt all the integration to some later stage of development. (Or perhaps these really aren't meant to be integrated at all?)
Anyway, a few of the things I've run into:
- HyperKitty uses the top-level template directory (eg. it has a templates/base.html file), which is generally reserved for site-level templates.
- HyperKitty's base templates aren't broken up into blocks in such a way that they can easily be used to extend a different base template. The base template defines both the overall page structure and various HyperKitty components, so it's impossible to, say, modify the navigation bar without replicating a large chunk of HyperKitty stuff.
- Both HyperKitty and Postorius have independent user profile systems, but both are set up to use global user settings like LOGIN_URL. The result is that one or the other is generally invisible and unnavigable.
- Moreover, both apps use the same view names in places. For example, the HyperKitty user_profile page loads Ajax content from the "user_subscriptions" view, but Postorius defines its own "user_subscriptions" view that returns a full page. The result is that if the main urls.py includes Postorius URLs after HyperKitty URLs, the HyperKitty subscriptions tab tries to load the Postorius page via Ajax and fails.
- Postorius uses BrowserID authentication through social_auth, while HyperKitty includes a separate browser_id library
- Both connect to the Mailman API in the same way, but using different settings names (HyperKitty uses MAILMAN_REST_SERVER/MAILMAN_API_USER/MAILMAN_API_PASS, while Postorius uses MAILMAN_API_URL/MAILMAN_USER/MAILMAN_PASS).
I was hoping to get a sense of the big picture here before either filing a bunch of tickets or working on a pull request to try to address some of these.
Thanks
Adam
9 years, 8 months