Users can't log in

[pedroparkero]

CONTENTS DELETED

The author has deleted this message.

[Verus Open Source Support]

Yes, we will check the problem locally. In the mean while please check their membership start and end dates

On 11/23/2011 07:48 AM, pedroparkero [via NewGenLib] wrote:

Hi! Our students can't log in to OPAC even after I changed the password for them. Does the OPAC accept a user ID with hyphens? Because I can access mine and other staff & faculty members' accounts where the username is only made of numbers or letters. Please help ASAP.

---

If you reply to this email, your message will be added to the discussion below:

http://newgenlib.2944635.n2.nabble.com/Users-can-t-log-in-tp7022957p7022957.html

To start a new topic under NewGenLib, email [hidden email]
To unsubscribe from NewGenLib, click here.
NAML

[pedroparkero]

Ooops. Someone messed up the years and made the end dates this year. Sorry for the trouble. Will delete this topic now...

[pedroparkero]

Oh. So it seems the threads here are undeleteable. Anyway, to avoid making the thread completely pointless, might as well give a suggestion:
If the membership is expired, I hope the error that comes out of the OPAC informs the user that his/her membership is expired, and not that it is an invalid username/password, because, as we have found out, it can be misconstrued by the user.

[Verus Open Source Support]

We recommend the same message to persist. Please comment


On 11/24/2011 08:01 AM, pedroparkero [via NewGenLib] wrote:

Oh. So it seems the threads here are undeleteable. Anyway, to avoid making the thread completely pointless, might as well give a suggestion:
If the membership is expired, I hope the error that comes out of the OPAC informs the user that his/her membership is expired, and not that it is an invalid username/password, because, as we have found out, it can be misconstrued by the user.

---

If you reply to this email, your message will be added to the discussion below:

http://newgenlib.2944635.n2.nabble.com/Users-can-t-log-in-tp7022957p7026852.html

To start a new topic under NewGenLib, email [hidden email]
To unsubscribe from NewGenLib, click here.
NAML

[pedroparkero]

But why would you recommend it persist? Wouldn't a more informative error message save people trouble in troubleshooting it? Separate errors for separate error events, not a one-size-fits-all message. For example, other good websites, when you input a username that isn't in their database, would not say the usual "invalid user/password" message but rather, will inform the user that the username does not exist and would give the option to the user to register instead with that name.  
Although I would understand your hesitation to change the error if it would be very hard and tricky to insert it into the source code. That's just my thoughts on the matter.

[Verus Open Source Support]

Thank you for your comments.
Our hesitation was not regarding the difficulty in changing the source code :)
Issue raised and will be addressed

On 11/24/2011 11:19 AM, pedroparkero [via NewGenLib] wrote:

But why would you recommend it persist? Wouldn't a more informative error message save people trouble in troubleshooting it? Separate errors for separate error events, not a one-size-fits-all message. For example, other good websites, when you input a username that isn't in their database, would not say the usual "invalid user/password" message but rather, will inform the user that the username does not exist and would give the option to the user to register instead with that name.  
Although I would understand your hesitation to change the error if it would be very hard and tricky to insert it into the source code. That's just my thoughts on the matter.

---

If you reply to this email, your message will be added to the discussion below:

http://newgenlib.2944635.n2.nabble.com/Users-can-t-log-in-tp7022957p7027150.html

To start a new topic under NewGenLib, email [hidden email]
To unsubscribe from NewGenLib, click here.
NAML

[pedroparkero]

That's great. Thank you. :-)