Announcement

01-09-04, 10:44 AM

module problem with upgrade.mvc

Susan Petracco wrote:
>
> 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.
>

What compatibility version are you compiling them with? What version of
the VM are they running?

For that matter, what version is everybody else compiling for or does it
really make a difference?

--
Bill Weiland A2Z Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc ">http://www.emporiumplus.com/store.mvc </A>
Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
PayPal, Gift/Wish List, Froogle/Yahoo datafeed, Shipping & 100+ more
Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm ">http://www.emporiumplus.com/tk3/v3/doc.htm </A>
Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS ">http://www.emporiumplus.com/mivamodu...vc?Screen=SPTS </A>
|

01-09-04, 10:53 AM

module problem with upgrade.mvc

Hi Susan,

This is a Module_API_Version issue (not a compiler version issue).
Modules that report 4.14 as the API version should roll through upgrade.mvc
just fine. If their API version is lower, upgrade.mvc will force you to
deactivate them.

For some reason, upgrade.mvc decides that even compiled modules that
adhere to <4.14 spec shouldn't run. You can, however, still install
and run compiled modules with <4.14 API versions, they just won't be
processed properly through upgrade.mvc.

James

>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]]On Behalf Of William Weiland
>Sent: Friday, January 09, 2004 1:44 PM
>To: [email protected]
>Subject: Re: [mrc] module problem with upgrade.mvc
>
>
>Susan Petracco wrote:
>>
>> 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.
>>
>
>What compatibility version are you compiling them with? What version of
>the VM are they running?
>
>For that matter, what version is everybody else compiling for or does it
>really make a difference?
>
>--
>Bill Weiland A2Z Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc ">http://www.emporiumplus.com/store.mvc </A>
>Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
>PayPal, Gift/Wish List, Froogle/Yahoo datafeed, Shipping & 100+ more
>Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm ">http://www.emporiumplus.com/tk3/v3/doc.htm </A>
>Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS ">http://www.emporiumplus.com/mivamodu...vc?Screen=SPTS </A>
>|
>
>

01-09-04, 11:09 AM

module problem with upgrade.mvc

all mine are compiled -c 4.06

Bill

-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of William Weiland
Sent: Friday, January 09, 2004 1:44 PM
To: [email protected]
Subject: Re: [mrc] module problem with upgrade.mvc

Susan Petracco wrote:
>
> 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.
>

What compatibility version are you compiling them with? What version of
the VM are they running?

For that matter, what version is everybody else compiling for or does it
really make a difference?

--
Bill Weiland A2Z Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc">http://www.emporiumplus.com/store.mvc</A>
Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
PayPal, Gift/Wish List, Froogle/Yahoo datafeed, Shipping & 100+ more
Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm">http://www.emporiumplus.com/tk3/v3/doc.htm</A>
Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS">http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS</A>
|

01-09-04, 11:41 AM

module problem with upgrade.mvc

I don't use any compiler flags.

Thanks for the info James on this; will upgrade the api version. Thought that might be it.
For the mods that don't need the newer API functions, I just left them as is.

Susan Petracco | [email protected]
------------------------------------------
NetBlazon - E-Business for Every Business
www.netblazon.com
------------------------------------------
*** NEW PHONE NUMBER: 281.298.1725 ***

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of James Harrell
> Sent: Friday, January 09, 2004 12:53 PM
> To: William Weiland; [email protected]
> Subject: RE: [mrc] module problem with upgrade.mvc
>
>
> Hi Susan,
>
> This is a Module_API_Version issue (not a compiler version issue).
> Modules that report 4.14 as the API version should roll through upgrade.mvc
> just fine. If their API version is lower, upgrade.mvc will force you to
> deactivate them.
>
> For some reason, upgrade.mvc decides that even compiled modules that
> adhere to <4.14 spec shouldn't run. You can, however, still install
> and run compiled modules with <4.14 API versions, they just won't be
> processed properly through upgrade.mvc.
>
> James
>
> >-----Original Message-----
> >From: [email protected]
> >[mailto:[email protected]]On Behalf Of William Weiland
> >Sent: Friday, January 09, 2004 1:44 PM
> >To: [email protected]
> >Subject: Re: [mrc] module problem with upgrade.mvc
> >
> >
> >Susan Petracco wrote:
> >>
> >> 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.
> >>
> >
> >What compatibility version are you compiling them with? What version of
> >the VM are they running?
> >
> >For that matter, what version is everybody else compiling for or does it
> >really make a difference?
> >
> >--
> >Bill Weiland A2Z Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc">http://www.emporiumplus.com/store.mvc</A>
> >Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
> >PayPal, Gift/Wish List, Froogle/Yahoo datafeed, Shipping & 100+ more
> >Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm">http://www.emporiumplus.com/tk3/v3/doc.htm</A>
> >Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS">http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS</A>
> >|
> >
> >

Announcement

module problem with upgrade.mvc

module problem with upgrade.mvc

Comment

Comment

Comment

Comment