Content Editor / Content View
The Content Editor application element is one of the basic controls. It is available as both an input and a view element. Markdown can be entered or displayed in the Content Editor. There is no limit on the length of the input. The Content Editor can only be linked to data fields of the " Text " data type.
In the image above, you can see the Content Editor in the browser. Entries can be saved by clicking the corresponding button, provided that a data field is linked to the editor.
The Content View element is used to view the data you have entered using the Content Editor. To do this, simply link it to the data field that's also linked to the Content Editor to display the Markdown text. No other settings need to be configured.
You can find the Content Editorand Content View elements in the Applications module under the Elements section. You can create a new element by dragging and dropping it from here onto the workspace.
For more information on creating elements, click here.
General information about Markdown can be found here:
The element's Properties dialog box opens automatically when the element is created. You can open the Properties dialog box for an existing element by double-clicking the element on the workspace, selecting "Properties" from the context menu, or choosing "Edit / Properties" from the main menu when the element is selected on the workspace.
General
Title
Enter the title of the content editor here. For more information on multilingual titles and the use of language constants, click here.
Show Titles Under Control
This setting causes the title to appear in the input field when the page is displayed in the browser.
Input Required
With this setting, an input field becomes a required field.
Read-only
This setting prevents input.
Show View Selector
This option displays the toggle between "Markdown" and "WYSIWYG" in the footer of the content editor.
Configuration
Starting with Intrexx version 12.0.1
This page is used to configure the editor's toolbar. There are various buttons available that can be added to the web editor.
Available / Selected Buttons
In the "Available Buttons" column, you'll find all the buttons you can select in the editor. All buttons included in the "Selected Buttons" column are also visible in the editor. The dotted line is used to visually group buttons together. This will help you keep track of things in the editor. The solid line is used to create an additional toolbar below the previous one.
Move to the right / left
The selected button will be moved to the left or right column.
Default Configuration
Clicking this button will reset the settings to their default configuration.
Delete Configuration
Moves all items from the "Selected Buttons" column back to the "Available Buttons" column
Move up / down
Changes the order of the buttons in the editor. The rule is: the higher up a button is in the list, the further to the left it will appear in the editor's toolbar. Causes the status bar at the bottom of the editor to display which HTML element is currently being edited, depending on the cursor's position.
"Content View" control type in view tables
If you include a data field linked to the Content Editor as a column in a view table, you can select the "Content View" control type there. You can find more information about control types here.
Create Your Own Default Configurations
To create your own default configuration, you must create an XML file in the portal directory "internal/cfg/htmleditor/markdown." The format for this can be adapted from the existing "ixdefault.xml" file.
You can then easily select your own default configuration using the corresponding menu in the configuration dialog.
GIPHY
To use the GIPHY picker or GIPHY search in the Content Editor, drag the "Insert GIPHY" entry from the "Available Buttons" list to the "Selected Buttons" list.
Why is a GIPHY API key required?
For data protection reasons, a valid API key is required for GIPHY; you will be notified of this with a corresponding message.
There are two different types of API keys: the so-called beta key and the production key.
The beta key is automatically generated after you create an account on GIPHY Dev and set up a new app. The beta key provides limited access to GIPHY's servers and is intended to test access.
In addition, a video can be created showing the application in which the key is used. This video is required to request a production key. The production key grants full access to GIPHY's servers and is intended for actual use.
Where do I create my GIPHY account?
You can create a new GIPHY account at https://developers.giphy.com/. Click "Create Account" here.
How do I generate my beta key?
Once your account has been created and you've logged in, click "Create an App." In the window that appears next, you can specify the scope of the key. We recommend selecting "API" here.
After making your selection, click "Next Step."
Enter the app's name and a description here. Then click "Create App."
Next, accept the GIPHY API Terms of Service to complete the process. The beta key for your app is now being created and activated.
Where do I enter my GIPHY key in Intrexx?
Enter your key in the "Integration" module under "External API Keys." To do this, select "External API Keys / Add New API Key" from the main menu.
How do I generate my production key?
When you're on the GIPHY dashboard (https://developers.giphy.com/dashboard/), all the apps you've created are displayed along with their corresponding beta keys. For each app, you'll find the "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 how to use the key. You must also upload a video showing your GIPHY search in action using the beta key. The disclaimer can be displayed in the GIPHY search.
Once you have entered all the information, you can submit the form. GIPHY will then let you know how long it will take to review your request and activate the production key.