Follow us: News Artisteer and Themler Unite! July 29, 2015. It's been a while since we had significant news to announce and we apologize for the long delay. Download TinyMCE for free, the most advanced features designed to simplify website content creation. Joomla i About the Tutorial Joomla is an open source Content Management System (CMS), which is used to build websites and online applications. It is free and.

1. Tinymce Wysiwyg Editor Joomla Download Templates Free

Using Url Parameter to set default Values in Forms - since Visforms 3.2.0 Since Visforms 3.2.0 it is possible to set default values for form fields through Url parameters. This allows you to set individual default values dynamically during run time. The feature was implemented in Visforms 3.2.0.

As Url parameters are easy to access, this is a feature which might invite bad users to try to manipulate your forms. We have countered that abuse with special security measures. Allow the use of Url parameters for fields As default the use of Url parameters is disabled. This is a security measure.

You can enable the use of Url parameters individually for every field in the field configuration, tab 'advanced'. Format of Url parameters You can add as many Url parameters to an Url as you need. Each parameter consists of a Parametername=Parametervalue pair. The first parameter which is attached to an Url has to be preceded with a question mark (?). Parmetername/Parametervalue pairs are concatenated with an ampersand (&).

As Parametername you have to use the field 'name', which you entered in the field configuration. Heads Up: Since Visforms 3.8.x you have to prefix the name with an additional context. If you publish the form via a menu item, the context is 'formN', where N is the id of the form.If you have for example a field named 'field1' in the form with id 1 the proper name of the Url parameter in Visforms prior to 3.8 is field 1 in Visforms since 3.8 is form1field1. If the form is published via a module the context, which you have to use since Visforms 3.8 is 'modvisformN'.

You have to replace N here with the module id! The Parametervalue is a string. You can only use strings as Parametervalue, which is also a security feature. For input fields (text, date etc.) the Parametervalue can be an arbitrary string, which you want to be used as default value. If you are dealing with a select, a radio, a checkbox group or a checkbox, which comes with their specific option lists, you have to use a valid option value as Parametervalue. Exceptions for selects and checkbox groups You have to add to the Parametername when you are setting Url parameters for selects or checkbox groups.

Also it is possible to set more than one default option for those field types by adding multiple Url parameters. As an example. If you have a select with the name 'select' and the three options s1 auswahl1, s2 auswahl2, s3 auswahl3 and you want the first and second option to be preselected, you would add the following string to the Url: &select=s1&select=s2 respectively?select=s1&select=s2, if it's the first parameters attached to the URL. Which value is used as default in the form? If a form is displayed for the first time Visforms checks, if there is a default value set in the field configuration and attaches that value to the field.

After that Visforms checks if Url parameters are enabled for the field and if yes, whether there is an Url parameter set for this field. If so, this value will be used as default. If a form has already be submitted but is displayed again (for example because the php validation failed), the user inputs are used as default values. Where do I get the Url from?

You have to create links with Url parameters manually. It is not possible to create a menu item link to a form and attach Url parameters in the menu item configuration. But you can use the forms Url as a base Url to wich you add your Url params. Use Case Example You manage events. You have a page (article) for each event, with event inforamtion and a link to a registration form.

You want to use only one single registration form regardless of the event. To make registration as comfortable as possible you want event specific fields in the form, like event date and event name, to be set properly by default. Using Url parameters is an easy way to achieve this. In addition to all the other form fields, you have to create the event specific fields in the form (a date field for event date, a select for the event names with one option for each event). Enable the use of Url params for the date field and the select. Create a menu item of type Visforms that links to the form and use the Url of that menu item as base for the link to the registration form which you provide in your event article (and which you have to enter manually).

For each event article add date and the select as Url parameters with the event specific information as values. When a user clicks on the link the form will open with the event date and event name option preselected properly. Formular Layout Configuration - since Visforms 3.2.0 Control of individual form layout through configuration has been improved significantly in Visforms 3.2.0. Form Layouts One of the big new features in Visforms 3.2.0 is the introduction of two new form layouts, so that you can choose now between three form layouts.

