Problem with site manager

[bucker]

I'm flashfxp registered user

I used flashfxp 3.0.2 bulid 1045,Win2k SP4

Problem:
Site manager can't saved the bookmarks of site.

For example:
open a flashfxp,sites-site manager,create a new site,at the new site's bookmarks option,new create a bookmark,and apply

new open a new flashfxp(but not close the first flashfxp),or open a new flashfxp after close the first flashfxp,the already saved bookmark of the site is not at there.

Please fix the bug at next version.Thanks!

I hope to become a Beta Tester.

[bigstar]

It seems to work fine here

[bucker]

please tell me your flashfxp's version and operation,Simplied Chinese?

I test the problem again.del the bookmarks.dat and bookmarks.dat.bak(backup first),the problem is solved.

but I doesn't understand the problem because...

[bigstar]

In that case perhaps the file was marked as read-only or the bookmarks.dat is corrupted.

[bucker]

no,the file isn't only read,I copy the bookmark.dat content:

ESTREAM

[Offical Symantec]
antivirus=/public/english_us_canada/antivirus_definitions/norton_antivirus/

[Offical Linksys]
WRG54G=//pub/network/

please copy the content to a txt format,and save as bookmarks.dat,put in the flashfxp's directory(please backup your origional bookmarks.dat),lastly,you test the problem.

[bigstar]

It seems your bookmarks.dat is corrupted.

Are you using application password protection?
Have you ever used application password protection
(Sites > Security > Set Password)

Did you upgrade from a previous version, if so which?

It's corrupted because the text "ESTREAM" should not appear in the file when the file is in text format, if you remove that text it should work.

[bucker]

Yes,I had ever used application password protection,but not use now.

I used flashfxp three years,the 3.0.2 b1045 update from previous version:v1.4 build 800->v1.4.3 build 835->and all official final version after v2.0.My site manager last reset time:2001-09-27

But now,remove the text content,the bookmarks.dat is correct,thanks!

[bigstar]

that's probably why, I believe this was a problem in v1.4.x