saving files after upload with firefox failed [resolved?]

[Flashbaer]

Hi, maybe I found a small Bug in WeBuilder 2008 9.0.0.97:
I created a simple HTML-file (index.html) and uploaded it with firefox 3 to the validator.w3.org. After upload, I edited the file and tried to save it again, but WeBuilder throwed the message: "The file cannot be saved with the specified name. Ensure that the file index.html is not Read-Only or specify different filename." This message came every time I clicked on "Save", until I closed the Firefox-Tab with the validator.
Saving the file with other applications was successful.
Is this a Bug of WeBuilder or Firefox or first a mistake of myself?
Greetings
Flashbaer

[chrisjlocke]

Sounds more like Firefox keeping the file open, which is unusual.
There is a program called 'Unlocker' which can detail whats keeping a file open, and also allow you to close the file handle. Its free, too.

http://ccollomb.free.fr/unlocker/
.

[Karlis]

WeBuilder will not save a file that is marked by another application as being currently written to, this may cause data loss. I know, other apps my just save and not look (thus you do not get error with other applications), but if some app has locked the file, the status must be respected. The problem may occur if some application locks the file permanently and forgets to unlock it. It looks like this might be the case.

[PARoss]

If this is a fix I didn't notice. If FX 3 is open and viewing the file, then Webuilder will not save it until FX is not viewing the program. Since I use FX Web Developer Toolbar functions to assist design, this has become a problem. It wasn't that way before. Please advise.

[MikeyB]

If this is a fix I didn't notice. If FX 3 is open and viewing the file, then Webuilder will not save it until FX is not viewing the program. Since I use FX Web Developer Toolbar functions to assist design, this has become a problem. It wasn't that way before. Please advise.

If Firefox has got the file locked, then no other program would be able to save the file, the only solution is to close Firefox.

It could even be the Web Developer Toolbar causing Firefox to have a lock on the file, as a test disable the Web Developer Toolbar and try again.

But this still doesn't solve the problem, but then there would be nothing that Karlis could do if Firefox has got the file locked.

[syrupcore]

If this is a fix I didn't notice. If FX 3 is open and viewing the file, then Webuilder will not save it until FX is not viewing the program. Since I use FX Web Developer Toolbar functions to assist design, this has become a problem. It wasn't that way before. Please advise.

Are you using the web dev toolbar save feature when editing the html? I can see that causing problems. Not on a computer with webuilder at the moment so I can't test it. If the save feature is the problem, you might try copy and pasting into webuilder when you want to save. Not ideal but it'd be super quick with: ctrl+a, ctrl+c, alt+tab (to WB), ctrl+a, ctrl+v, ctrl+s. :D

nerdily yours,
will

[PARoss]

Will,

No, the problem is with Webuilder. I get an error message that the file is read-only. And when I go look at the folder the read-only box is not checked, but filled in with a color. It's not empty, but half checked. I then used Windows to make the files not read-only, Windows does its thing. But the files are still the same. It may be a Windows setting that got changed. I don't know. But the problem is driving me nuts.

I disabled WebDev, and the problem persists.

Phil

[Karlis]

By read only you should understand read only or locked. The error message might not be as clear, but the fact is that the file is marked as unwriteable.

You can try this program:
http://ccollomb.free.fr/unlocker/

It will show what is going on with the file. Maybe it helps to solve the mystery.

[ouzo]

Hi,

I have still the same problem but an other environment:


I open and save the files direct on my Intranet-Server via a netshare . The Server runs an IIS . After loading the Page in any Browser the file is about 30 sec. locked. After that time I can store the files again.

This behavior is only with your Editor, all other Editors saves without problem directly.

[Karlis]

This behavior is only with your Editor, all other Editors saves without problem directly.

Yes, because they do not honor locked status set by the other program which may cause data loss and damage to your file. The FireFox has a known bug with locking the files for writing and failing to unlock them. Not sure about the web server, but probably it is the case too.

[ouzo]

yes ,you do honor the lock-status. But I use now an other Editor who does it not. Sorry for you.

I must work..

Or you make an Option to disable this.

[PARoss]

Carlis, I agree. It is the worst feature of Webuilder -- and it's new. It didn't used to be this way.

Either make it optional, or make it an alert with an option to continue saving anyway.

Phil

[Jay Q]

FTR, on my system, it's Firebug not Firefox that's the problem. Went through the usual drill of disabling add-ons, restarting. Narrowed it down to Firebug. Found that when I reverted to version 1.2.1, the file-locking stopped, so this behavior starts from 1.3.0 (I reinstalled 1.3.0 to confirm).

I have to agree with the posters who request some kind of option for this feature. While I appreciate your diligence in wanting to ensure that files don't get inadvertently overwritten, I would also hope that you appreciate the need we, as developers, have in being able to control this kind of behavior. in my job, I'm constantly having to modify then upload files, and the way I'm most productive is using Firefox and Firebug. Yes, there are workarounds, but the time wasted on workarounds defeats the purpose of trying to increase productivity. And besides, undo is just a few clicks away; it seems like an extremely unlikely case where one would be editing a file in another app and simultaneously editing in WB while making changes in both apps. And if someone chooses to work that sloppily, I'd rather not pay for their sloppy practices .

You give us an option for reloading a file that was overwritten elsewhere (e.g., when one downloads a file that's currently open in WB) -- that's a good option because it gives us a choice. The same would be appreciated in this instance -- I'd prefer an option that can be set, but even a pop-up message on each save attempt would be preferable to the current behavior.

[Karlis]

Ok, can you also list the version of FireFox and Windows you are running? I am running FireFox 3.0.8 and FireBug 1.3.3 and do not have this problem. I'll try to submit a bug-report to the developers of FireBug if I become able to reproduce the problem.

EDIT

This appears to have been a confirmed BUG in FireBug extension. They seem to have fixed this BUG already (see http://code.google.com/p/fbug/issues/detail?id=1357)

[PARoss]

Karlis,

I'm using Fx 3.0.8 and Firebug 1.3.3, too. And when I open in Firefox a local computer file that is being simultaneously edited by Webuilder, I cannot save the edited file in Webulder.

Error message: "The file cannot be saved with specified name. Ensure that the file about.htm is not Read-Only or specify different filename." It happens every time, all the time, and it is not Read-Only.

Phil