Since version 3 has focused on creating HTML Code, which works with the Bootstrap framework, it just felt right, to create Bootstrap layouts for Visforms as well. Bootstrap is a front-end framework which helps you, develop frontend layouts fast and easily. You just have to write the right HTML Code structure with the appropriate class attributes. In addition to the 'old' Visforms Default Layout, Visforms provides you now with a form Layout that implements the Bootstrap 'default form styles' ( Default Bootstrap Layout) and ein Layout, that implements the Bootstrap 'horizontal forms' ( Bootstrap Horizontal Layout). The Bootstrap Inline Form layout only suits specific small forms and was therefore not implemented. You can select the form layout in the form configuration, tab 'advanced'.

As a matter of fact, not all Joomla! 3 templates are Bootstrap templates. That is why you also have an option, that allows you to include the original Bootstrap form CSS. Only enable the option 'Load Bootstrap form CSS', if you do not use a Bootstrap template. If you use a Bootstrap template on your website, the template will deliver the required CSS.

Click preview to enlarge the image. Default Visforms Layout Label and control are aligned in one line, labels are aligned to the left. Default Bootstrap Layout Label is positioned above the control. Horizontal Bootstrap Layout Label and control are aligned in one line, label is align to the right.

Hide Label and the use of placeholders All modern browsers have implemented so called placeholders, which allow you to display a placeholder text inside an input. In contrast to a default value, which will be submitted with the form, a placeholder is just an informative text, that vanishes, either when you click into the input or when you start to enter characters (depending on which browser you use). Since Visforms 3.2.0 you can add a placeholder to all text inputs in the field configuration. Further on you can hide the field label for those fields through configuration. If you have not entered a placeholder text, the field label will be used as placeholder in this case, to make sure, that the user knows what sort of input they are required to enter. Please note, that the display of a 'tool tip text' depends on a field label, because the tool tip is displayed when the user hovers the field label text. When you hide the field label then there is no 'tool tip text', too, even if you have entered a 'tool tip text' in the field configuration.

The Internet Explorer only supports placeholders since version 10. That is why we have added some Javascript code, that makes sure, placeholders can be used with browsers, that do not support them genuinely, as well. Mandatory fields and the use of. It's a common feature to use a. in forms to indicate that a form field is mandatory and the user is required to provide a value. In Visforms prior to version 3.2.0 the position of the.

was hard coded, to the right side of the field label. There are different opinions on whether or not the.

should be displayed at all and on where to put it, if it is displayed. Visforms since 3.2.0 therefore comes with a new option, that allows you to hide the.

You can find the option in the form configuration's tab 'advanced'. Further on the. is no longer part of the HTML Code itself, but is now generated with CSS, which allows you to determine it's position and it's layout much more flexible with your custom CSS. Position of 'Custom Text' Since Visforms 3.2.0 there is a field option in field configuration's tab 'advanced' which enables you to choose the position of the fields 'custom text' more flexible.

You can choose between three positions:. Above the Label.

Above the input. At the bottom of the input with the position of the first and second option having a visibly different result only in the Default Bootstrap Layout, because label an input are aligned in one line for the other two layouts. Visforms Events for Plugin Development - since Visforms 3.2.0 Some feature request, which we have received in the past, were about individuel business processes. These are features like individual submit handler or specific tasks to be performed on the form data after the form was successfully send, like exporting the submitted data into a text file on the server which is thus continually updated.

Sensibly, such features cannot be implemented in the Visforms core code. But with the help of the event system which was introduced in Visforms 3.2.0, it is possible to develop custom plugins and thus to add custom code to Visforms easily. An other advantage of the usage of plugins is, that they are not affected by Visforms updates.

