Commit b132fb5a authored by Marc Egger's avatar Marc Egger

correct sphinx warnings

parent 2e6230fe
......@@ -1467,7 +1467,7 @@ Action
only the STORE SIP supports the feature 'wipe'. This is useful to suppress any repeating events by using the browser history.
The following example will send a mail only the first when it is called with a given SIP::
10.sql = SELECT '...' AS _sendmail FROM Person AS p WHERE '{{action:S::w}}'='send' AND p.id={{pId:S}}
10.sql = SELECT '...' AS _sendmail FROM Person AS p WHERE '{{action:S::w}}'='send' AND p.id={{pId:S}}
......@@ -1492,7 +1492,7 @@ If a value violates the sanitize class, the following actions are possible:
* 'e' - Instead of the value an empty string will be set as content.
* '0' - Instead of the value the string '0' will be set as content.
* 'custom text ...' - Instead of the value, the custom text will be set as content. If the text contains a ':', that one
needs to be escaped by \\ . Check `variable-escape`_ qualifier 'C' to let QFQ do the colon escaping.
needs to be escaped by \\ . Check `variable-escape`_ qualifier 'C' to let QFQ do the colon escaping.
.. _`sql-variables`:
......@@ -1963,7 +1963,7 @@ Store: *VARS* - V
+=========================+============================================================================================================================================+
| random | Random string with length of 32 alphanum chars (lower & upper case). This is variable is always filled. |
+-------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
| slaveId | see `slaveId`_ |
| slaveId | see `slave-id`_ |
+-------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
| allRequiredGiven | Form save - Set during check of all required FE. If every *required* FE is given: *1*. Else: *0*. If there is no required FE: *1*. |
| | Even with `formModeGlobal` = `requiredOff` | `requiredOffButMark` the variable will be set. |
......@@ -2845,9 +2845,9 @@ Code: ``SELECT 'p:{{pageAlias}}&form=person&r=1&formModeGlobal=readquiredOff|s|t
* A form has one or more FormElement with 'fe.type=required'.
* Opening the form with `formModeGlobal=requiredOff` will allow the user to save the form, even if not all
FE.type=required elements are given. This can be called 'draft' mode.
FE.type=required elements are given. This can be called 'draft' mode.
* Opening the form without `formModeGlobal` (that's the default), forces the user to fill out
all FE.type=required fields. This can be called 'final submit' mode.
all FE.type=required fields. This can be called 'final submit' mode.
*Draft Mode 2*
......@@ -2855,7 +2855,7 @@ Code: ``SELECT 'p:{{pageAlias}}&form=person&r=1&formModeGlobal=readquiredOff|s|t
* A form has one or more FormElement with 'fe.type=required'.
* Calling the form with `formModeGlobal=requiredOff` will allow the user to save the form, even if not all
FE.type=required elements are given.
FE.type=required elements are given.
* Define an FE-Action 'afterSave', and do some action on `{{allRequiredGiven:V0}}` like::
{{UPDATE <table> SET dataValid={{allRequiredGiven:V0}} WHERE id={{id:R}} }}
......@@ -3068,7 +3068,7 @@ Fields:
+---------------------+-----------------------------+-----------------------------------------------------------------------------------------------------+
|Size | string | Depends on the FormElement type. E.g. visible length (and height) of input element `input-text`_ . |
| | | Might be omitted, depending on the chosen form layout. |
| | | Format: <width>[,<(min) height>[,<max height]] (in characters). |
| | | Format: <width>[,<(min) height>[,<max height]] (in characters). |
+---------------------+-----------------------------+-----------------------------------------------------------------------------------------------------+
|BS Label Columns | string | Number of bootstrap grid columns. By default empty, value inherits from the form. |
| | | _`field-bsLabelColumns`. See `bs-custom-field-width`_ |
......@@ -4724,7 +4724,7 @@ FormElement:
Advanced
^^^^^^^^
To handle foreign records (insert/update/delete), use the slaveId_ concept.
To handle foreign records (insert/update/delete), use the `slave-id`_ concept.
Typically the `FormElement.name` is not a column of the primary table.
......@@ -8061,7 +8061,7 @@ The *tablesorter* options:
* To preselect a view, append a HTML anker to the current URL. Get the anker by selecting the view and copy it from the
browser address bar. Example::
https://localhost/index.php?id=person#allperson=public:email
https://localhost/index.php?id=person#allperson=public:email
* 'allperson' is the '<uniqueName>' of the `tablesorter-view-saver` command.
* 'public' means the view is tagged as 'public' visible.
......
......@@ -398,7 +398,7 @@ Notes
* Use the CSS class 'qfq-sticky' in `<thead>` to make a table header 'sticky' - on long pages such tables headers are always
visible.
* The page with the list of all forms: a new best practice report includes useful statistics `Form-Editor-Usage`_ - best
* The page with the list of all forms: a new best practice report includes useful statistics :ref:`Form-Editor-Usage` - best
is to replace the old code.
Features
......@@ -407,7 +407,7 @@ Features
* #9203 / Pin the header of table (CCS 'sticky'), to make it always visible even if the page scrolls down.
* #9172 / AutoCron: new colum 'autoGenerated', 'xId'
* #9089 / Move Stored Procedure to SECURITY=INVOKER
* Manual.rst: Best practice `Form-Editor-Usage`_
* Manual.rst: Best practice :ref:`Form-Editor-Usage`
* Reduce BS legend.font-size from 21 to 17.
* Change doc of tablesorter to use 'sorter-false' as class.
......
......@@ -7,4 +7,4 @@ Sitemap
=======
.. template 'sitemap.html' will insert the toctree as a sitemap here
below normal contents
below normal contents
......@@ -408,7 +408,7 @@ already. The interesting part is the part below the SQL statement. Here a little
* tail = ... : This line is being executed as soon as the SQL stement is fininshed and all the data has been displayed on the screen.
* rbeg = ... : Rbeg means row beginn. At every row beginn a <tr> is being placed.
* rend is row end, fbeg is field beginn and fend is field end. So whenever a field or a row starts or ends, one of the HTML statements
are going to be executed.
are going to be executed.
Details: https://docs.typo3.org/typo3cms/drafts/github/T3DocumentationStarter/Public-Info-053/Manual.html#qfq-keywords-bodytext
......@@ -449,9 +449,9 @@ This SQL statement is a little more complicated, but most of the content didn't
of the new lines of code:
- *form = {{form}}*: this line tells the website, that on that specific page we want to create a button, which opens up a Form.
If this line would miss, we could't open the form. If you don't know what I mean, just delete the first line of code, save
the QFQ element, go to the webpage and try to open the Form with the little button at the left. You will see, the button is
not working.
If this line would miss, we could't open the form. If you don't know what I mean, just delete the first line of code, save
the QFQ element, go to the webpage and try to open the Form with the little button at the left. You will see, the button is
not working.
Details: https://docs.typo3.org/typo3cms/drafts/github/T3DocumentationStarter/Public-Info-053/Manual.html#qfq-keywords-bodytext
......@@ -466,13 +466,13 @@ Details: https://docs.typo3.org/typo3cms/drafts/github/T3DocumentationStarter/Pu
- *&form=Application&*: This line opens up the Form Application. Whenever you want to create a link, where a specific Form is
going to be opened, you have to specify which Form you want to open up, with this notation.
- *AS _Pagee: This part tells QFQ that we want to create a button with an edit symbol on it.
- *AS _Pagee*: This part tells QFQ that we want to create a button with an edit symbol on it.
- *(SELECT 1) AS fake WHERE '{{form:SE}}'=''*: This statement is at the end of the SQL Statement and looks complicated. What it does:
If this line of code wouldn't be there you would have the following problem. When you open up the link, you want to see only the Form,
and not the list of all other Applicants under the form. This line of code does exactely that. It does hide the list of
people as soon as you open up the form.
If it is not clear what is meant by that I'll show you a few screenshots to illustrate the problem:
If this line of code wouldn't be there you would have the following problem. When you open up the link, you want to see only the Form,
and not the list of all other Applicants under the form. This line of code does exactely that. It does hide the list of
people as soon as you open up the form.
If it is not clear what is meant by that I'll show you a few screenshots to illustrate the problem:
If you would delete the following statement: *(SELECT 1) AS fake WHERE '{{form:SE}}'=''*, this would happen:
......@@ -629,7 +629,7 @@ Here a working query if yours is not working: ::
Job Advertisements
=================
==================
Until now it is only possible to apply to a job and to add reviewers, which evaluate all the applications. But we
can't put any job advertisements online. So that's our next task. We want to create three things:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment