Wiki source code of Einstellungen
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | == Default settings == | ||
| 2 | |||
| 3 | {{lightbox image="sixCMS_1.png" width="400"/}} | ||
| 4 | |||
| 5 | |||
| 6 | In the plug-in, under the menu item //Configuration// (section //Set default//), the default values for the plug-in can be set. The values set here are available later when configuring the container/form, but can be overwritten there. | ||
| 7 | |||
| 8 | The forms created in the {{designer case="dat"/}} use some javascript frameworks such as jQuery, as well as partly also user-defined CSS files. If jQuery has already been included in the project, FORMCYCLE does not need to load and include jQuery additionally. The values (true/false) can be used to set which scripts should be loaded or not. The situation is different for the CSS files. The CSS files specified here are loaded when the {{designer case="gen"/}} is called up and are then available in the CSS area of the elements as CSS classes. | ||
| 9 | |||
| 10 | * {{litem title="base_url"}}Here the URL to the FORMCYCLE server must be stored. It should be noted that the SixCMS **server** has access to the FORMCYCLE server via the specified base_url!{{/litem}} | ||
| 11 | |||
| 12 | * {{litem title="alternative_url"}}Use this parameter if the URL for delivering the forms is different from the URL of the FORMCYCLE master server. This is necessary, for example, when using a frontend server. In this case, enter the URL of the frontend server. {{/litem}} | ||
| 13 | |||
| 14 | * {{litem title="render"}}There are 3 different ways to render the form: | ||
| 15 | |||
| 16 | 1. inline\\ The form is rendered as DIV content in the page (see figure access 1). | ||
| 17 | 1. iFrame\\ The form is provided as an iFrame in the page (see figure access 2). | ||
| 18 | 1. ajax\\ The form is loaded into the page (DIV) via an ajax request (see figure access 2). | ||
| 19 | {{/litem}} | ||
| 20 | * {{litem title="use_css"}}Here one or more CSS files can be specified. Please make sure that these CSS files are also included on the page later on.{{/litem}} | ||
| 21 | * {{litem title="use_jq"}}If the value is //true//, the jQuery framework (jquery-xxx.min.js) will be loaded by the form.{{/litem}} | ||
| 22 | * {{litem title="use_ui"}}If you have included jQuery UI components in the form (e.g. datepicker ...) the value must be //true// or the corresponding file must be defined in SiXCMS.{{/litem}} | ||
| 23 | |||
| 24 | |||
| 25 | {{lightbox image="six_cms_net_1.png" width="300" title="Abbildung: Access 1"/}}\\Figure: access 1 | ||
| 26 | |||
| 27 | {{lightbox image="six_cms_net_2.png" width="300" title="Abbildung: Access 2"/}}\\Figure: access 2 |