If you are in need of such an individual feature we were pleased to develop the plugin for you. Just send us a description of what you need and we will make you an offer. Events supported by Visforms. onVisformsBeforeHtmlPrepare.

onVisformsAfterHtmlPrepare. onVisformsAfterCustomtextPrepare.

onVisformsFormPrepare. onVisformsEditFormPrepare. onVisformsBeforeFormSave. onVisformsAfterFormSave. onVisformsEmailPrepare onVisformsBeforeHtmlPrepare The HTML code that renders a form field, depending on the field type, the field settings and the forms settings, is created completely inside the Visforms code, now, as a string which is just inserted into the form view. The onVisformsBeforeHtmlPrepare event can be used to change field setting before the HTML string is created.

Parameters. String $context: comvisforms.field. Object $field: Reference to the field object. String $layout: visforms, btdefault, bthorizontal or multicolumn onVisformsAfterHtmlPrepare The onVisformsAfterHtmlPrepare event is triggerd after the HTML code string is generated and can be used to post process the HTML string. Parameters.

String $context: comvisforms.field. Object $field: Reference to the field object.

String $html: Reference to the HTML string. String $layout: visforms, btdefault, bthorizontal or multicolumn onVisformsAfterCustomtextPrepare The onVisformsAfterCustomtextPrepare event is triggerd after the HTML code, that renders the 'Custom Text' of a field is created. It can be used to post process the HTML string. Parameters. String $context: comvisforms.field.

String $html: Reference to the HTML string. String $layout: visforms, btdefault, bthorizontal or multicolumn onVisformsFormPrepare The onVisformsFormPrepare event is triggered from inside the form view, before the form is rendered. You can use it to insert individual Javascript code into the form or to adapt form options and to modify the form layout. Parameters. String $context: comvisforms.form (Form is displayed with menu item) or modvisforms.form (Formis displayed with module) oder plgvfformview.form (Form is displayed with Content Plugin Form View ).

Object $visforms: Reference to the form object. Object $menuparams: Reference to the menu params onVisformsEditFormPrepare The onVisformsFormPrepare event is triggered from inside the form view, before the form is rendered. You can use it to insert individual Javascript code into the form or to adapt form options and to modify the form layout. Parameters. String $context: comvisforms.form. Object $visforms: Reference to the form object.

Object $menuparams: Reference to the menu params onVisformsBeforeFormSave The onVisformsBeforeFormSave event is triggered after the form is submitted and the user inputs are validated and before user inputs are stored in the database. Parameters. String $context: comvisforms.form.

Object $visforms: Reference to the form object. Array $fields: Reference to the fields objects onVisformsAfterFormSave The onVisformsAfterFormSave event is triggered after user inputs are stored in the database. Parameters. String $context: comvisforms.form. Object $visforms: Reference to the form object. Array $fields: Reference to the fields objects onVisformsEmailPrepare The onVisformsEmailPrepare event is triggered with differing contexts when Visforms prepares to send the receipt mail and the result mail. It can be used to perform individual tasks on the mails before they are finally send.

For example to attach files to the mails. Parameters. String $context: comvisforms.form.receiptmail or comvisforms.form.resultmail. Object $mail: Reference to the mailer object. Object $visforms: Reference to the form object. Using User Inputs in Result Text and E-Mails This feature was added in Visforms 3.2.0 for Visforms allows you to add placeholders to the result mail text, the receipt mail text and to the result text, which are replaced with the submitted user input before the mail is send or the message is displayed.

This is a powerful feature, because. you can highly individualize the texts according to your requirements. you can customize the layout of the e-mails individually including the display ot the sumitted data Basics We use textareas to enter long texts (like the receipt mail text). To allow you to give more or less format to this texts without (much) knowledge of HTML, Joomla! Provides you with a so called WYSIWYG (what you see is what you get) editor. By default this WYSIWYG editor is TinyMCE.

