The Updater also stores versioning and checksum information in its own database. It runs a checksum on the addon files to detect modifications and mark them as "Dirty".
I'm afraid there is currently no way to update locally modified addons automatically, but i'll let Kaelten know about your question/request, and see what he thinks.
Edit:
Further testing reveals, if an addon is out of date and locally modified, its simply marked as "Out of Date", and not "Dirty" anymore, and will simply update, overwriting the local change. I wonder if thats intended behaviour..
Further testing reveals, if an addon is out of date and locally modified, its simply marked as "Out of Date", and not "Dirty" anymore, and will simply update, overwriting the local change. I wonder if thats intended behaviour..
It's not doing that for me :confused:
Dirty Addons stay dirty in my Client even if new versions are available. The lastest version column is not updated for them, even if I click refresh.
Has the client been released without an announcement? Mine has auto-updated to version 2.1.2.0 (no longer with a RC tag). Of course, this could be another release candidate that has removed that tag in preparation for final cosmetic polish.
Has the client been released without an announcement? Mine has auto-updated to version 2.1.2.0 (no longer with a RC tag). Of course, this could be another release candidate that has removed that tag in preparation for final cosmetic polish.
2.1.2.0 was released yesterday for a final testing phase, and if nothing big comes up, today might be the final release.
My PC crashed while downloading a client update. Now the client just crashes, event log says
Faulting application CurseClient.exe, version 0.0.0.0, time stamp 0x49a5db59, faulting module CurseClient.exe, version 0.0.0.0, time stamp 0x49a5db59, exception code 0xc0000417, fault offset 0x00223ddd, process id 0x135c, application start time 0x01c99938ee0f1db1.
No amount of uninstalling and reinstalling of any version I can find seems to make any difference.
Today we will be releasing version 2.1.2.5 of the client. I've tracked down a number of issues, including:
Client launches, and displays a blank window. Confirmed fixed.
Client launches, and after the "Scanning Local Directories" it stalls on "Building Addon List". Confirmed fixed.
Attempting to login produces the message: "An unknown error occurred contacting the server". This fix is not 100% confirmed, but it is related the fix for #2.
If I got that right, when the client detects that WoW is running and a user clicks "Refresh" it does nothing but displays "Scanning local directories", correct?
If it is like that, it should be changed to a notice message ala "Scanning aborted. Please close WoW before scanning again" or so.
Is there another place to download the client executable from? http://www.curseforge.com/projects/curse-client-new/files/ shows 2.1.2.1 as the latest version, but I gather this isn't the latest version. Since I use Linux, I cannot use the autoupdate and the client crashes if I choose to not let it update, would be great if there's an .exe download somewhere. Or any other workaround would be greatly appreciated.
I don't know. The client prompts before login if I want to install the new version, no matter what I choose it just hangs. Previously I just downloaded the .exe and installed the latest version, that worked fine, but now I can't find the .exe anymore. I tried to look through the registry if there's an option to completely disable checking for updates, I couldn't find any.
I had issues where the CurseClient was not exiting correctly and turned into a zombie, preventing the updater to do its duty. If I kill those zombies, the update process continues properly.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm afraid there is currently no way to update locally modified addons automatically, but i'll let Kaelten know about your question/request, and see what he thinks.
Edit:
Further testing reveals, if an addon is out of date and locally modified, its simply marked as "Out of Date", and not "Dirty" anymore, and will simply update, overwriting the local change. I wonder if thats intended behaviour..
It's not doing that for me :confused:
Dirty Addons stay dirty in my Client even if new versions are available. The lastest version column is not updated for them, even if I click refresh.
2.1.2.0 was released yesterday for a final testing phase, and if nothing big comes up, today might be the final release.
I am looking forward to the full release. Is it still happening in a matter of days?
Faulting application CurseClient.exe, version 0.0.0.0, time stamp 0x49a5db59, faulting module CurseClient.exe, version 0.0.0.0, time stamp 0x49a5db59, exception code 0xc0000417, fault offset 0x00223ddd, process id 0x135c, application start time 0x01c99938ee0f1db1.
No amount of uninstalling and reinstalling of any version I can find seems to make any difference.
Anyone any ideas?
I manually scrubbed all references to curse from the registry after an uninstall. The next install started working again.
Today we will be releasing version 2.1.2.5 of the client. I've tracked down a number of issues, including:
Full release or beta/release candidate release?
If it is like that, it should be changed to a notice message ala "Scanning aborted. Please close WoW before scanning again" or so.
If i press 'sign in' I see a message on the bottom 'doing login' -> 'logged in <accountname>' and still i see the login mask.
Kaelten is working on it: http://www.curseforge.com/projects/curse-client-new/tickets/238-login-problems/
I don't know. The client prompts before login if I want to install the new version, no matter what I choose it just hangs. Previously I just downloaded the .exe and installed the latest version, that worked fine, but now I can't find the .exe anymore. I tried to look through the registry if there's an option to completely disable checking for updates, I couldn't find any.
I had issues where the CurseClient was not exiting correctly and turned into a zombie, preventing the updater to do its duty. If I kill those zombies, the update process continues properly.