|
Here is our current content targeting approach,
still rough, but it functions (BTW it is still missing some admin security
stuff).
OK to give it a whirl
--> deploy the cmContentTargets.cfc from
the packages/types folder
--> place the contentTarget.cfc in the
packages/custom
--> put the contentTarget.cfm in your
customAdmin and target it wherever you want
Once you have setup some targets, lay down this to
your tag to your liking:
<cfscript>
o = createObject("component",
"#application.custompackagepath#.custom.contentTarget");
o.getDisplay(objectID="#url.ObjectID#", type="dmfacts",
teaser="displayTeaser", numItems="1",isRandom="yes");
</cfscript>
--> objectID should always be the
url
--> type is what you are targeting
--> teasers are the webskin teasers
without the .cfm
--> numItems is how many to
show
--> isRandom is whether it is random or
not
It may still be buggy as I am not totally done
yet. With that said I think Chris is on to something much better.
This approach is more for if the client really should not even be trying to mess
with containers :)
Chris, I will meet you in a dark ally to settle
this battle :)
Regards,
Michael J. Sammut ________________________________________________ F O U R E Y E S P R O D U C T I O N S think | plan | create :: web site design & development :: NYC E. [EMAIL PROTECTED] | T: 718.254.9557 ext. 101 | F: 718.254.0399 W. http://www.foureyes.com |
contentTargeting.cfm
Description: Binary data
contentTarget.cfc
Description: Binary data
cmContentTargets.cfc
Description: Binary data
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
