|
Mailing Lists
|
Home /
Groups /
Fusebox
Error in Fusebox: "Complex object types cannot be converted to simple values"
Hello all.Bouton Jones 07/11/11 02:18 P Quick answer is, dump the vars on that line and see what's really inRey Muradaz 07/11/11 02:44 P >Quick answer is, dump the vars on that line and see what's really inBouton Jones 07/11/11 03:23 P I think your problem is here:Rey Muradaz 07/11/11 05:16 P You're right. All the rest of the code on the admin.adminmenu.cfm template followed your syntax.Bouton Jones 07/11/11 06:00 P No problem--that's why we're all here :). Good luck with the rest ofRey Muradaz 07/11/11 06:47 P Hello all. Please excuse my ignorance. I'm a CF developer starting on a new contract. I have had early experience with Fusebox 3 but my new assignment requires Fusebox 5.1. I have tried to google an answer to this problem without success. I'm trying to add a new fuse to a large legacy application. I'm getting the following error "Complex object types cannot be converted to simple values." for this new line of code in the dsp_adminMenu.cfm template (inside the "admin" folder) <li><a href="#self#?fuseaction=#xfa.grantorGoalObj#">Grantor Goal/Objective</a></li> The code follows the same syntax as the other links in the template such as <li><a href="#self#?fuseaction=#xfa.grantTraining#">Grant Training</a></li> In the circuit.xml file in the admin folder--- following the existing syntax --- I've added the following line of code <set name="xfa.grantorGoalObj" value="grantorGoalObj.addSearch" /> Within the "admin" directory, I've added a subdirectory named "grantorGoalObj" In the parsed\admin.adminmenu.cfm template I've added <cfset xfa.grantorGoalObj.addSearch = "grantorGoalObj.addSearch" /> I think I'm missing something that's unique to fusebox 5.1. Can anyone advise what that might be? Thank you in advance. Quick answer is, dump the vars on that line and see what's really in them--it might not be what you think it is... simple values" Hello all. Please excuse my ignorance. I'm a CF developer starting on a new contract. I have had early experience with Fusebox 3 but my new assignment requires Fusebox 5.1. I have tried to google an answer to this problem without success. I'm trying to add a new fuse to a large legacy application. I'm getting the following error "Complex object types cannot be converted to simple values." for this new line of code in the dsp_adminMenu.cfm template (inside the "admin" folder) <li><a href="#self#?fuseaction=#xfa.grantorGoalObj#">Grantor Goal/Objective</a></li> The code follows the same syntax as the other links in the template such as <li><a href="#self#?fuseaction=#xfa.grantTraining#">Grant Training</a></li> In the circuit.xml file in the admin folder--- following the existing syntax --- I've added the following line of code <set name="xfa.grantorGoalObj" value="grantorGoalObj.addSearch" /> Within the "admin" directory, I've added a subdirectory named "grantorGoalObj" In the parsed\admin.adminmenu.cfm template I've added <cfset xfa.grantorGoalObj.addSearch = "grantorGoalObj.addSearch" /> I think I'm missing something that's unique to fusebox 5.1. Can anyone advise what that might be? Thank you in advance. >Quick answer is, dump the vars on that line and see what's really in >them--it might not be what you think it is... Thank you. By using three CFDUMP tags I see that xfa.grantorGoalObj is a structure and that the other existing fuses are simple values. Any idea why the existing values are simple but the new value is a structure? Is there some requirement in fusebox 4 that I'm leaving out? I have read Nelson and Gigard's Fusebox book and Peter and Papovich's Fusebox book but they were about earlier versions. I think your problem is here: <cfset xfa.grantorGoalObj.addSearch = "grantorGoalObj.addSearch" /> You're turning xfa.grantorGoalObj into a struct by adding the .addSearch child element. The xfa element (grantorGoalObj in this case) should be a simple key with a value of "grantorGoalObj.addSearch", not a struct. Because you're implicitly creating a struct in the parsed\admin.adminmenu.cfm template reference, that's causing CF to choke when it hits that item, because it's looking for a simple value. Try removing the .addSearch child element from the cfset and see if that works... Cheers, REM O- simple values" >Quick answer is, dump the vars on that line and see what's really in >them--it might not be what you think it is... Thank you. By using three CFDUMP tags I see that xfa.grantorGoalObj is a structure and that the other existing fuses are simple values. Any idea why the existing values are simple but the new value is a structure? Is there some requirement in fusebox 4 that I'm leaving out? I have read Nelson and Gigard's Fusebox book and Peter and Papovich's Fusebox book but they were about earlier versions. You're right. All the rest of the code on the admin.adminmenu.cfm template followed your syntax. The change fixed the error. Thank you. Bouton ----- Excess quoted text cut - see Original Post for more ----- No problem--that's why we're all here :). Good luck with the rest of it--don't hesitate to ask if you have more questions... Cheers, REM O- simple values" You're right. All the rest of the code on the admin.adminmenu.cfm template followed your syntax. The change fixed the error. Thank you. Bouton >I think your problem is here: ><cfset xfa.grantorGoalObj.addSearch = "grantorGoalObj.addSearch" /> > >You're turning xfa.grantorGoalObj into a struct by adding the >.addSearch child element. The xfa element (grantorGoalObj in this >case) should be a simple key with a value of "grantorGoalObj.addSearch", not a struct. ----- Excess quoted text cut - see Original Post for more -----
|
May 22, 2013
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||