Content Editor / Content View

The "Content Editor" element is one of the basic controls. It exists as an input element and as a view element. You can enter or display markdown in the Content Editor. The input length is not limited. The Content Editor can only be connected to data fields with the data type "Text".

In the image above, you can see the Content Editor in the browser. Inputs can be saved with a corresponding button, provided that a data field is connected to the Editor.

Use the "Content View" element to view the data you entered in the Content Editor. To display the markdown text, simply link the view element to the field that is also linked to the Content Editor. There are no further settings to update.

The "Content Editor" and "Content View" elements can be found in the "Applications" module in the "Elements" area. A new element can be created by dragging & dropping it from here and positioning it in the workspace.

More information on creating elements can be found here.

The element properties dialog box opens automatically when a new element is created. The properties dialog of an existing element can be opened by double-clicking the element on the workspace, via the "Properties" context menu, or via the "Edit / Properties" main menu, if the element is selected in the workspace.

General

Title

Enter the title of the Content Editor here. Further information on multilingual titles and the use of language constants can be found here.

Display title in control

This setting means the title will be displayed in the edit field when it is viewed in the browser.

Input required

This setting makes the edit field into a mandatory field.

Write-protected

The text area cannot be edited if this setting is active.

Show view toggle

This option displays the toggle between "Markdown" and "WYSIWYG" in the footer of the Content Editor.

Configuration

From Intrexx version 12.0.1

On this page, the toolbar of the Editor is configured. There are several buttons available that can be added to the Editor on the web.

Available / Selected buttons

Here, you will find all buttons that you can add to the Editor. If you want to add an additional button, highlight it in the column and move it with the arrow button to the "Selected buttons" column. With the dotted line, buttons will be visually combined into groups. In this way, you will get a clear overview in the Editor. The solid line will be used to create an additional icon bar below a previous one.

Move right / Move left

The selected field is moved to the right/left column, respectively.

standard configuration

Clicking this button resets the settings to the default configuration.

Delete configuration

Moves all elements from the "Selected buttons" column back to the "Available buttons" column

Move up / Move down

These define the order of the buttons in the editor. The following applies here: The higher the button is in the list, the further to the left it will be shown in the editor toolbar. Displays which HTML element is currently being edited in the status bar at the bottom of the editor, depending on the position of the cursor.

Control type "Content view" in view tables

If you include a data field that is linked to the Content Editor as a column in a view table, you can select the "Content view" control type there. Further information on control types can be found here.

Create your own default configurations

To create your own default configuration, an XML file must be created in the portal directory "internal/cfg/htmleditor/markdown". The format for this can be adapted from the existing "ixdefault.xml".

Your own default configuration can then be easily selected via the corresponding menu in the configuration dialog.

GIPHY

To use the GIPHY picker or search in the Content Editor, move the entry "Insert Giphy" from the "Available Buttons" list to the "Selected Buttons" list.

Why do I need an API key for GIPHY?

For data protection reasons, a valid API key is required for GIPHY. You will receive a message notifying you of this.

There are two different types of API key: the beta key and the production key.

The beta key is generated automatically after an account is created at GIPHY Dev and a new app has been created. The beta key only has limited access to GIPHY's servers and is used to test access.

In addition, a video of the application in which the key is used can be created. This video is required to request a production key. The production key grants full access to GIPHY's servers and is to be used for the actual deployment.

Where do I create my GIPHY account?

You can create a new GIPHY account at https://developers.giphy.com/. Click on "Create Account" here.

How do I create my beta key?

Once the account is created and you have logged in, click "Create an App". In the next window, you can define the scope of the key. We recommend the option "API" here.

After you have selected an option, click on "Next Step".

Enter the name of the app and a description here. Then click on "Create App".

Finally, confirm the GIPHY API terms and conditions to complete the process. The beta key for your app is now created and activated.

Where do I store my GIPHY key in Intrexx?

Enter your key in the "Integration" module under "External API keys". To do this, select the main menu item "External API keys / Add new API key".

How do I create my Production Key?

When you are on the GIPHY dashboard (https://developers.giphy.com/dashboard/), all the apps created are displayed with their associated beta keys. Each app contains an "Upgrade to Production" button.

You will then be taken to a page where you will need to enter more specific information about the app and the use of the key. A video must also be posted showing your GIPHY search in action using the beta key. The disclaimer can be shown in the GIPHY search.

If you have entered all the information, you can submit the form. GIPHY will then tell you how long it will take to review your request and activate the production key.