Editors are Joomla! Plugins of the plugin type 'editor', which can be enable or disable in the administrator panels Plugin Manager. In addition to the TinyMCE editor plugin Joomla! Has two more default editors plugins, the Code Mirror and the None. Other editors are available as third party extensions.

Tinymce Wysiwyg Editor Joomla Download Templates Free

For your Joomla! Installation to work properly you must always enable at least one editor plugin! But you can enable as many editor plugins as you like. You set a default editor in the global configuration of your Joomla! According to your settings in the user mananger options, users may be able to choose a different editor as their own default editor. If you do not want to use a WYSIWYG editor you have to enable the 'None' editor and choose it as default.

Further on Joomla! Provides you with so called editor buttons which are displayed below the textarea/editor field. These are for example buttons like the 'Article'-Button or the 'Image'-Button which you can use, to easily insert images or links to articles into the editor field, by selecting the item in a popup window with the mouse.

Editor buttons are Joomla! They are of the type 'editor-xtd'. Usually the buttons work fine with all editors, but when you have more than one editor field at a time, the buttons only work as expected with the TinyMCE editor but not with Code Mirror or None. You have to bear this basics in mind to understand the limitations of using user inputs in texts. Please make sure that the plugin 'Button - Visformfields' of type 'Editor-xtd' is enabled. Inserting Placeholder Visforms comes with a custom editor button Visformfields for the editor for the Receipt Mail Text, for the editor for the Result Mail Text and for the editor for the Result Text in the Edit form view that works similiar to the Article or Image button.

A click on that button opens a popup with a list of all form fields that can be used as placeholders. Just click on the form field title and the placeholder is inserted a the cursor position in the editor field. The edit form view contains several editor fields. As we have learned above in this case editor buttons only work properly with the TinyMCE editor. Therefore Visforms tries to enforce the use of the TinyMCE editor in the edit form view. If the TinyMCE editor plugin is disable on your Joomla!

Installation for any reason, the editor buttons will not be displayed! Insert Placeholder manually If you want to use a user input in receipt mail or result message and have disable the TinyMCE plugin for any reason, you can add the placeholder manually. Just enter the string FIELDNAME, where 'FIELDNAME' is the name of the field you want to be replaced. You must replace all lower case characters in the field name with upper case characters!

Please note, that fields of type Submit Button, Image Submit Button, Reset Button and Field Separator can not be used as placeholders. If you misstype a fieldname or use one of the former field types, the placeholder is just removed. Please not, if a form field has no user input, which may happen for field which are not required, then the placeholder is just removed. So consider carefully which fields you have to set as required. Make E-Mails Look Pretty You can create pretty individual e-mails with this feature, for example the receipt mail.

Disable the 'Include Data' Option for receipt mails. Create an individual list to display the user inputs anywhere inside the receipt mail text, using placeholders. So you can determine the field order.

You can omit specific fields if you like. You can create individual labels. You can use the editor to format the output as list, as table or just as you would like it to look like Note: If you have enabled the Show a download link option for the receipt mail the placeholder for fields of type upload will be replaced by a download link otherwise by the original name of the uploaded file. Placeholders in Text Result This feature works similar for the Result Text except for fields of type upload where the placeholder will always be replaced with the original name of the uploaded file.

Placehoders in Mail Subjects You can use placehoders in the 'Subject' Options of the mails as well. You have to enter the placeholder manually, there, as described above. Text HTML offers two different field types for texts the textarea and the input that comes with different types like text, email, password. The difference between these both HTML field types is, that the input creates a smaller single line input box, while the textarea creates a bigger box meant for longer texts, like messages. While you cannot force an input to become bigger than a single line, width and hight of a textarea can be set with the HTML attributes 'cols' and 'rows' and textareas feature by default a height of more than one row. In addition the textarea will show scroll bars, when the text, entered into it, takes more lines than the original height of the textarea provides. Please note that for reasons of simpler form validation each input type is a separate field type in Visforms.