We are using OJS 3.0.2.
I am currently testing Notification mailing list features.
I would like to discuss about a few aspects.
1) Access to Notification mailing list page with the back-end view
When you are not logged in, you access to a page which permits you to register your email to subscribe to Notification mailing list: notification/subscribeMailList
This page is with a back-end view. When you are not a registered user of the journal but just a visitor which wants to subscribe to the Notification mailing list, it could be a bit confusing. It would be more logical to access to this page with the front-end view.
So in my opinion, I think “templates/notification/maillist.tpl” template should include “frontend/components/header.tpl” and “frontend/components/footer.tpl” templates instead of “common/header.tpl” and “common/footer.tpl” templates.
And for notification index page (referenced by “templates/notification/index.tpl” template), I don’t see the value to permit to show it when you are not logged in and to have a back-end view with no valuable informations. It’s just my opinion. It could be interesting for other people.
2) Captcha on notification mailing list registration
The Captcha on notification mailing list registration is no longer displayed. Besides, there is no more “captcha_on_mailinglist” variable in the “config.inc.php” file.
Is it a choice or it’s because it has not been implemented yet ?
3) unsubscribeMaillist URL
When you enter your email address to receive notifications, you receive an email with 2 URLs, 1 with a confirmMailListSubscription link and 1 with a unsubscribeMaillist link.
But if you loose this email or delete it, you can’t unsubscribe anymore. It would be useful to have a section to enter the registered email to receive the mail again to be able to unsubscribe.
Maybe it could be the same section that for subscription and when you enter an email already registered in database, it will send you the email again with only the unsubscribeMaillist link.
4) Manage email registered in notification_mail_list table
The journal Manager can’t manage (view, add, delete) emails registered with Notification mailing list form which are stored in notification_mail_list table. Only a system administrator can do that by a direct access to database.
Is it planed to add an interface in the back-end to manage (view, add, delete) emails stored in notification_mail_list table ?
Thanks in advance for your answers.