Why does upgrade.mvc sometimes say that a module won't work with the new version? Is this
a Module_API_Version issue or something else? It seems to be sporadic - works fine for
most clients, but sometimes it just fails (even when the file has been copied to the new
4.xx/modules branch) and I'd like to have a good answer (or better, a solution!) to this
question.
Susan Petracco | [email protected]
------------------------------------------
NetBlazon - E-Business for Every Business
www.netblazon.com
------------------------------------------
*** NEW PHONE NUMBER: 281.298.1725 ***
Comment