Thanks Blair

Do you have an example of how to use <skin:buildlink> and
<skink:location> ?

Although I guess if I never change the farcry core from 4.09, theres
no harm in continuing to use .fu method as per Tomeks solution.

On Dec 18, 11:44 pm, "Blair McKenzie" <[email protected]> wrote:
> It didn't take you long to find the flaw in the approach :). Mainly you
> should work with what is in the wiki. If you get help with something that
> isn't in the wiki raise it as something to add.
>
> The tag libraries are probably the most reliable - when we do work on them
> it is usually to add features. It's rare for them to be removed or their
> interfaces changed.
>
> The security scope (application.security) is effectively API. To a lesser
> extend so are the components in application.factory. Actually FU might be in
> there, so returnFU is probably OK, but if there is a tag and a function that
> do the same thing the tag will always be more reliable.
>
> Does this make sense?
>
> On Fri, Dec 19, 2008 at 10:36 AM, Tomek Kott <[email protected]> wrote:
> > Hmm, is there a list of approved / explicit API functions?
> > Thanks,
>
> > Tomek
>
> > On Thu, Dec 18, 2008 at 5:26 PM, Blair McKenzie <[email protected]> wrote:
>
> >> <skin:buildLink ... /> creates a link with the friendly URL.
> >> <skin:location ... /> redirects to the friendly URL. Be careful about using
> >> the returnFU function - it's not an explicit API function, so it could
> >> change in the future.
>
> >> Blair
>
> >> On Fri, Dec 19, 2008 at 6:22 AM, Tomek Kott <[email protected]> wrote:
>
> >>> I've usedhttp://www.farcrycore.org/cfcdoc/generally. But it's not
> >>> up-to-date, so I go there to browse and then find the function I need.
> >>> Tomek
>
> >>> On Thu, Dec 18, 2008 at 2:18 PM, BazD <[email protected]> wrote:
>
> >>>> Thanks Jeff, Tomek
>
> >>>> The returnFU solution worked perfectly.
>
> >>>> Its certainly good to know of these kind of components.
>
> >>>> Is there a list somewhere of all the farcry components that can be
> >>>> utilised to obtain information about content items etc ?
>
> >>>> On Dec 18, 6:51 pm, Jeff Coughlin <[email protected]> wrote:
> >>>> > > Quick question on news items.
>
> >>>> > > Ive created a page template on my local machine, which is in a 2
> >>>> > > column format. Left column contains the main page content, and right
> >>>> > > column contains some simple cfml which simply pulls the top 3 news
> >>>> > > items from the database.
>
> >>>> > > So Ive got a news date, news title, news teaser text in there, and
> >>>> at
> >>>> > > the end, a "view more" text link, which takes the user to the main
> >>>> > > news story page. All easy stuff.
>
> >>>> > > However, the site uses friendly URLs, and Im wondering if it is at
> >>>> all
> >>>> > > possible to link form the teaser story to the main news page and
> >>>> > > retain the friendly URL format in the address bar? At the moment,
> >>>> all
> >>>> > > I can see is something like this:
>
> >>>> > > index.cfm?objectid=4627D778-FF1A-359E-243160B10F9C3AC4
>
> >>>> > > when the main news story page appears.
>
> >>>> > > It would be nice if the news story title, was somehow, the friendly
> >>>> > > URL.
>
> >>>> > > Can this done at all ?
>
> >>>> > 1. Which version of FarCry are you using?
> >>>> > 2. How are you listing the news listings? (rule, type webskin/listing,
>
> >>>> > etc)
>
> >>>> > Generally, just using the <skin:buildLink/> custom tag will take care
>
> >>>> > of your needs.  However, if it's still not working you may be missing
>
> >>>> > something else.
>
> >>>> > Regards,
>
> >>>> > --
> >>>> > Jeff Coughlin
> >>>> > Web Application Developerhttp://jeffcoughlin.com
>
>
--~--~---------~--~----~------------~-------~--~----~
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