Incorrect Parse of timeline messages

Hello Guys,

I recently migrated a running instance of statusnet from a test machine into one of our production webservers. The migration was executed without problems and after some minutes statusnet was up and running. However after the migration we noticed that all our statusnet desktop clients started to display all the messages in the timeline in the following format:

example #1:
Lorem i**um dolor *it amet, *on*e*tetur adi*i**ing elit. Prae*ent nulla ligula, ia*uli* vel bibendum *ed, gravida ut le*tu*. Mae*ena* at ma**a id ligula *orta tem*or vitae a* tortor. *urabitur nullam

example #2:
!<**an *la**="v*ard"><**an *la**="fn ni*kname">ng** Gente *or favor leer el *orreo, ini*iamo* el *ro*e*o *ara u*ar SVN *ara manejar el re*o*itorio

example #3:
@<**an *la**="v*ard"><**an *la**="fn ni*kname">max Ya el dmz *e a*tualizo...

As you can see the Desktop client is not parsing the messages correctly, but they all display perfectly in the website. I already checked all the language setting and charset encoding of the database and they seem to be fine (utf-8).

Any ideas of what is going on here? Again... on the website everything works fine, this issue only affect the timeline display in the desktop client, even the messages that I post from the desktop client...

Comments

  • @danmarte what versions of the client and server are you running?
    Were the clients using the test machine before you set it to production?
  • @jordanc Thanks for your response! Yes the Desktop clients were using the test machine as the Statusnet server... After we moved the data and database records to the new server we only switch our DNS records to point to the new server.
    The Mac client version is: StatusNet_Desktop-0.9.1
    And the server is: StatusNet 0.9.6 "Man on the Moon"
  • Try purging the cached data from the clients, there may be a conflict somewhere confusing things.
    • Linux: Run in the terminal $ rm ~/.titanium/appdata/net.status.desktop.client/statusnet.db
    • Windows: Delete statusnet.db from
      XP: C:\Documents and Settings\YOURUSERNAME\Application Data\Titanium\appdata\net.status.desktop.client\statusnet.db
      Vista/Win7: C:\Users\YOURUSERNAME\Application Data\Titanium\appdata\net.status.desktop.client\statusnet.db
    • Mac: Delete statusnet.db from ~/Library/Application Settings/Titanium/appdata\net.status.desktop.client\statusnet.db
  • @jordanc I read that tip on the website the other day, and I did it on my own mac but it didn't work...
  • @jordanc This doesn't seem to be an encoding problem... If you pay attention the client grabs the the message text from the rendered field in the notice table. But it looks like it is not parsing the message, instead it replaces random characters with stars...
    We have people connected to our statusnet server using gwibber and gravity, some others are using their mobile clients, and they haven't report any issues... This is only happening with the Statusnet Desktop client (in all platforms).
    Any ideas?
  • By the way, on Snow Leopard, the path to the statusnet.db is:

    ~/Library/Application\ Support/Titanium/appdata/net.status.desktop.client/statusnet.db
  • @danmarte and you did not have any problems with the desktop clients before the move?
  • No... it was working perfectly...
  • Uninstalling and manually removing the ~/Library/Application\ Support/Titanium didn't work :(
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google Sign In with OpenID