-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OJS] Users import/export plugin doesn't include notification functionality #2166
Comments
This is implemented in OJS 2.x in... It's not implemented in OJS 3.x here: https://github.com/pkp/pkp-lib/blob/ojs-stable-3_0_1/plugins/importexport/users/filter/UserXmlPKPUserFilter.inc.php#L132 The "notify" flag would need to be added to the UI somewhere, but otherwise it would be a relatively quick addition. |
Is it possible to get this assigned to a future release, especially if it is an easy fix? Have been talking to some folks who have been asking about it. |
Already implemented as part of #3462. |
Hello @asmecher, I seem to be running into this issue (or one like it) on a new installation of OJS 3.1.2-1 from the OJS downloads page. When I import a user using the XML below (but with a real email address), I get a message that says a notification was sent to the email address. However, no email is received. I am using Gmail SMTP to send emails, and no email is present in the email account's Sent box. The user is imported into OJS, and when I send a test email from the Users page, it is successfully delivered. Any ideas about why the import notification is not being sent?
|
@brueyd, the two most likely situations are
To determine which, I'd suggest adding
If you can confirm that Next time, it's probably better to post questions like this in the support forum -- https://forum.pkp.sfu.ca -- rather than on old/closed issues like this. |
It appears that the user notification functionality in the users import/export plugin hasn't been ported over. This is problematic, as users can be imported, but won't be notified of their username/password.
The text was updated successfully, but these errors were encountered: