'Cascade' tickbox

Hi,


We have a public-permission asset builder that creates a new asset of type ‘user’, but also uses a metadata schema to take additional details such as mobile phone number, state/territory etc. -> http://mybusinessinrealestate.com/create_accoun



The metadata fields are displayed on the front end for the public user to fill out.



Absolutely no problems with this implementation until we upgraded our version of MySource Matrix to 3.18.7.



Now on the front-end, along with the metadata field, each field also has a ‘cascade’ tickbox next to it.



I understand what this field does and why it is there, but it makes no sense to the public user and looks quite ordinary on our registration form.



My question is: is there any way to turn it off or any way to stop it displaying?



Any help greatly appreciated…

Currently, you have to hide it using JS/CSS. In 3.20, you will be able to turn it off.


Any idea how you would do it with CSS?

Check this post: http://forums.matrix.squiz.net/index.php?showtopic=5676&st=0&p=28026&#entry28026

Thanks, that's done the trick.

This is a really dumb feature...I look forward to it being fixed.

Greg, do you guys ever post code to patch things like this? Or would that have to be talked about with Squiz support? I am sure there would be lots of people here on the forums that would be interested in a patch if it was just a file or two to update.

No, we don't provided patches. Giving you a patch would be against the SLA provided by the Squiz office in your country (or AU in your case). You need to contact Squiz directly to have them patch your system so they can continue to warrant the code.



And to be clearer, there is no patch for this yet. It will be in 3.20.0 when it gets done sometime this month. So nothing right now.

[quote]No, we don't provided patches. Giving you a patch would be against the SLA provided by the Squiz office in your country (or AU in your case). You need to contact Squiz directly to have them patch your system so they can continue to warrant the code.


And to be clearer, there is no patch for this yet. It will be in 3.20.0 when it gets done sometime this month. So nothing right now.[/quote]



Thanks, just curious. :slight_smile:

Same bug for me. Looking forward to my SLA fixing this :wink: