I sure hope this isn't a duplicate post.

I just upgraded my FarCry 3.0.2 to 4.0.11 and when I attempt to edit a
news story, it fails with:

 The CATEGORYID argument passed to the getCategoryNamebyID function is
not of type uuid.
If the component name is specified as a type of this argument, its
possible that a definition file for the component cannot be found or
is not accessible.

The error occurred in
C:\websites\farcry4\core\packages\farcry\category.cfc: line 26
Called from C:\websites\farcry4\core\packages\formtools\category.cfc:
line 43
Called from C:\websites\farcry4\core\tags\wizard\object.cfm: line 378
Called from C:\websites\farcry4\core\tags\wizard\object.cfm: line 375
Called from C:\websites\farcry4\core\tags\wizard\object.cfm: line 370
Called from C:\websites\farcry4\core\tags\wizard\object.cfm: line 245
Called from C:\websites\farcry4\core\tags\wizard\object.cfm: line 1
Called from C:\websites\farcry4\core\packages\types\types.cfc: line
1146
Called from C:\websites\farcry4\core\admin\conjuror\invocation.cfm:
line 180

I looked in category.cfc and it indeed requires a UUID to be passed to
it.

In the database, there's a column in dmNews called catNews, but it's
null. In 3.0.2, each news item had an array of categories in
refCategories, which could then be looked up in the categories table.

On the 4.0 Upgrading from Earlier Version Guide, it says something
about array property faults and that I should check for all direct
references to array property tables (ie. those that bypass fourq) and
tha tit mayrequires a change from objectid to parentid in most cases.
But I'm not really sure what that means.

--
Rob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to