Closed GoogleCodeExporter closed 9 years ago
I've also added it to my plugins folder and it doesn't show up in pidgin
plugins list after a restart?
What are we doing wrong?
Original comment by mjhillie...@googlemail.com
on 12 Feb 2013 at 5:30
I've also done the same steps as mentioned and have not been able to get it to
show up in the plugins list or the protocol list when adding a new account.
Original comment by Aak4shpa...@gmail.com
on 17 Feb 2013 at 1:56
[deleted comment]
Same problem as above. Solved by downloading libjson-glib-1.0.dll from
http://code.google.com/p/flist-pidgin/downloads/list and copying it into
C:\Program Files\Pidgin\
Then restart Pidgin and create a new account (with MightyText protocol).
Seems to work fine now...
Original comment by bobzo...@gmail.com
on 28 Feb 2013 at 10:28
Thanks for the tip Bob! Works great now! How did you figure that out..?
Original comment by jpcho...@gmail.com
on 28 Feb 2013 at 6:49
Is it possible to get clear directions on this?
I have the libmightytext.dll in my %appdata%\.purple\plugins folder and the
libjson-glib-1.0.dll file in C:\Program Files (x86)\Pidgin folder and I can't
get it to work.
Original comment by rtric...@gmail.com
on 8 Mar 2013 at 5:06
Yes that works great!!
Have you restarted pidgen and added a new MightyText account?
Original comment by mjhillie...@googlemail.com
on 11 Mar 2013 at 1:56
Is it possible to get a CLEAR definition of "doesn't work"?
Original comment by t...@joobleblob.co.uk
on 18 Mar 2013 at 3:27
You add the plugin into pidgins plugin folder and it doesn't show up in
protocol list when adding a new account.
It needs libjson-glib-1.0.dll in the pidgin folder to make it work.
Original comment by mjhillie...@googlemail.com
on 22 Mar 2013 at 9:57
Done all.. placed both dlls at the pidgin folder but still dont get the
mightytext account... maybe I am trying to find something is already there?
adding the protocol list i get when trying to add a new account.
Any help would be great...
Original comment by kramb...@gmail.com
on 11 Apr 2013 at 8:26
Attachments:
Same issue as kramb, any help would be appreciated. I'm running windows 7 64
bit if that makes a difference.
Original comment by unatc...@gmail.com
on 26 May 2013 at 7:27
In my case (win7 x64) :
- libmightytext.dll > C:\Program Files (x86)\Pidgin\plugins
- libjson-glib-1.0.dll > C:\Program Files (x86)\Pidgin\plugins
close/open Pidgin and it works !
Original comment by naiss...@gmail.com
on 30 May 2013 at 6:19
I copied the plugin (libmightytext.dll) to C:\Program Files
(x86)\Pidgin\plugins and saved libjson-glib-1.0.dll (found at
http://code.google.com/p/flist-pidgin/downloads/list) to C:\Program Files
(x86)\Pidgin\
Original comment by s...@stevewillows.com
on 30 Jun 2013 at 4:32
i can create an account but it is saying authentication failed when i try to
enable the account. i don't have any kind of proxy running which would
influence the connection.
Original comment by tyler.ho...@gmail.com
on 25 Jul 2013 at 6:12
[deleted comment]
I've updated the front page of the plugin website with some instructions on how
to install.
Original comment by eionrobb
on 1 Apr 2014 at 1:06
I am having the same problem as Tyler. Please advise on how to solve the
authentication problem, as mighty text is showing up in the selection list of
protocols. My phone is synced with mighty text and is set up to receive/send
from the mightytext website.
Original comment by tpool....@gmail.com
on 15 Dec 2014 at 5:39
>> tyler.ho...@gmail.com
>> tpool....@gmail.com
You need to modify your Google account.
https://encrypted.google.com/accounts/ManageAccount
You have two options.
1. Enable two-setp verification and create an app password:
https://support.google.com/accounts/answer/185833?hl=en
2. Modify your account to allow less secure apps:
https://support.google.com/accounts/answer/6010255?hl=en
Original comment by grunos...@gmail.com
on 22 Apr 2015 at 3:24
>> grunos...@gmail.com
I am still having the authentication problem. I have allowed less secure apps.
Do I have to Enable two-step verification as well?
Original comment by angoos...@gmail.com
on 29 May 2015 at 5:10
I have the same authentication problem (with all changes done) as mentioned
above
Original comment by jordanre...@gmail.com
on 15 Jul 2015 at 8:45
Original issue reported on code.google.com by
rogergra...@gmail.com
on 11 Feb 2013 at 8:59