Strange. What part of the code does it report as the source of the error? Blair
On 11/3/07, tilespace <[EMAIL PROTECTED]> wrote: > > > Ok... I spoke too soon. For some reason, when I refreshed the app > scope, I now get a CF Error: "Complex object types cannot be converted > to simple values." on all of the pages that list the types except for > one. I've copied and pasted the code from the one that works to the > other display pages but they still don't work and yet that one does > (?!??!). We've purposely named all of our display fields the same for > all of our custom types for ease and you can view the code below. > > Does anyone have any insight on this? I've Googled it, I've search > here in the FarCry groups but it seems like we're the only ones that > have come across this :/ > > <!--- @@displayname: Hotspot List Teaser ---> > <cfset myNavID = StructNew()> > <cfset a = StructInsert(myNavID, "navid", "#request.navid#")> > <cfoutput> > <!--- Show hotspot name and link it to full hotspot details item > ---> > <tr> > <td colspan=4><b><skin:buildLink objectid="#stObj.objectid#" > stParameters="#myNavID#">#stObj.label#</skin:buildLink></b></td> > </tr> > <tr> > <td><cfif len(trim(stObj.locations)) GT > 0>#stObj.locations#<cfelse>#stObj.addr1#</cfif></td> > <td>#stObj.hours#</td> > <td>#stObj.cost#</td> > <td><cfif len(trim(stObj.phone)) GT > 0>#stObj.phone#<cfelse>#stObj.website#</cfif></td> > </tr> > </cfoutput> > > Oh and I've moved the code that creates the struct inside the cfoutput > tags as well and received the same error... > > On Nov 2, 10:06 am, tilespace <[EMAIL PROTECTED]> wrote: > > You're a life saver Blair! The orange flavored even! :) > > I had to go grab your rewrite rule from another post here but once i > > implemented that and changed all of the links to skin:buildLink, > > everything worked great! > > > > Thanks again for your patience with my barrage of questions and > > issues :) > > > > On Nov 1, 4:58 pm, "Blair McKenzie" <[EMAIL PROTECTED]> wrote: > > > > > > > > > If you need to add url parameters, I believe the buildlink tag accepts > a > > > stParams attribute (or something :). For inserting an image ... not > sure > > > what to do there. The core would probably have to be extended so that > > > innerHTML can provide start and end copy to put in front of selected > text > > > and after. > > > > > You could put a ticket in the bug tracker for an improvement, but that > > > probably won't help right now. > > > > > Blair > > > > > On 11/2/07, 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 -- 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 -~----------~----~----~----~------~----~------~--~---
