You are correct Ad,
I had set up default as default="typeA" (with the quotes and lowercase t).
The cargo tables valid values were defined as values=TypeA,TypeB (without
quotes and using an uppercase T)
The difference was messing up the persistence when the filed was hidden.
The template call was then written as subtype="typeA". When the field was
visible the drop down control apparently would fix things up and write the
template call as subtype=TypeA. The persistence would then work. At least
that is what I think was happening.
The fix was to set default=TypeA as it should have been.
Thanks!
Ed
On Sat, Dec 19, 2015 at 4:29 AM, Ad Strack van Schijndel <
ad.strackvanschijndel(a)gmail.com> wrote:
Hi Ed,
First: this doesn't have to do with Cargo. The form modifies the source
code of the page and the template stores things with Cargo or SMW (or both).
And what you do should work also when the field is hidden. So probably
there is just some error in your field definition.
Is this the exact code you use in your form?
Ad
Op 19 dec. 2015, om 03:26 heeft Ed <edward.hoo(a)gmail.com> het volgende
geschreven:
Hi all,
I'm using Cargo with Semantic Forms. The cargo table is defined in one
template and attached in others. Each has it own form as they represent
subtypes. How can I hardcode the subtype so that when I query the cargo
table holding all the subtypes the info is available?
In one of the forms, I tried with
{{{field|SubType|mandatory|default="TypeA"}}}
and it works. However, when I hide it
{{{field|SubType|mandatory|default="TypeA"|hidden}}}
it does not.
Thoughts? Thanks!
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l