I've also done the CW4 integration. Funny, they still rely on matching querystrings for a lot of their presentation logic. It's a problem because of the url.furl creates mismatches. They also use url.view in the accounts are; i changed it to url.cw4view. And I replaced all the cfhtmlhead to skin:loadjs. Also had to make sure the application name is the same as farcry's. Still, it's a great jump from cw3 and integration was much easier this time around. Chris, I'm going to have a go at setData() on my next cw4 project. From memory it doesn't (or hasn't for me) automatically create the furl.
Initially my though was to create a url.cwfurl at the cartweaver end. At the server rewrite end if the uri started with /products (eg /products/my-thing-a-me-jig) i would rewrite to this: furl=/products&cwfurl=/my-thing-a-me-jig. Then get cartweaver to look it's own table of cwfurl's. This may still be the way I go. I'm still not sold on the whole SEO argument on online stores needing this level of friendlies. Phil -- -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
