LOL. I posted here rather than emailing you because I didn't want to bother you. I'm trying to get this done so that we can be on FC6 before you come to Dubbo in January.
I had tried setting stParam and passing it to the view but that also didn't work. This is the exact line from /displayPageSingle.cfm <skin:view objectid="#stobj.objectid#" typename="#stobj.typename#" template="displayHeaderStandard" layoutclass="type-c" /> Then in displayHeaderStandard I've got it dumping attributes, stObj even URL and can't see any sign of layoutclass. Even tried dumping stParam just in case, but it doesn't exist. I did notice when following the execution path that getview from fourq.cfc passes stparam to the runView function but runView doesn't do anything with stParam..... Sorry should have noted before that I'm testing with FarCry 6.1 milestone. Cheers Mark On Dec 2, 2:16 pm, Justin Carter <[email protected]> wrote: > Yep you're right, that is how it should work and we do this all the time. > The alternative is passing in a struct using the stParam attribute - which > that tag already seems to have. I'm not aware of there being any conflicts > though, I assumed the stParam struct would be used and then any individual > attributes would overwrite stParam. > > You could try setting the layout class in the struct before the skin:view > tag is called: > > <cfset stParam.layoutclass = "type-c"> > > Alternatively, if you're not actually populating stParam then just remove > it. It really should work both ways though... > > cheers, > Justin > > > > On Fri, Dec 2, 2011 at 2:05 PM, tHeSmUrF <[email protected]> wrote: > > Hi, > > > In the process again of preparing our FC4 sites for an upgrade to > > FC6.1 and I’m hitting an issue with webskins. Can someone tell me how > > I pass additional parameters to the webskins? > > > On the FC4 sites I have a template in dmInclude of > > displayPageTypeA.cfm. This skin would call in the header (project/ > > webskin/includes/header.cfm) using cfmodule and at the same type pass > > a couple of variables (e.g. layoutclass). The header.cfm file would > > check for the variables and process accordingly. > > > With FC6 I have a similar template in dmInclude called > > displayPageSingle.cfm. This uses <skin:view etc.> to load the /project/ > > webskin/types/displayHeaderStandard webskin. > > > I thought that changing the line in displayPageSingle: > > > <skin:view stParam="#stParam#" objectid="#stobj.objectid#" > > typename="#stobj.typename#" template="displayHeaderStandard"> > > > to > > > <skin:view stParam="#stParam#" objectid="#stobj.objectid#" > > typename="#stobj.typename#" template="displayHeaderStandard" > > layoutclass=”type-c”> > > > Would cause \core\tags\webskin\view.cfm to add the additional > > “layoutclass” to the stParam structure (around line 38 of view.cfm) so > > that layoutclass would be available to displayHeaderStandard but this > > doesn’t seem to be true. Is this how it should work? If not, how do I > > pass variables around the webskins? > > > Cheers > > Mark > > > -- > > You received this message cos you are subscribed to "farcry-dev" Google > > group. > > To post, email: [email protected] > > To unsubscribe, email: [email protected] > > For more options:http://groups.google.com/group/farcry-dev > > -------------------------------- > > Follow us on Twitter:http://twitter.com/farcry- Hide quoted text - > > - Show quoted text - -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
