This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version = NetBeans IDE 7.3 (Build 201302132200) Operating System = Windows Server 2008 R2 version 6.1 running on amd64 Java; VM; Vendor = 1.7.0_09 Runtime = Java HotSpot(TM) 64-Bit Server VM 23.5-b02 Hi, At sporadic times I am unable to save changes I've made to a file. The editor decides that the particular file doesn't have any changes to save. The filename in the tab is highlighted bold to signify that at some point during the edit it understood that changes had happened but the save button (greyed out) or CTRL S doesn't work. I have to open the particular file using another editor such as windows notepad; select all the contents from the same open file in netbeans; paste the contents into windows notepad and save it there; netbeans then recognises the changes and updates the file in the netbeans IDE. I've lost half a days work due to this bug. If I open and edit other files in netbeans whilst the file in question is malfunctioning I can still save changes to the other files. I look forward to seeing the fix :-) Thanks, Lee
Created attachment 134785 [details] IDE log
*** Bug 230158 has been marked as a duplicate of this bug. ***
Did you experience the problem just with 7.3 or e.g. with 7.2 too? Is the problem specific to a certain file's mime-type e.g. php or java or is it generic?
Hi, It was originally happening on 7.2, so we upgraded to 7.3 but the issue is still occurring. I'm only using PHP files so I couldn’t say if it is mime-type specific. Thanks, Lee
I'm the reporter of bug 230158 was has been classified as a duplicate of this bug and in our case we have the problem with an own MIME type. So I think that the problem is not MIME type specific.
*** Bug 226337 has been marked as a duplicate of this bug. ***
Since issue #228991 removes extra CloneableEditorSupport.notifyModify()/notifyUnmodify() call pairs and also CloneableEditorSupport.LOCK_NOTIFY_MODIFY I think this problem could be resolved by that fix. If not please reopen the issue. Thanks. *** This bug has been marked as a duplicate of bug 228991 ***