-
-
-
- Building blocks of the data model
- Basic concepts
- Classes
- Key fields
- Local lookup lists
- Fields and data types
- Defining the columns of a table
- Relations between classes
- Global lookup lists
- Filters
- Universal connected classes
- Deleting foreign records
- Class inheritance
- Storage of personal data on test and develop environment (scrambling)
-
- User interface versions
- Building blocks for user interface design
- Adding styles with a css
- Surrounding page
- Changing snippets
- Creating a custom login page (pre 3.4)
- Creating a custom login page
- Using velocity templates within the blueprint
- Create your own web pages
- HTML delivery requirements
- How to customize system mails
-
- Resource files
- Velocity - How does it work?
- Quick Velocity Tutorial
- Debugging velocity scripts
- Velocity Command Reference
- Script Editor Tutorial
- Using velocity for calculations
- Using predefined forms in a html design
- Velocity forms
- Data field identifiers
- Macros and methods
- Velocity library
- Velocity: using the #macro command
- velocity and xml
- Using AJAX in your velocity scripts
-
-
- Argon2 password conversion
- Introduction to security
- Secure development
- Security certification
- Security Exam
- Field properties concerning security
- Developing user groups securely
- Security considerations for user interface
- Secure file organization
- Securely using the request
- Cross Site Scripting (XSS)
- Other options concerning secure development
- Security analysis
- Secure deployment
- Secure application management
- Scrambling of testdata
- Anonymization of personal data
- Using robots.txt
- Permission settings
- Security measures
- Data encryption
-
- Search Engine Optimization
- OTP
- User Interface migration guide
- User account management
- Instructies voor implementatie van visueel editen van nieuwsbrieven
- Login as another user
- Support
- More information about moving to User Interface Version 4.0
- Standaard page layout
- Sections moved to layout
- Aanpassingen in release 2024-7
- Media library
- Aanpassingen in release 2024-10
- Analytics and Matomo
- Registration forms
- How to change names of classes and fields?
- Responsible Disclosure Policy
- How to upload a blob in Velocity?
- Aanpassingen in release 2024-2
- Instances
- Componenten in onze technologie
- Google Analytics
- Street and City helper (postcodecheck)
- Responsible disclosure-beleid
- Postcode check service (straat en huisnummer) kosten
- Expressions
- Regular Expression Reference
-
Configure the HTML editor
The HTML editor can be configured as you need. You need a field with Data type: memo and HTML: HTML editor. Now you can configure the HTML editor configuration. The configuration is done in JSON format. The options you configure will overwrite the corresponding options in the default configuration.
Below is an example configuration.
- First we add
content_css. This allows us to add styling to the HTML in the editor, so it will correspond to the read-only HTML as we present it on the web page. - We set the
menubar(topmost bar) to false, so it will not show. - The
toolbargets a specific configuration. With limited options we want to present to the user. Use spaces to delimit between the toolbar buttons. Use pipe characters to group buttons. - Finally we set the
valid_elements. By default the editor accepts all valid HTML elements. With this option you can limit the elements to the set you provide. The elements are comma seperated. Square brackets after an element contain the attributes allowed on the element. Pipe characters delimit between the attributes.
{
"content_css": "/htmleditor.css",
"menubar": false,
"toolbar": "bold italic strikethrough | formatselect | bullist numlist | image imagefinder | pastetext | cx_formatcode | fullscreen",
"valid_elements": "h1,h2,h3,h4,h5,h6,p,br,b,strong,i,ul[style],ol[style],li,span[class|style],code[class],pre[class|data-mode|data-readonly|data-autoheight]"
}
For more configuration options have a look at: https://www.tiny.cloud/docs/tinymce/5/configure/