Ok, so for the first issue, we found a quicker way... Pretty much the
same thing (manual copy and paste) but less steps...

On Nov 1, 4:45 pm, tilespace <[EMAIL PROTECTED]> wrote:
> Ok... So we tried Stephen's suggestion for the first item and Blair's
> for the second item and they both work great! Almost. LOL
>
> I shoulda mentioned that for the linking to internal pages, we're
> using images. So when we follow the "click the FarCry button" as
> above, everything works great except it inputs a text link. We've
> tried inserting the image and then using the FarCry button but alas
> that doesn't work :/ Our current solution is training the data-entry
> people to create the association through the FarCry button first,
> highlighting the text, clicking the insert/edit link button, copying
> the (now) FU link, inserting the image, clicking the image and then
> clicking the insert/edit link again, pasting the FU link, updating
> then closing the popup, then deleting the text version (eh).
>
> For making our custom types FU, Blair's solution worked except we now
> lost our breadcrumb and primary navigation highlighting since the
> skin:buildlink tag won't take the objectid and navid and, as far as we
> can see, the buildLink.cfm file doesn't allow the passing of a navid
> (or similar) variable. Oh well, at least the important part (SEO
> friendly) works!
>
> Thanks again both of you!
>
> On Nov 1, 3:33 pm, tilespace <[EMAIL PROTECTED]> wrote:
>
>
>
> > That is awesome! Thank you! It definitely gives us a starting point
> > which is what we need :)
>
> > Thank you again!
>
> > On Nov 1, 3:22 pm, "Stephen Moretti" <[EMAIL PROTECTED]>
> > wrote:
>
> > > On 01/11/2007, tilespace <[EMAIL PROTECTED]> wrote:
>
> > > > For example:
> > > > We create an HTML page. We have a link that needs to go to another
> > > > page that we've created. We click on the "Insert/Edit Link" button in
> > > > TinyMCE and we choose the appropriate page in the dropdown. We click
> > > > the "Save" button and approve the new page. When we pull the site up,
> > > > go to our new page and click on our link, we still have
> > > > "objectid=23432kljlk23;kjj;234lk2jk34l2j3lk4;jlk32432". Do we need to
> > > > modify the core files? If so, which ones?
>
> > > You need to associate the appropriate navigation links with your HTML page
> > > and then use the Farcry icon in the editor to select the navigation link 
> > > you
> > > want to add.  There should be a display option to insert a friendly URL 
> > > for
> > > the selected navigation item.
>
> > > The other issue that we have is that we now have many (8+) custom
>
> > > > modules/types with many (50+) items in each. We need to be able to
> > > > link to more than a few of these individual items throughout the site
> > > > but these also don't show up when we click on "Insert/Edit Link". Do
> > > > we need to also modify the core files for this functionality? And, if
> > > > so, which ones?
>
> > > You need to extend the dmHTML type to allow you to associate more types 
> > > with
> > > your html pages.  You actually only need up extend the dmhtml property
> > > aObjectID by copying the existing one and adding your types to the ftJoin
> > > attribute. You'll also need to add insertHTML_blah.cfm webskin files for
> > > each of your data types, so that the farcry tool will know how to insert
> > > links to your custom types.
>
> > > There should never be any need to meddle with the core code - everything 
> > > is
> > > extendible. ;)
>
> > > I hope that helps point you in the right direction.
>
> > > Regards
>
> > > Stephen- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -


--~--~---------~--~----~------------~-------~--~----~
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