Using CoreFTP Lite 1.3c
When I click "New Site" button in site manager, and type in my information, it adds the new site. But, it also picks another site, and changes that site's information to match the new site's.
For example, say I have Sites A, B, and C. I click the new site button and fill in the information for site D. The next time I use Coreftp, I have sites A, D, C, and D. Site B is no longer there, and site D is there twice.
I know this was not a problem with earlier versions of CoreFTPLite. I am surprised that this problem hasn't been posted here before.
adding a new site zaps an old one?
Build: 1437
Re-indexing has fixed this for me in the past, and did again this time. I was able to add a few new sites after re-indexing, without affecting previous sites. I guess I will make it a habit to re-index every time, before I add a new site.
But, this is a bug, it should never happen. Right?
More info which might help you fix it, the first time this happened, I saw that site "D" was in there twice. I deleted one, which also deleted the other one at the same time, so they were both gone. Looking in the idx file, the same number appears twice. The bottom entry in the idx file list is the same as one above it.
I could answer other questions about this if you have any.
Re-indexing has fixed this for me in the past, and did again this time. I was able to add a few new sites after re-indexing, without affecting previous sites. I guess I will make it a habit to re-index every time, before I add a new site.
But, this is a bug, it should never happen. Right?
More info which might help you fix it, the first time this happened, I saw that site "D" was in there twice. I deleted one, which also deleted the other one at the same time, so they were both gone. Looking in the idx file, the same number appears twice. The bottom entry in the idx file list is the same as one above it.
I could answer other questions about this if you have any.
I will do this.
You may have heard this before, but having different versions (1.3c) with the same version number (just build number is different) is confusing. If you are releasing a new build so that people can download it, change the version number, too. It makes it easier to ensure I have the latest version.
You may have heard this before, but having different versions (1.3c) with the same version number (just build number is different) is confusing. If you are releasing a new build so that people can download it, change the version number, too. It makes it easier to ensure I have the latest version.