Incompatibility with new redesigned site

[GoogleCodeExporter]

As Facebook is pushing a new redesigned version of their site (http://
www.techcrunch.com/2010/01/04/facebook-rolling-out-redesign-to-some-users) 
this brakes the ability to use this protocol plugin.

The user has no option for using old design (AFAIK).

FB protocol v.0.0.0.7 build #535 "false detects" this new layout as 
Facebook lite. Older versions just got stuck in "connecting to...".

Current (FB plugin) debug log level does not provide any useful 
information.

Original issue reported on code.google.com by aksiom on 19 Jan 2010 at 9:33

[GoogleCodeExporter]

Unfortunately, none of my two accounts has this redesigned layout available so 
I 
cannot analyze and reparse it. Since it will be generally available, I'll have 
to 
recode it for everyone. Until then, I can't do anything about it, sorry for 
this :)

Original comment by n3weRm0re.ewer on 19 Jan 2010 at 12:53

• Changed state: CannotFix
• Added labels: Product-Facebook, Component-Logic
• Removed labels: Product-, Component-

[GoogleCodeExporter]

Issue 29 has been merged into this issue.

Original comment by n3weRm0re.ewer on 5 Feb 2010 at 8:21

[GoogleCodeExporter]

check the issue 28, there i posted a link and this links chat also works with 
new
version. So using this one everyone (old, new and lite users) can chat. I would 
try
on your place

Original comment by bug.me.not.dude@googlemail.com on 5 Feb 2010 at 9:41

[GoogleCodeExporter]

Issue 32 has been merged into this issue.

Original comment by n3weRm0re.ewer on 7 Feb 2010 at 10:49

[GoogleCodeExporter]

Today one of my accounts got the new redesigned theme, adaptation should be 
pretty 
fast as most data items are almost same/similar, but not same as before of 
course, 
that's why it doesn't work at this moment and the same reason the notice is 
displayed. 
On the other hand, due to really bad C-based JSON parser and whole processing 
complications I plan to do a deeper revision of the code flow, followed by move 
to a 
CAJUN JSON parser, which seems to be really fantastic :) To sum it all, I hope 
the 
result will be pretty as a heaven :]

Original comment by n3weRm0re.ewer on 7 Feb 2010 at 10:55

• Changed state: Started

[GoogleCodeExporter]

Original comment by n3weRm0re.ewer on 7 Feb 2010 at 11:09

• Added labels: Priority-High

[GoogleCodeExporter]

Should be fixed in 0.1.0.0, since this build both new and old designs should 
work.

Original comment by n3weRm0re.ewer on 8 Feb 2010 at 11:38

• Changed state: FixedNextVersion

[GoogleCodeExporter]

The alpha build 1.0.0.604 is installed.  It logs in ok, sends messages, but I 
cannot
receive messages via FB.  It may have interfered with send/receive on other
protocols, but I don't have sufficient testing to prove it.  

Original comment by douglask...@gmail.com on 9 Feb 2010 at 3:04

[GoogleCodeExporter]

Should be working fine in #607, sorry, my fault ^^

Original comment by n3weRm0re.ewer on 9 Feb 2010 at 8:02

[GoogleCodeExporter]

Issue 33 has been merged into this issue.

Original comment by n3weRm0re.ewer on 9 Feb 2010 at 8:03

[GoogleCodeExporter]

Testing alpha build 1.0.0.607:

1. upgrading from v.0.0.0.7 build #535 

2. Miranda restart -> login error -> "invalid password in database" (Miranda is 
set 
to login to every account on restart; password in DB is correct)

3. On manual connect -> plugin managed to connect -> loaded contact statuses -> 
Miranda crashed (msvcr80.dll)

4. Removing "ID" and "LogonTS" from DB -> no more "invalid password in 
database" on 
restart -> successful login -> after some time it would crash (msvcr80.dll) 

5. Disabled Debug Logging -> no crash -> after some time received Live Feed 
notifications (approx. the same time it would crash with Debug Logging ON)

6. It seems crashes are related to Debug Logging .. and a fact I jumped from 
#535 to 
#607 :)

----

So far, as Debug logging is disabled everything works fine.

Original comment by aksiom on 9 Feb 2010 at 10:37

[GoogleCodeExporter]

> n3weRm0re.ewer: Build #615 changelog -> Improved logging low-level process

Build #615 fixes Debug Logging crashes I mentioned above.

Though, it still returns error "Probably wrong password entered, please try 
again" 
on first login attempt (every time you start Miranda) which can be solved by 
removing old "ID" record in DB

Original comment by aksiom on 9 Feb 2010 at 12:38

[GoogleCodeExporter]

Issue 37 has been merged into this issue.

Original comment by n3weRm0re.ewer on 10 Feb 2010 at 10:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Issue 40 has been merged into this issue.

Original comment by n3weRm0re.ewer on 11 Feb 2010 at 12:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by n3weRm0re.ewer on 12 Feb 2010 at 9:42

• Changed state: Fixed