Difference between revisions of "Issues:027"
Josef.Noll (Talk | contribs) (Created page with "{{Issue Template |Headline=LinkedIN address not shown |Issue Status=New |Issue Type=Bug |Priority=Normal |Description=I tried to show the LinkedIN address of users in the "par...") |
|||
Line 1: | Line 1: | ||
{{Issue Template | {{Issue Template | ||
|Headline=LinkedIN address not shown | |Headline=LinkedIN address not shown | ||
− | |Issue Status= | + | |Issue Status=Closed |
|Issue Type=Bug | |Issue Type=Bug | ||
|Priority=Normal | |Priority=Normal | ||
Line 10: | Line 10: | ||
|Created By=Josef.Noll | |Created By=Josef.Noll | ||
|Creation date=2017/10/14 | |Creation date=2017/10/14 | ||
+ | }} | ||
+ | {{Response Template | ||
+ | |Response=Hi Josef. | ||
+ | |||
+ | I have fixed this. The User short template was not storing the LinkedIn field to the property. | ||
+ | |||
+ | I also modified the Partner User template you use in listings to have the LinkedIn field, otherwise it was appearing in the e: line in the listing. | ||
+ | |||
+ | One other thing, I notice you are using colons in field names e.g. {{{LinkedIn company:}}}, {{{Web:}}} etc. You should avoid this as arraymaps (and other things in SMW) do not like colons. | ||
+ | |||
+ | Also, when using arraymaps it's best to avoid having a single x. The way arraymaps work, if the value in the field contains an x only that letter will get put into the array. I always use xx to avoid this as no words have a double x in them :) | ||
+ | |Response Date=2017/11/01 | ||
+ | |Response By=Neill | ||
}} | }} |
Latest revision as of 09:15, 1 November 2017
Go to Issue Log page | ||||||||||||||||||
|
|