Difference between revisions of "Issues:006"
Josef.Noll (Talk | contribs) |
|||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Issue Template | {{Issue Template | ||
|Headline="Free form" normal text input before search elements | |Headline="Free form" normal text input before search elements | ||
− | |Issue Status= | + | |Issue Status=Closed |
|Issue Type=Enhancement | |Issue Type=Enhancement | ||
|Priority=Normal | |Priority=Normal | ||
Line 47: | Line 47: | ||
− | I have sorted out the size of the User field and Title field. SF now defaults to input type of textarea for text fields. I have told it that the Title field is input type text which then obeys the size parameter. The User is an array type so needed the size parameter rather than rows and cols :) I'll look at the CSS to sort out the ugly alignment of the dates. | + | I have sorted out the size of the User field and Title field. SF now defaults to input type of textarea for text fields. So I have told it that the Title field is input type text which then obeys the size parameter. The User is an array type so needed the size parameter rather than rows and cols :) I'll look at the CSS to sort out the ugly alignment of the dates. |
|Response Date=2015/10/19 | |Response Date=2015/10/19 | ||
+ | |Response By=Neill | ||
+ | }} | ||
+ | {{Response Template | ||
+ | |Response=Hi Neill, | ||
+ | |||
+ | perfectly okay to omit the "free text" input. What do you suggest we use? We can start from Scratch for Users, as almost no user has information about himself on the page (some might). Thus, please provide me with an example for a new "User" page. | ||
+ | Do you recommend to move them into the "Namespace User:Josef_Noll"? | ||
+ | |Response Date=2015/10/21 | ||
+ | |Response By=Josef.Noll | ||
+ | }} | ||
+ | {{Response Template | ||
+ | |Response=Hi Josef. | ||
+ | |||
+ | We can salvage the free text that is currently captured by using a replace text regex to assign it to a new field in the template. I suggest we call the new field "ItemText" to replace the free text element. | ||
+ | |||
+ | I am working on the new user page. I'll let you know when it's in a state to demo. | ||
+ | |Response Date=2015/10/28 | ||
+ | |Response By=Neill | ||
+ | }} | ||
+ | {{Response Template | ||
+ | |Response=I have replaced the Free Text in the IoT_AI template with a text field. I installed the Replace Text extension and run a regex to convert the existing pages from Free Text to the ItemText field. So now the | ||
+ | "See all Action Items of IoTSec" and "Edit this action item" links now appear under the text as requested. | ||
+ | |||
+ | I've added the category query method of linking to the category pages to sort out the footer merger issue. | ||
+ | |||
+ | I also sorted out the alignment of the dates etc :) | ||
+ | |||
+ | We should look to replace the Free Text with a field in other templates e.g. Meetings. Please let me know if you want me to do this. | ||
+ | |Response Date=2015/11/04 | ||
+ | |Response By=Neill | ||
+ | }} | ||
+ | {{Response Template | ||
+ | |Response=Well done in Form:IoTSec_AI - Yes, please replace the text also in the Meetings, such that it is easier to handle. | ||
+ | A small mistake in Form:IoTSec_AI - When the Form is called within the IoTAdmin namespace, the action item has a double IoTAdmin, like: "IoTAdmin:IoTAdmin:AI-044". | ||
+ | page name=IoTAdmin:AI-<unique number;start=001> | ||
+ | |||
+ | Can you add a query that the page AI-044 is created in the respective namespace IoTAdmin, regardless if you call the page from IoTSec or IoTAdmin namespace? | ||
+ | |Response Page Link=http://cwi.unik.no/wiki/IoTSec:All_Action_Items | ||
+ | |Response Screenshot=Screen Shot 2015-11-11 at 21.34.44.png | ||
+ | |Response Date=2015/11/11 | ||
+ | |Response By=Josef.Noll | ||
+ | }} | ||
+ | {{Response Template | ||
+ | |Response=Hi Josef. | ||
+ | |||
+ | I see the problem with the double IoTAdmin namespace on the page name. You have IoTAdmin hardwired in the form - IoTAdmin:AI-<unique number;start=001> | ||
+ | |||
+ | You should not specify the namespace in the form itself. Instead use the namespace= parameter on the formlink that calls the form to specify which namespace the page will be in. This way you can use the form for multiple namespaces :) | ||
+ | |||
+ | For example, the issues formlink specifies the issues pages are in the Issues namespace using: | ||
+ | |||
+ | <pre>{{#formlink:form=Issue Form|link text=Log a new Issue|link type=button|namespace=Issues}}</pre> | ||
+ | |Response Date=2015/11/24 | ||
|Response By=Neill | |Response By=Neill | ||
}} | }} |
Latest revision as of 11:50, 11 January 2016
Go to Issue Log page | ||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|