SWLE :: View topic

dimidola · Posted: Wed Oct 07, 2009 2:18 pm **Confirm Action.. NO**

OK, so I was about to kick someone rom the dynasty and then I thought I should check out something.. I pressed the No button for Confirm action but.... the user was banned by dimidola!!!

Alba · Posted: Wed Oct 07, 2009 3:10 pm **Re: Confirm Action.. NO**

Dannic2002 · Posted: Thu Oct 08, 2009 11:50 pm

I thought that when I clicked no Once, it kicked the member anyway.

I could have been mistaken as I was rushing though.

Dan

Jeanne · Posted: Fri Oct 09, 2009 3:25 am

It used to be when you clicked NO the member wasn't kicked (or pro/demoted if that was your action).

Zidane · Posted: Fri Nov 06, 2009 7:41 pm **A bug when removing members**

I found a bug - what else this is.

I remove members from my dynasty, click "remove", click "no" button when I am prompted for confirmation but the member is removed even that I clicked "no".

The first time I thought "so I clicked YES instead", but no, this is not the case. I tried it now and observed what will happen - the "no" button confirms - or not stops - the removal. The "yes" button is working correctly - confirming the removal.

idem32 · Posted: Tue Nov 10, 2009 7:59 am

The same thing happened to me,click in NO is YES to removed.

I also have the problem of H.A.T, or not counted, or tells me to back or tell me I failed, when actually I have done. :sad:

dimidola · Posted: Tue Nov 10, 2009 10:23 am

there's a post with tha same topic but it seems it hasn't been fixed yet... MODS??? help???

http://yarold.eu/phpBB2/v...p?p=46561#46561

DemonicJ · Posted: Tue Nov 10, 2009 1:12 pm

both threads merged.

This is one for Yarold to look into

Zidane · Posted: Sun Nov 15, 2009 11:42 pm

Seems OK now. I was as kampaku about to kick an inactive member, so I thought "I will click NO, what will happen?" and the member was NOT kicked, so the bug seems to be removed.

I am sorry to create new thread about a problem that I see there was a thread at the time I created mine - I think this is the case because of the "threads merged" thing, but the problem seems to be fixed at least and this is good :wink: