On Thu, Feb 9, 2012 at 3:41 PM, Sean Coyne <coyne.s...@gmail.com> wrote: > What version of FarCry core? I assume you are also using the FarCry CMS > plugin? What version of the plugin?
> -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: farcry-dev@googlegroups.com > To unsubscribe, email: farcry-dev+unsubscribe@googlegroups.com > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry
> On Thu, Feb 9, 2012 at 3:41 PM, Sean Coyne <coyne.s...@gmail.com> wrote:
>> What version of FarCry core? I assume you are also using the FarCry CMS >> plugin? What version of the plugin?
>> -- >> You received this message cos you are subscribed to "farcry-dev" Google >> group. >> To post, email: farcry-dev@googlegroups.com >> To unsubscribe, email: farcry-dev+unsubscribe@googlegroups.com >> For more options: http://groups.google.com/group/farcry-dev >> -------------------------------- >> Follow us on Twitter: http://twitter.com/farcry
Its probably an issue with the category formtool. Have you tried removing the category field from the list of filter fields? Does the label filter work then? If so, you may have to alter the metadata for the category field using the stFilterMetadata attribute of the <ft:objectadmin> tag.
I think this is due to formtools validation on properties that you have included in your filter. You need to override the formtool validation for the object admin.
Try adding the following before <ft:objectadmin replacing/addig property names as required <cfset stFilterMetadata = { status = { ftValidation = "" }, catNews = { ftValidation = "" }
} />
And add the following to your <ft:objectadmin stFilterMetadata="#stFilterMetadata#"
On Fri, Feb 10, 2012 at 1:46 PM, Chris Kent <mxdes...@gmail.com> wrote: > I think this is due to formtools validation on properties that you have > included in your filter. You need to override the formtool validation for > the object admin.
> Try adding the following before <ft:objectadmin replacing/addig property > names as required > <cfset stFilterMetadata = { > status = { ftValidation = "" }, > catNews = { ftValidation = "" } > } />
> And add the following to your <ft:objectadmin > stFilterMetadata="#stFilterMetadata#"
> Chris
> -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: farcry-dev@googlegroups.com > To unsubscribe, email: farcry-dev+unsubscribe@googlegroups.com > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry
> This seems to work in dmNews. Will have a look into other troubling > properties and get back.
> Much appreciated.
> On Fri, Feb 10, 2012 at 1:46 PM, Chris Kent <mxdes...@gmail.com> wrote:
>> I think this is due to formtools validation on properties that you have >> included in your filter. You need to override the formtool validation for >> the object admin.
>> Try adding the following before <ft:objectadmin replacing/addig property >> names as required >> <cfset stFilterMetadata = { >> status = { ftValidation = "" }, >> catNews = { ftValidation = "" } >> } />
>> And add the following to your <ft:objectadmin >> stFilterMetadata="#stFilterMetadata#"
>> Chris
>> -- >> You received this message cos you are subscribed to "farcry-dev" Google >> group. >> To post, email: farcry-dev@googlegroups.com >> To unsubscribe, email: farcry-dev+unsubscribe@googlegroups.com >> For more options: http://groups.google.com/group/farcry-dev >> -------------------------------- >> Follow us on Twitter: http://twitter.com/farcry