jilly said the following on 08/05/2010 10:08 AM: > Does eventContext.displayView() change the enablecfoutputonly setting > to "yes" in 1.8? I had to add: > <cfsetting enablecfoutputonly="no"> > to my layout view to get the content to display correctly after > upgrading from 1.6! > > Yes, we added some aggressive whitespace handling in Mach-II 1.8. However, problems like this are caused by extra <cfsetting enablecfouputOnly="xxx"> in an application code base. This tag doesn't work exactly right because saying enablecfouputonly="true" *twice* and doing enablecfouputonly="false" only *once* doesn't turn off the output only part. They have to be done in pairs. So if it's turned on twice; it has to be turned off twice.
Based on your question, it sounds like you are dynamically via the EventContext calling a view from a filter or something. Is that true? If so, then this ticket applies to you: http://trac.mach-ii.com/machii/ticket/522 Can you share some code? It could be as simple as the "output" attribute on the function being set to false or left off entirely (the "output" attribute is not a true boolean in Adobe CF it is a tripod). .pjf -- You received this message because you are subscribed to Mach-II for CFML list. 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/mach-ii-for-coldfusion?hl=en ***New URLs as of April 29th, 2010*** SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
