Maybe I'm crazy, but I would really think that the two systems would be tied together, so that if the client says that version 1.2.3 is the most recent, the web site would agree.  I just spent 20 min going through all of my addons checking the client installed version against the site latest version.  Around a dozen that needed to be updated.  Further, the client is now whining about BankItems being messed up, even though I installed it via the client from the site.

I'm interested in this too.

The curse client is showing all my addons and says they are all up to date... except when I follow the "view addon website" link, I find that a newer version of some addons exist that doesn't match the "latest" column of the client. Which kinda defeats of the object of having the client. (Found this today with Cartographer, GridIndicatorCornerPlus and even XLoot - which was updated for version 3.1 and the client hadn't told me about).

I am using the free service (3.0.0.9) under Vista64, everything else works (addons do update, I can click on "install via the client" links on the website, etc). I have it set for "Regular" releases (which the website says these are). The install path to WoW is listed in the configuration as "D:/Games/WoW/" (which is correct, albeit with "/" instead of "\")

What's the point of having an addon updater that doens't tell you that your addons need updating?

Both are linked and working on the same DB. Can you please give us some exemples. Thanks

Hubert

Already mentioned Cartographer, etc above.

One I still haven't updated.... SCT - Damage. I have v3.22 installed. The client says latest is v3.22. However the latest as shown on the website is listed as 3.3

Cut-and-Paste from the client....

Installed:v3.22 (Released: 2008/10/18)
Latest: v3.22 (Released: 2008/10/18)

From the website....

Project updated: 2 days ago.

http://wow.curse.com/downloads/wow-addons/details/sct-damage.aspx

Other?....

FreeRefills ( http://wow.curse.com/downloads/wow-addons/details/free-refills.aspx )

Client shows latest and installed as :

Installed:r89-release (Released: 2009/07/19)
Latest: r89-release (Released: 2009/07/19)

Website lists it as : r91-release (updated yesterday).

Most of the "essentials", I've already updated manually. These are two I missed.

HeHeHe... I kinda point out the same issue in the forum I posted (http://www.curse.com/forums/t/111168.aspx) but no administrator has responded to my forum with a "stalling" response.

I definately agree with what ur saying Balkias. A perfect example that the two ARE NOT linked is the situation I'm in. I can obviously login to the site, since I'm posting this response, but when I try to login to the client (using the SAME account name and the SAME password that I use on the site) a "failed to login" message pops up after a 5 second countdown D:

I wouldn't be complaining about my example if the client was a little more honest and said "Failed to connect to Curse.com" But no! Instead it gives me the misleading idea that I have to start a new account and password. But even then, it's the same outcome.

THERE! THAT is a PERFECT example, Mr. Curse Administrator Man, That the client and the website ARE NOT "working on the same DB". If they are, curse needs to check the wires or someshit cuz they sure as **** aren't communicating.

I know this reply didnt help Balkias. But at least Mr. Curse Administrator Man has another example showing the system is a bit unorganized.

Thank you for your replies guy. The curse client  is installing the latest versions for all the exemple for me. I will try to reproduce this issue.

Hubert

Two other bits of information.

First...
It's looks like it may not be EVERY addon.
http://wow.curse.com/downloads/wow-addons/details/grid-status-raid-debuff.aspx was updated today, and is listed as a possible update.

Second...
Thinking perhaps the cache/configuration/whatever maybe borked, I decided to delete the C:\Users\####\AppData\Local\CurseClient folder, so the client would recreate it. It has, but the vaste majority of my addons are listed under the "Unidentified Addons" tabs now instead. This happened the first time I installed the client too, and then I did the "install selected match" for each of the addons. This maybe something that is unrelated/insignificant - but perhaps it isn't.

I havent checked all of my addons but X-Perl is showing version 3.0.5c as the most current version on the site, but the Curse client was saying 3.0.3c was the most current.  Until, that is, I used WoWMatrix and upgraded it to 3.0.5c.  Now the Curse client has jumped on the 3.0.5c bandwagon.

Also, as mentioned above Cartographer is having the same issue.

Finally, what the heck is up with the Curse website?  If you go to Addons, click in the search box, and type x-perl it says in the drop down that there are 5 results.  However when you actually hit return, or click on that, it says "sorry charlie, no results found".  Ummm... oook...

I've had the same problem with Omen Threat Meter and RatingBuster. I was curious why they hadn't issued 3.2 compatible updates days later. Sure enough I go to their Curse websites and they did.

The Curse Client is telling me everything is up to date though.  I just downloaded the updates myself.

[Edit]

It HAS been detecting updates for other addons. Only a few seem to be affected.

same problem for me:

i have installed Outfitter 4.7.4., when i click "View at Curse.com" it shows

even when i try the button 'install via curse client' it stays on the old version

and another problem with BloodyRare - but a closer look shows a even deeper problem:

BloodyRare.toc hast the line "## Version: 1.1d", but the client says: "BloodyRare-1.31" - so probably the versionising is done on different places and not the same on each of them..... 

ok - i see now, that outfitter 4.8b6 is a 'beta' - but strage for me is: the download-button http://wow.curse.com/downloads/wow-addons/details/outfitter.aspx gives me this beta.

i think i remember the there usually i did not get betas?

Okay.... so more information...

After the issues immediately after the patch, I fired up the curse client, renamed the ./interface/addons folder and created a new empty one. I then followed each "view addon website" link for all the addons I had just moved/removed (using the website to get the latest version) and used the website's "install via curse client" button.

My aim was to ensure I had the absolute latest version of the addons, and to have only gotten then via the client.

For the last few days, it's worked as I would have expected. New addons being issued or fixed for the 3.2 patch being released all the time and the client seeing those new versions.

However, today I did a few more checks and found that the GridAutoFrameSize addon has been updated from 2.3.5 to 2.3.6 - and the client hasn't picked up on it again. Linky: http://wow.curse.com/downloads/wow-addons/details/grid-auto-frame-size.aspx

Whatever it is, it's still with us.

I should say I also use ***Matrix these days to double check the curse client's recommendations (it's how I new GridAutoFrameSize has been updated). Whilst the number of addons it can deal with these days has been severely curtailed - it at least does work for the remaining ones. I realise I'm muddying the issue by mentioning it, as there might be attemptation to blame it blindly. But if you guys are investigating this, you need to know all the relevant information. I should point out I've not actually used WoWMat*** to actually update any addons - just draw my attention to version changed missed by the curse client.

Just skimmed through the thread.

The main issue with the Curse Client vs the downloads on the sites has to do with your install preferences.

The Curse Client is set to install Release versions only.  That means that an author has to explicitly state "I want this addon to be a release version".  You can configure this setting per addon or for all addons within the Curse Client (right click on the addon, select install type).

The other two options are Beta and Alpha.

Alpha's are essentially the latest set of code from the author.  I'll use my work as an example.  My alphas may have bugs, typos, etc in them. These are usually fixed quickly, but sometimes it takes a day to fix it.  If you install alphas, you may get errors now and then, however you will have the latest version always.

Betas can be viewed as a stable version of an alpha.  We have new features in an addon we want people to try out, but there may be some functional bugs here and there.

Woetoo: I just mentioned I skimmed through the thread. ;)  That post wasn't directed at you specifically, more of a general post for peoples information.

This grid file is a release, and the client is picking up 2.3.5 as the latest downloadable release?  What happens when you hit the "refresh' button within the client?

Hmm this is really throwing me for a loop.

In my tests I had 2.3.6 show up in the client.

Lets try manually deleting the addon database.  Exit the client, then look for the folder with CurseClient.log (don't know where it is exactly somewhere in app data).  Delete that file and then load the client up again.

My bad, just delete all the .log files where the CurseClient.log is. :)

I have had exactly the same problems described here.  I also notice that occassionally, when you do a search on curse.com for an addon, the "Updated" date on the search page is often out of date.  I don't know if this is related or not, but it's worth a look...

For example, do a search right now on curse.com for "Deadly Boss Mods".  You will see that the "Updated" date says 6/4/2009 - but when you click through to the addon's page, it was actually updated on August 12th.