Loading...
 
Skip to main content

Custom Share Module 0.1dev

Features / Usability

Features / Usability


yet another login problem...

posts: 12

Sorry to bother you with these login problems, but I
found no documentation about this particular situation:

My website (www.scoutsaintquirin.be.tf) ask its users
to login. For most of them, it runs fine, but for a
few, they get the "invalid username and password" error
message in their browser (Internet Explorer). The
strange thing is that if I try to login myself with the
same username and password (with Galeon on my Linux
machine), it's OK !

Is this a bug in Tiki specific to Internet Explorer
users?

Note: I use the 1.7 release

posts: 29 United States

Most likely another user ๐Ÿ˜ฌ problem.
Typical things to look for:

  • is the CAPSLOCK key off
  • if using a laptop or notebook: is the NUMLOCK key off

If you fail, try & try again ๐Ÿ˜Š.
Cheers,
Dr Magu


posts: 12

Well, I wished it was that, but it isn't... I asked them to check everything (letters in uppercase, capslock,...), but the error stayed.

I'm currently upgrading my website to 1.7.7, maybe it will solve something.

posts: 2881 United Kingdom

> plison:
> Well, I wished it was that, but it isn't... I asked them to check everything (letters in uppercase, capslock,...), but the error stayed.
>
> I'm currently upgrading my website to 1.7.7, maybe it will solve something.

See Compression maybe?

Damian


posts: 2881 United Kingdom

> plison:
> Well, I wished it was that, but it isn't... I asked them to check everything (letters in uppercase, capslock,...), but the error stayed.
>
> I'm currently upgrading my website to 1.7.7, maybe it will solve something.

See Compression maybe?

Damian


posts: 12

๐Ÿ™ I took hours to upgrade the whole site, and the login for some users is still not working...

And no, it's not the compression.

Any other ideas ?


posts: 73

I had the same problem with my setup. I finally deleted their accounts and asked them to make a new one. I still think the problem was that they were putting in the wrong password somehow. Many times, they'll make a password and accidentally cap or make a typo. If they try it four or five times, sometimes they'll stumble on the right combination and get access.

This does make me wonder why tikiwiki dosen't allow admins to easily alter the passwords of users. This was an essential feature of phpbb that I used quite often, considering most of my users were students who were fairly new to computers. I can't really think of a good reason why the admin shouldn't be able to do this.

posts: 2881 United Kingdom

> blacklily8:

> This does make me wonder why tikiwiki dosen't allow admins to easily alter the passwords of users. This was an essential feature of phpbb that I used quite often, considering most of my users were students who were fairly new to computers. I can't really think of a good reason why the admin shouldn't be able to do this.

You can. See the FAQs for details on how. and its even easier to change in 1.9 tiki.

Damian


posts: 2881 United Kingdom

> blacklily8:

> This does make me wonder why tikiwiki dosen't allow admins to easily alter the passwords of users. This was an essential feature of phpbb that I used quite often, considering most of my users were students who were fairly new to computers. I can't really think of a good reason why the admin shouldn't be able to do this.

You can. See the FAQs for details on how. and its even easier to change in 1.9 tiki.

Damian



posts: 12

I think I found (at least part of ) the problem. Using extensively the mail function, I managed to see where this evil thing came from: I don't know why, but for some of my users, the SQL query "select email from users_users where binary login = $user" return nothing, even if the given $user IS indeed in the database (and I verified thousand of times that is was, with the very same spelling).

Why is it so? I have no idea. Maybe is it due to a specific coding system (iso-8859-15 instead of iso-8859-1, or utf-8) ? Me and my users are belgian, and the diversity of coding standards is often confusing.

So I simply deleted this part of the code, and it seems to go better.

Right now, the problem isn't entirely solved, but it should be in the next few hours (I still need to ask one of my unfortunate users to test the whole thing one last time).

Am I the only one to have been confronted to this type of bug ?


Upcoming Events

1)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4) 
Tiki birthday
5)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting