You should be able to upgrade directly.

If you've modified the template for the add-on in some way, it is designed to be able to be upgraded without manual merges. That was the purpose of the templating system -- so you don't need to worry about updating the add-on and losing customized design changes :)

Thanks for your timely reply, elyon. I'm still going to need to unpack and inspect the package before installing it.

Also, I do not 'connect' my client's c5 based websites to the 'community.' Doing so just opens up too many unnecessary privacy & security questions. It doesn't matter if _I_ am comfortable. What matters is my clients who are _not_ comfortable discovering that such a 'connection' exists.

As a developer of websites, I use open source tools whenever possible. Your plug-in saved me a great deal of work and I appreciate that. I will happily pay you for additional licenses if I need them. But I only have three c5 based websites deployed and only one of those has a blog.

Can you please email the package to me or provide a download link?

Also, would you recommend upgrading Wordpress, first, to 3.5 /before/ upgrading the plug-in?

Thanks again & regards,

Carl

WordPress should be fine, so long as the JSON API plugin is installed. If you are going to upgrade both, I might recommend updating the add-on before WordPress, just to know the source if any issues pop up, but I don't expect there to be.

When you are not connected the community, your Profile page here on concrete5.org will let you view your licenses, and download the ZIP for your add-ons you have purchased, here:

http://www.concrete5.org/profile/orders/...

Ah, yes, of course I've seen that download capability before. I guess I just don't spend enough time here! ;-)

Thanks for your help!

Carl