(please see the example issue report and if possible, provide Labels! :), too)
Thanks to all of you for your support :)
- Release build
- Includes proto icons from Addons
- REQUIRES Visual C/C++ 8 Runtime libraries installed
- There should be no special conflict when connected to Facebook via browser at the same time, but I recommend logging in with Miranda first, followed by the browser.
- I also RECOMMEND using Crash Dumper plug-in along with this plug-in, it should be pretty stable, but I would like to know when some error occurs. To make a good crash report, you must put all the files from the archive into your Plugins folder, otherwise the report will be missing data and thus useless! You should also provide the .mdmp file, as .txt one is often nothing-saying when conflict affects surrounding components.
- No major issue at this time, watch Issues on Tracker for more info
- Wall posts are not sent properly when you set them to often — server limit requires captcha confirmation when it considers you are "flooding"
- Being disconnected sometimes — server fault, mostly caused by server time-out side to side with restrictive connection politics
- Away status is not applicable — FB doesn't support any controllable Away status
For providing a help, you can use two options how to log what plugin does.
First option is to use a Crash Dumper plugin, which is helpful when crashes and similar invokes occur. Additional files included with the Facebook Protocol ZIP archive are required to make a good crash report. This is usually stored somewhere in the profile directory. Such crash event usually generates two files, TXT and MDMP, where the binary MDMP file is the more important one.
Second option which is usually helpful when some part of service stops working etc. is an active logging implemented in this plugin. You can enable such logging in Miranda Options on Facebook account dialog page. The resulting log is placed right in the Miranda directory side by side with miranda32.exe executable. Please use this logging only in a situation when you detect some repeating event which could be logged (f.e. disconnecting, login issues, etc.) for a short-time period to effectively catch only the relevant time period, thus providing a short, helpful log.