Hide last authors
Ricardo Rodríguez 52.1 1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
Vincent Massol 1.1 4
Ecaterina Moraru (Valica) 102.1 5 This tutorial will show you how to build a Frequently Asked Questions (FAQs) [[Application>>platform:Features.Applications]] much like the one you can find on the [[FAQ page>>FAQ.WebHome]]. This is a very simple application that makes use of XWiki's [[classes, properties, and objects>>platform:DevGuide.DataModel||anchor="HXWikiClasses2CObjects2CandProperties"]]. It also uses a technique that you may frequently use as the basis for several different kinds of applications.
Vincent Massol 96.1 6
Ecaterina Moraru (Valica) 105.1 7 {{info}}
Fawad Ali 117.1 8 It's also possible to follow this tutorial as a [[video tutorial on Youtube>>https://youtu.be/tIzASeJb2Bs]].
Ecaterina Moraru (Valica) 105.1 9 {{/info}}
Vincent Massol 103.1 10
Vincent Massol 96.1 11 = Prerequisites for following the tutorial =
12
Vincent Massol 95.1 13 {{warning}}
Ecaterina Moraru (Valica) 102.1 14 If you've already followed the [[AWM FAQ Tutorial>>Documentation.DevGuide.FAQTutorial.FAQTutorialAWM]] or installed the [[FAQ Application>>extensions:Extension.FAQ Application]] you'll need to do one of 2 things before you can take this tutorial:
Fawad Ali 117.1 15
Vincent Massol 95.1 16 * Delete the ##FAQ## space (if you've followed the AWM FAQ Tutorial) or uninstall the FAQ Application (if you've installed the FAQ Application)
17 * or simply follow the tutorial below but replace the space ##FAQ## with another value everywhere it's used. For example use ##MyFAQ## as the space name instead.
18 {{/warning}}
19
Vincent Massol 101.3 20 You should have [[installed XWiki>>platform:AdminGuide.Installation]] and have a [[basic understanding of how to use it>>platform:Features.WebHome]].
Vincent Massol 54.2 21
Vincent Massol 101.3 22 All through this tutorial you should refer to the [[XWiki Data Model>>platform:DevGuide.DataModel]] for information on XWiki's data model. You might also use the [[XWiki Scripting Guide>>platform:DevGuide.Scripting]] to get you started with scripting in XWiki and manipulating XWiki objects. In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications. Completing this tutorial is a recommended prerequisite for anyone who wants to build custom applications on the XWiki engine.
Vincent Massol 54.3 23
Vincent Massol 100.3 24 {{warning}}
Ecaterina Moraru (Valica) 101.4 25 Make sure that your user is an [[Advanced user>>platform:Features.PageEditing||anchor="HAdvancedMode"]] before following this tutorial since you'll need for example to use the wiki editor (##Wiki > Edit## menu).
Vincent Massol 100.2 26 {{/warning}}
27
Silvia Macovei 48.2 28 = Application Overview =
Vincent Massol 1.1 29
Guillaume Lerouge 42.1 30 The FAQ application allows users to post a question by entering the question into a simple form field and then submitting the form. The question then appears in a list along with all other questions that have been previously posted. Users can click on the questions to view both the question and answer in a consistently styled view. If the question has not yet been answered, any user can post an answer to the question by editing the page. In edit mode, the page will display a web form that is the same for every FAQ page.
Vincent Massol 1.1 31
Manuel Smeria 80.1 32 Let us begin by taking a look at what we are going to build. The new application will have the following views:
Vincent Massol 1.1 33
Vincent Massol 112.1 34 * The FAQ [[Class>>FAQ.WhatIsAClass]](((
Vincent Massol 111.1 35 {{image reference="FAQsSummary.png"/}}
Vincent Massol 112.1 36 )))
37
Marius Dumitru Florea 115.1 38 * An FAQ entry in View mode (notice that the properties can be edited in-place starting with XWiki 12.4RC1)(((
Vincent Massol 111.1 39 {{image reference="FAQSheetView.PNG"/}}
Vincent Massol 112.1 40 )))
41 * An FAQ entry in Edit mode(((
Vincent Massol 111.1 42 {{image reference="FAQSheetEdit.PNG"/}}
Vincent Massol 112.1 43 )))
Hassan Ali 110.1 44
Silvia Macovei 48.2 45 = Authoring Templates and Page Design Sheets =
Silvia Macovei 48.1 46
Anca Luca 14.1 47 An Authoring Template is a template for creating documents of a specific type. Unlike a regular content page in edit mode with one field for freeform editing, an Authoring Template presents a custom set of form fields for creating a document with specific type of data. These form elements are defined by the properties of a class.
Vincent Massol 1.1 48
Silvia Macovei 48.1 49 In object oriented programming, remember that a //class// is a template for an object. Using the analogy of a cookie cutter, the //class// is the //cookie cutter// and the //objects// are the actual //cookies//. An Authoring Template provides one way to represent a class visually so that users can fill out a form to set unique properties (values in form fields). When the user submits the form, they are creating a unique //object// of the //class// type.
Vincent Massol 1.1 50
Anca Luca 14.1 51 Precisely, an Authoring Template is a prototype document used to create other specific instances of documents of the same type, along with a method of exposing the creation process to the user: the properties edit form. Remember that a XWiki Document can contain objects and this is the case of an authoring template: it is a XWiki Document with an empty object of a specific class, which is duplicated to create more and more documents based on that model, using the data inserted by the user in the editing form as specific values for the particular object instance in the current copy.
Vincent Massol 1.1 52
Silvia Macovei 31.6 53 The Page Design Sheet is like a style sheet that defines what each document will look like when rendered. Even though the unique object instances will have different values for their properties, they will always have a consistent presentation display because they will be rendered through the Page Design Sheet. The XWiki API available in scripting languages provides a mechanism that will help us use the same sheet for both editing and view modes. We will see how we can achieve this once we get to the FAQ Design Sheet section.
Vincent Massol 1.1 54
Silvia Macovei 48.2 55 = Go to the Class Editor Wizard =
Silvia Macovei 31.6 56
Bart Kummel 104.1 57 Five pages, which collectively make up a [[XClass application>>extensions:Extension.XClass Application]] (a.k.a Class Wizard or Class Editor Wizard), have been developed to assist you in this process. Those page are technical pages hidden by default. To navigate to the wizard home page, go to your profile page, select the Preferences tab, edit the page and choose to view Hidden Documents. Enter a search query for the keyword "XWikiClasses". This should return a document called ##XWikiClasses## in the ##XWiki## space (i.e. ##XWiki.XWikiClasses##). (Note that the //title// of this document is "Data types".) This is the homepage of the class wizard creator: you are now ready to start building your FAQs application.
Vincent Massol 1.1 58
Silvia Macovei 48.2 59 = Create the FAQ Class =
Vincent Massol 1.1 60
Vincent Massol 111.1 61 * On the Class Editor wizard entry page (XWiki.XWikiClasses), under the heading "Create a new data type", in the "Title" field, enter ##FAQ## as the name of the page to create:(((
Vincent Massol 84.3 62 {{image reference="CreateANewClass1.png"/}}
Silvia Macovei 48.4 63 )))
Vincent Massol 96.2 64 * As you can see in the Breadcrumb below the new page will be created at location ##XWiki > FAQ##. In practice the Class Wizard will automatically prefix the page name with ##Class## (you could also enter ##FAQClass## as the page name directly).
Vincent Massol 111.1 65 * Now it would be nice to have it created in a new location such as ##FAQ > FAQ Class##. Since the ##FAQ## parent doesn't exist we cannot use the Tree picker button. Thus click the Pencil button as shown in the following image and replace ##XWiki## by ##FAQ##.(((
Vincent Massol 84.3 66 {{image reference="CreateANewClass2.png"/}}
67 )))
Vincent Massol 96.2 68 * In technical terms you're creating a page named ##FAQClass## (with a title of "FAQ Class") located in a space also called ##FAQ## and thus the technical reference is ##FAQ.FAQClass##.
Manuel Smeria 80.1 69 * Click the "Create this Class" button. You should then see a page with the following content:(((
Silvia Macovei 48.1 70 {{code language="none"}}
Silvia Macovei 41.1 71 {{velocity}}
simard 60.6 72 ## Replace the default space with the space where you want your documents to be created.
Silvia Macovei 41.1 73 ## Replace the default parent with the one of your choice and save the document.
74 ##
simard 60.6 75 #set($defaultSpace = $doc.space)
76 #set($defaultParent = $doc.fullName)
Silvia Macovei 41.1 77 {{/velocity}}
Silvia Macovei 48.1 78 {{/code}}
Silvia Macovei 48.4 79 )))
Anca Luca 14.1 80
Manuel Smeria 80.1 81 In the code, change the word "$doc.space" with the name of the space where you want you FAQ pages to be created as the commented instructions in the page code suggest.
82 The line of code should look like this:
Vincent Massol 1.1 83
Ricardo Rodríguez 52.1 84 {{code language="none"}}
85 #set($defaultSpace = 'FAQ')
86 {{/code}}
Anca Luca 14.1 87
Manuel Smeria 80.1 88 You can also change the default parent of the new FAQ documents that are going to be created. To do so, replace the "$defaultParent" variable with the name of your document.
89 The line of code should look like this:
Vincent Massol 1.1 90
Ricardo Rodríguez 52.1 91 {{code language="none"}}
92 #set($defaultParent = 'FAQ.WebHome')
93 {{/code}}
Vincent Massol 1.1 94
Guillaume Lerouge 42.1 95 Click the "Save & View" button. The class is now created and you should be looking at a page titled "Class: FAQ" that looks like this:
georgosn 28.1 96
Manuel Smeria 80.1 97 {{image reference="FAQClass1.PNG"/}}
georgosn 29.1 98
Silvia Macovei 48.2 99 = Add Properties to the Class =
Vincent Massol 1.1 100
Silvia Macovei 48.3 101 Under the page title, you should see the words "The class does not have any properties yet. You can use the //__class editor__// to define them." Let's just follow those instructions!
Vincent Massol 1.1 102
Manuel Smeria 80.1 103 * Click on the 'class editor' link
Vincent Massol 92.2 104 * Note that the link trail in the header is something like "Wiki Home / FAQ / FAQ Class". This shows you that you are indeed on the FAQ class page in Class edit mode.
Vincent Massol 1.1 105
Vincent Massol 92.3 106 In our document, we'll store both a //question// and an //answer//. So we need to create a property for each of them.
Vincent Massol 1.1 107
Manuel Smeria 80.1 108 * Enter the text //question// in the "name" field
Vincent Massol 111.1 109 * Choose a TextArea type for the property and then click on "Add". The TextArea will ultimately give us a multi-line text field in our authoring template.(((
Manuel Smeria 80.1 110 {{image reference="AddQuestionProperty.PNG"/}}
Silvia Macovei 48.4 111 )))
Manuel Smeria 80.1 112 * Click on the "+" icon to expand the options for the newly created property
Vincent Massol 111.1 113 * Change the value of the "Pretty Name" field to "Question"(capital Q):(((
Manuel Smeria 80.1 114 {{image reference="QuestionProperty.PNG"/}}
Silvia Macovei 48.4 115 )))
Manuel Smeria 80.1 116 * Now create another property called //answer// the same way that you did for the previous "question" property (choose TextArea for the property type)
117 * Expand it from the property list and change the value of the "Pretty Name" field to "Answer"
118 * When you are done adding and configuring the properties, click the "Save & View" button
Vincent Massol 1.1 119
Silvia Macovei 48.2 120 = Create the Page Design Sheet =
Vincent Massol 1.1 121
Vincent Massol 111.1 122 * After the previous step you are now on the FAQClass page which should look like this:(((
Manuel Smeria 80.1 123 {{image reference="FAQClass2.PNG"/}}
Silvia Macovei 48.4 124 )))
Manuel Smeria 80.1 125 * Click the first button ("Create the document sheet") to create the document sheet (the Page Design Sheet). This sheet determines how your page's objects will be rendered to the user. The document is automatically created.
Vincent Massol 92.4 126 * You should see a warning message with the text "The sheet is not bound to the class so it won't be applied automatically when a page that has an object of this class is displayed". Click the "Bind the sheet to the class" link that appears after the text. **What this does is important**:
OgisTarkan 98.1 127 ** It adds an object of type ##XWiki.ClassSheetBinding## to the ##FAQ.FAQClass" document. Basically it ties the FAQ Class to the Sheet.##
Vincent Massol 92.4 128 ** **It's because of this object that users will be sent to form edition mode when editing FAQ entries**
Vincent Massol 111.1 129 * Now click on "View the sheet document". This takes you to the ##FAQ.FAQSheet## page which you can edit in wiki mode and see its default content:(((
Silvia Macovei 48.1 130 {{code language="none"}}
Silvia Macovei 41.1 131 {{velocity}}
132 ## You can modify this page to customize the presentation of your object.
133 ## At first you should keep the default presentation and just save the document.
Anca Luca 14.1 134
Marius Dumitru Florea 116.1 135 ## We have to use wiki=true because $doc.display() can produce wiki syntax.
136 {{html wiki="true" clean="false"}}
137 ## Load the JavaScript code required to make the object properties editable in-place.
138 #set ($discard = $xwiki.jsfx.use('uicomponents/edit/editableProperty.js', {
139 'forceSkinAction': true,
140 'language': $xcontext.locale
141 }))
142 #set ($editing = $xcontext.action == 'edit')
143 ## The object to display.
144 #set ($xobject = $doc.getObject('FAQ.FAQClass'))
145 ## The class that describes the object properties.
146 #set ($xclass = $xobject.xWikiClass)
147 ## Make sure the following display* method calls use the right object.
148 #set ($discard = $doc.use($xobject))
149 ## Using the xform vertical form layout.
150 <div class="xform">
151 <dl>
152 #foreach ($property in $xclass.properties)
153 <dt #if (!$editing && $hasEdit)
154 class="editableProperty"
155 #set ($xobjectPropertyReference = $xobject.getProperty($property.name).reference)
156 data-property="$escapetool.xml($services.model.serialize($xobjectPropertyReference))"
157 data-property-type="object"#end>
158 ## This must match the id generated by the $doc.display() method below.
159 #set ($propertyId = "${xclass.name}_${xobject.number}_$property.name")
160 <label#if ($editing) for="$escapetool.xml($propertyId)"#end>
161 $escapetool.xml($property.translatedPrettyName)
162 </label>
163 ## Support for specifying a translation key as hint in the property definition.
164 <span class="xHint">$!escapetool.xml($services.localization.render($property.hint))</span>
165 </dt>
166 <dd>$doc.display($property.name)</dd>
167 #end
168 #if (!$xclass.properties || $xclass.properties.size() == 0)
169 ## Keep the empty definition term in order to have valid HTML.
170 <dt></dt>
171 <dd>$escapetool.xml($services.localization.render('xclass.defaultObjectSheet.noProperties'))</dd>
172 #end
173 </dl>
174 </div>
175 {{/html}}
Silvia Macovei 41.1 176 {{/velocity}}
Silvia Macovei 48.1 177 {{/code}}
Guillaume Lerouge 42.1 178
Marius Dumitru Florea 116.1 179 Let's take a moment now and analyze this code:
Silvia Macovei 48.1 180
Marius Dumitru Florea 116.1 181 * first, it loads the JavaScript required for in-place editing
182 * then it retrieves the FAQ object from the current page and the FAQ class defintion
183 * then it iterates through all the FAQ class properties displaying:
184 ** the translated pretty name
185 ** the translated hint
186 ** the value from the FAQ object in view mode, or the form field used to input or modify the value in edit mode
187 * it uses a definition list to display the FAQ object, following the [[Vertical Form>>xwiki:Documentation.DevGuide.FrontendResources.VerticalForms.WebHome]] layout
188
189 As we mentioned, XWiki provides a mechanism that helps us create sheets used for both view and edit mode. This is the ##display## function used in the line:
190
Manuel Smeria 83.1 191 {{code language="none"}}
Marius Dumitru Florea 116.1 192 <dd>$doc.display($property.name)</dd>
Manuel Smeria 83.1 193 {{/code}}
Silvia Macovei 48.1 194
Marius Dumitru Florea 116.1 195 It detects the current mode (edit or view) and displays the property referenced by its argument as the mode dictates:
Manuel Smeria 80.1 196
Marius Dumitru Florea 116.1 197 * in view mode it will display the value of the property
198 * in edit mode it will display a form field that will allow the user to edit it
Guillaume Lerouge 42.1 199
Vincent Massol 101.3 200 This way we can use a single Design Sheet to both display and edit our FAQ entries. See the [[XWiki API reference>>platform:DevGuide.API]] and [[XWiki Scripting>>platform:DevGuide.Scripting]] pages for more details about this.
Marius Dumitru Florea 116.1 201 )))
Guillaume Lerouge 42.1 202 * Click "Save & View"
203
Silvia Macovei 48.2 204 = Create the Authoring Template =
Vincent Massol 1.1 205
Vincent Massol 111.1 206 * Navigate back to the ##FAQ.FAQClass## document (you can use the arrows in the breadcrumb to do so). The document should look like this:(((
Manuel Smeria 80.1 207 {{image reference="FAQClass3.PNG"/}}
Silvia Macovei 48.4 208 )))
Manuel Smeria 80.1 209 * Click on the "Create the document template" button. The Authoring Template will be automatically created.
Vincent Massol 1.1 210
Vincent Massol 101.3 211 Note that earlier, we changed the space name preceding the page name because we wanted all of our FAQ pages to reside in a space named FAQ. Remember that all our documents will be copies of the Authoring Template used as a prototype so the content will be copied in all our FAQs documents and will execute the Design Sheet code in the context of the current document. See the [[dedicated page>>platform:DevGuide.IncludeInVelocity]] for more information regarding this technique.
Guillaume Lerouge 42.1 212
Vincent Massol 92.8 213 Now we need to associate the prototype object with this document to turn it into a true authoring template:
214
215 * If you're on the template page, navigate back to the ##FAQ.FAQClass## document.
216 * At the bottom of the page, look for the following warning message: "The template does not contain an object of type FAQClass. Add a FAQ object to the template »."
Vincent Massol 111.1 217 * Click on "Add a FAQ object to the template »":(((
Manuel Smeria 80.1 218 {{image reference="FAQObject.png"/}}
219 )))
Manuel Smeria 83.1 220
Vincent Massol 92.8 221 Next, we want to remove the title for the newly created template:
Manuel Smeria 83.1 222
Vincent Massol 92.8 223 * Navigate to the ##FAQ.FAQTemplate## document (you can click on the "View the template page (FAQ / FAQ Template)" link for doing that for example.
Manuel Smeria 83.1 224 * Edit this document in Wiki mode
225 * Inside the Title field you have "FAQ Template" written -> delete this text
226 * Save & View
227
228 This step is needed so that all of our future entries don't have "FAQ Template" as their title.
229
230 Congratulations: you just created an Authoring Template! You're almost done now.
Vincent Massol 92.8 231
Manuel Smeria 80.1 232 {{image reference="FAQClass4.PNG"/}}
Ricardo Rodríguez 52.1 233
Alex Cotiugă 105.2 234 = Create the Template Provider =
235
Alex Cotiugă 105.3 236 After the template was created and the object was added, a new section appears with a button to create a template provider to use the existing template.
237 The template provider is created with some default values, but those can be updated to match the needs.
Alex Cotiugă 105.2 238
Alex Cotiugă 107.2 239 {{gallery}}
Alex Cotiugă 108.2 240 image:3-missingTemplateProvider.png
Alex Cotiugă 107.2 241 image:4-addedTemplateProvider.png
242 image:5-templateProviderView.png
243 {{/gallery}}
244
245
Silvia Macovei 48.2 246 = Create a home page for the FAQ application =
Silvia Macovei 38.1 247
Guillaume Lerouge 42.1 248 You want your users to be able to see a list of all existing questions and answers and to add new questions. The best way to do this is to put the FAQ application in its own space and to use that space's homepage to display existing questions.
Vincent Massol 1.1 249
Vincent Massol 93.1 250 Thus we now need to create the ##FAQ.WebHome## page
Vincent Massol 1.1 251
Vincent Massol 93.1 252 * Click on "FAQ" in the breadcrumb to navigate to ##FAQ.WebHome## and notice that the page doesn't exist.
253 * Edit it in wiki mode
254 * Type in the title "FAQs"
255
Silvia Macovei 48.2 256 == Displaying existing FAQ entries ==
Vincent Massol 1.1 257
Manuel Smeria 80.1 258 You have 2 options when it comes to displaying existing FAQ entries:
Guillaume Lerouge 55.2 259
Manuel Smeria 80.1 260 1. Use the livetable component
261 1. Write custom code in order to display them
262
Guillaume Lerouge 55.2 263 === Using the Livetable component ===
264
265 In this section, we will show how to use the [[Livetable Macro>>extensions:Extension.Livetable Macro]] to display the existing questions and answers.
266
Guillaume Lerouge 56.1 267 The livetable component will give users the ability to easily list and filter through existing FAQ documents. The macro is made of 3 parts:
268
269 * The list of columns: for each entry, we will display the question, the date when it was created and a special column that lets users quickly modify entries
270 * The properties of each column: for each column, we will define how it should be displayed, whether it should link to the entry and whether it should be filterable
271 * The livetable options: those are options related to the display of the livetable (in this case we will to display a tag cloud and 10 rows by default)
272
273 Here is the resulting code:
274
275 {{code language="none"}}
276 {{velocity}}
Guillaume Lerouge 55.2 277 #set($columns = ["question", "doc.creationDate", "_actions"])
278 #set($columnsProperties = {
279 "question" : { "type" : "text", "link" : "view", "html" : "true", "sortable":true },
Guillaume Lerouge 56.1 280 "_actions" : {"actions": ["edit","delete"]}
Guillaume Lerouge 55.2 281 })
282 #set($options = {
283 "className":"FAQ.FAQClass",
284 "translationPrefix" : "faq.",
285 "tagCloud" : true,
286 "rowCount": 10
287 })
288 #livetable("faq" $columns $columnsProperties $options)
crowne 57.1 289 {{/velocity}}
Guillaume Lerouge 55.2 290 {{/code}}
291
Vincent Massol 93.1 292 * Copy this code and paste it as Wiki content (inside ##FAQ.WebHome##)
Guillaume Lerouge 56.1 293 * Click "Save and View"
294 * New FAQ entries will now be displayed on the page once you create them
295
Vincent Massol 93.1 296 The ##FAQ.WebHome## page should look similar to this:
Manuel Smeria 80.1 297
298 {{image reference="FAQsLivetable.png"/}}
299
Vincent Massol 93.1 300 Notice how there are some translation keys displayed inside the livetable. Let's create a translations document and change those keys to actual text:
Manuel Smeria 83.1 301
Vincent Massol 93.1 302 * Create a new page inside the FAQ space called Translations, i.e. at ##FAQ.Translations## (using the "+" button)
Manuel Smeria 80.1 303 * Edit it in Wiki mode and paste this content inside:(((
304 {{code language="none"}}
305 faq.question=Question
306 faq.doc.creationDate=Creation Date
307 faq._actions=Actions
Manuel Smeria 83.1 308 {{/code}}
309 )))
Vincent Massol 93.1 310 * Click "Save & View"
311 * Edit it again in Object mode and add a new ##XWiki.TranslationDocumentClass## object to mark the page as a page containing translations. Make sure to select the right scope. Using "Global" means the translations would be visible to all wikis (and it requires having Programming Rights!) and "Wiki" means it's visible to the current wiki only. Choose "Wiki" as the scope.
312 * Click "Save & View" again
Manuel Smeria 80.1 313
Vincent Massol 93.1 314 Now the ##FAQ.WebHome## page should look like this (notice the translations instead of the keys):
Manuel Smeria 80.1 315
316 {{image reference="FAQsLivetableWithTranslations.png"/}}
317
Guillaume Lerouge 55.2 318 === Using custom code ===
319
Guillaume Lerouge 42.1 320 You will need to write the following code:
Vincent Massol 1.1 321
Vincent Massol 93.2 322 * A XWQL query that will find all your FAQ documents. Check the [[Query API documentation>>extensions:Extension.Query Module]] to know more about it.
Vincent Massol 93.1 323 ** The XWQL query looks for all documents that have a ##FAQ.FAQClass## object other than the template
Guillaume Lerouge 42.1 324 ** If no document has been created yet, a warning message is displayed
Guillaume Delhumeau 59.2 325 * A piece of velocity code to display all those documents
Guillaume Lerouge 42.1 326 ** The velocity code loops in that list
327 ** For each item, the full document is loaded in memory so that values can be retrieved from it
328 ** For each document, the question is retrieved and displayed as a link towards the FAQ entry
Vincent Massol 1.1 329
Manuel Smeria 80.1 330 Here is the resulting code:
Vincent Massol 1.1 331
Silvia Macovei 48.1 332 {{code language="none"}}
Guillaume Lerouge 42.1 333 = Existing FAQ entries =
Vincent Massol 1.1 334
Guillaume Lerouge 42.1 335 {{velocity}}
Vincent Massol 93.1 336 #set($xwql = "from doc.object(FAQ.FAQClass) as faq where doc.fullName <> 'FAQ.FAQTemplate'")
337 #set($results = $services.query.xwql($xwql).execute())
Guillaume Lerouge 42.1 338 #if($results.empty)
Thibaut Camberlin 49.1 339 No FAQ has been created yet!
Guillaume Lerouge 42.1 340 #else
Thibaut Camberlin 49.1 341 #foreach ($item in $results)
342 #set($faq = $xwiki.getDocument($item))
Thibaut Camberlin 51.1 343 * [[${faq.display("question").replace("<p>", "").replace("</p>", "")}>>${item}]]
Thibaut Camberlin 49.1 344 #end
Guillaume Lerouge 42.1 345 #end
346 {{/velocity}}
Silvia Macovei 48.1 347 {{/code}}
Vincent Massol 1.1 348
Vincent Massol 93.1 349 * Copy this code and paste it as Wiki content inside ##FAQ.WebHome##
Guillaume Lerouge 42.1 350 * Click "Save and View"
351 * New FAQ entries will now be displayed on the page once you create them
Vincent Massol 1.1 352
Vincent Massol 93.1 353 The ##FAQ.WebHome## page should look similar to this:
Manuel Smeria 80.1 354
355 {{image reference="FAQsCustomCode.png"/}}
356
Silvia Macovei 48.2 357 == Creating new FAQ entries ==
Vincent Massol 1.1 358
Manuel Smeria 80.1 359 There are 2 ways for you to let your users create new FAQ entries:
Manuel Smeria 83.1 360
Manuel Smeria 80.1 361 1. Declare the FAQ as a template
362 1. Add a custom creation form
Anca Luca 14.1 363
Guillaume Lerouge 55.1 364 === Using a Template ===
365
Manuel Smeria 83.1 366 You will have to define a template provider [[as explained on this page>>extensions:Extension.Administration Application||anchor="HCreatethetemplateprovider"]]
Guillaume Lerouge 55.1 367
Alex Cotiugă 107.2 368 Go to your wiki's administration interface, in the "Templates" section (Administration -> Content -> Templates). Create a new template provider in the
Vincent Massol 94.1 369 ##FAQ## space and name it ##FAQTemplateProvider##
Guillaume Lerouge 55.1 370
371 You can then use the following values:
372
Vincent Massol 94.1 373 * Provider name: ##FAQ Template Provider##
374 * Template name: ##New FAQ entry##
375 * Template to use: ##FAQ.FAQTemplate##
Guillaume Lerouge 55.1 376
Vincent Massol 94.1 377 If you'd like, you can restrict FAQ entries so that they're created only in the ##FAQ## space. Once you're done, click "Save & View". Your template is now ready to be used! Users who click on the "Add >> Page" button will now have the option to create a new page using the FAQ template.
Guillaume Lerouge 55.1 378
379 === Custom creation form ===
380
381 If you choose this option, you will need to write some code to let your users create new FAQ entries. To do this, you will have to create a form in which the user can enter the name of the questions she wants to create. Once typed in, the form calls the same page to trigger the new document creation based on the parameters entered by the user:
382
Guillaume Lerouge 42.1 383 * The first part of the code checks whether the page has a parameter. If so:
384 ** The name of the document that will be created is computed
385 ** A check is done to verify the document doesn't exist yet
386 ** If everything's ok, the user is sent to the new document in inline edition mode
387 * The second part of the code is the actual FAQ creation form
Vincent Massol 94.1 388 ** It builds the name of the document to create it in the ##FAQ## space
Guillaume Lerouge 42.1 389 ** It sets the document parent as being the current document
390 ** It defines the template to use to create the new document
Vincent Massol 1.1 391
Silvia Macovei 48.1 392 {{code language="none"}}
Guillaume Lerouge 42.1 393 {{velocity}}
394 #if("$!request.docName" != '')
395 ## Request for creating a new instance
Clemens Robbenhaar 62.1 396 #set($docName = ${request.docName})
Guillaume Lerouge 47.1 397 #set($targetDocName = "${request.spaceName}.${docName}")
Clemens Robbenhaar 62.1 398 #if(!$xwiki.exists($targetDocName) && $xwiki.hasAccessLevel('edit', $xcontext.user, $targetDocName))
Clemens Robbenhaar 61.1 399 $response.sendRedirect($xwiki.getURL($targetDocName, 'inline', "template=${escapetool.url($request.template)}&parent=${escapetool.url($request.parent)}"))
Guillaume Lerouge 42.1 400 ## Stop processing, since we already sent a redirect.
401 #stop
402 #end
403 #end
Vincent Massol 1.1 404
Guillaume Lerouge 42.1 405 = Add a new question =
406
407 #if("$!targetDocName" != '' && $xwiki.exists($targetDocName))
408 {{warning}}The target document already exists. Please choose a different name, or [[view the existing document>>$targetDocName]]{{/warning}}
409 #elseif("$!targetDocName" != '')
410 {{warning}}You don't have permission to create that document{{/warning}}
411 #end
412
413 {{html}}
414 <form action="" id="newdoc" method="post">
415 <div>
416 <input type="hidden" name="parent" value="${doc.fullName}"/>
417 <input type="hidden" name="template" value="FAQ.FAQTemplate"/>
418 <input type="hidden" name="sheet" value="1"/>
419 <input type="hidden" name="spaceName" value="FAQ"/>
420 Document: <input type="text" name="docName" value="Enter your question here" class="withTip" size="50"/>
421 <span class="buttonwrapper"><input type="submit" value="Create this FAQ" class="button"/></span>
422 </div>
423 </form>
424 {{/html}}
425 {{/velocity}}
Silvia Macovei 48.1 426 {{/code}}
Vincent Massol 1.1 427
Vincent Massol 94.1 428 * Copy this code and paste it as Wiki content inside ##FAQ.WebHome##, below the code that's already there
Guillaume Lerouge 42.1 429 * Click "Save and View"
Vincent Massol 111.1 430 * A form to create new FAQ entries is now available on the page:(((
Manuel Smeria 80.1 431 {{image reference="FAQsWithForm.png"/}}
432 )))
Anca Luca 14.1 433
Silvia Macovei 48.2 434 = Test the Application =
jingbo 27.1 435
Manuel Smeria 80.1 436 Now let's just create a new document in our application to test it out.
Vincent Massol 94.1 437
Manuel Smeria 80.1 438 If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps:
Guillaume Lerouge 42.1 439
Vincent Massol 94.1 440 * Go to ##FAQ.WebHome##
Manuel Smeria 80.1 441 * Below the "Add a new question" header, enter a question (which will also be used as the document title) in the //Document// field
442 * Click //Create this FAQ//
Vincent Massol 111.1 443 * You can then enter your question in longer form using the //Question// field on the template, like this:(((
Manuel Smeria 80.1 444 {{image reference="FAQSheetEdit.PNG"/}}
Silvia Macovei 48.4 445 )))
Vincent Massol 111.1 446 * Click //Save & View// and then you will see the newly created document, like this:(((
Manuel Smeria 80.1 447 {{image reference="FAQSheetView.PNG"/}}
Silvia Macovei 48.4 448 )))
Vincent Massol 111.1 449 * Go back to the ##FAQ.WebHome## page (you can use the breadcrumbs) to see the list of existing questions(((
Manuel Smeria 80.1 450 {{image reference="FAQsWithEntry.png"/}}
451 )))
Guillaume Lerouge 42.1 452
Silvia Macovei 48.2 453 = Conclusion =
Vincent Massol 1.1 454
Manuel Smeria 80.1 455 This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
Vincent Massol 94.1 456
Manuel Smeria 80.1 457 You may also have learned a little bit about Velocity scripting in documents. You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.
Vincent Massol 1.1 458
459 As always, please take the time to make this document better for other users if you find ways that it can be improved as you read it for the first time.

Get Connected