Electrons

Team members that worked on this item. You can only select persons listed on your Team page, so if you want to add external contributors: add them to the team page first (can be unpublished).

Connect any available static resource(s) to this page. Presently, this is not being shown in any template, so it's up to you to implement it as you see fit.

Point to external sources, to add some scientific credibility to your content. You can automatically attach these links to content references by activating the setting under Navigation.

This will also create a relation on the linked page. You can (and should!) link to other pages in your content whenever relevant, but this makes it easier to generate lists of related pages.

Connect the related organization(s). If this list is empty, you need to create an Organizations container first and register its ID under System Settings.

Connect a person to this item. This list is populated with all the persons that are listed on your Team page.

Maintain a list of social media platforms through which visitors can connect with you.

Connect a MODX user to this item. Only active users will be shown.

Optional. This is the address where the messages appear to be sent from. Can be a non-existing address, like [email protected]. Defaults to emailsender system setting.

Optional. This is the name that will (probably) be visible in the recipients' inbox. Defaults to site_name system setting.

The content of the email that will be sent. You can use placeholders here with the following syntax: . If you want to use your own HTML, see the template option below.

Optional. This address will be used when recipient replies to this message directly. Defaults to respectively the client_email and emailsender system setting.

Name of the chunk containing the (HTML) email template. The default fbAutoresponder chunk only parses the autoresponse message above.

IMPORTANT! For the autoresponder to know which email address to use, the Input (Email) field needs to be present in the form.

Page containing the ConfirmRegister snippet for email activation. Enter page ID or drag the page from the menu tree to this input field. Defaults to the activation_resource_id system setting.

Whether or not new users need to activate their account via email. IMPORTANT! For the activation process to know which address to use, the Input (Email) field needs to be present in the form.

Number of minutes until the activation email expires. Defaults to 3 hours.

If switched on, any extra fields in the form are added to the extended field in the user profile.

Name of the form field that will receive the full name of the user. Handy when using email address as username. You can use the label name of the CB field here, or the input name in the HTML.

Name of the form field that will receive a password. If empty, a password will be generated instead. You can use the label name of the CB field here, or the input name in the HTML.

Optional. A comma-separated list of user group names or IDs to add the newly-registered user to.

Optional. The name of the form field that decides which user groups the new user will belong to. You can use the label name of the ContentBlock field here, or the name in the HTML.

Name of the form field that will receive the username. You can use the label name of the CB field here, or the input name in the HTML. Tip: consider using the email address here..

Stored uploads are saved in this folder. The path needs to be relative to the location of the assets_path setting. Please note that 6 will be parsed, but other placeholders wont.

Place any snippet / FastField call here that outputs a single email address. WARNING: populating this field will override the default recipient address, so test thoroughly!

Prefix used by the chunks containing the HTML for the template rows. After this prefix follows an ID (i.e. fbEmailRow_28), connecting that chunk to the correct ContentBlocks field.

A snippet name (or comma separated list of names) to execute. They are run after the form is submitted, but before any emails are sent (or user is created). Useful for additional validation.

A snippet name (or comma separated list of names) to execute. They are run after the form is fully submitted and all emails are sent. Useful for writing submitted values to the database.

A snippet name (or comma separated list of names). They are run before the form is initialised. Useful for prefilling form fields with existing data.

Place any element here that is able to decide where to redirect the user after form submission. If the result is empty, it falls back on the ID provided under general settings.

A snippet name (or comma separated list of names) to execute. They are run when the form loads and all pre-hooks are finished. Useful for fetching session data.

Store data in session before redirecting the user to a confirmation / thank you page, or to another form (as part of a multi-page form). Use FormItRetriever to access the data again.

If 'store data' is switched on, this specifies the number of seconds to store the submitted form data. Defaults to five minutes.

The content of the activation email, if email type is Inline. Make sure it contains the placeholder for the confirmation link!

Enter chunk name here if email type is Chunk, or an absolute file path if email type is File (you can use {core_path}, {base_path} or {assets_path} as placeholders here).

Optional.

Optional.

Optional. Defaults to emailsender system setting.

Optional. Defaults to site_name system setting.

Name of the chunk containing the (HTML) email template. You can replace the default with your own... Just make sure it contains the fbFormReport snippet call for listing the fields.

Submitted forms will be sent to this address. If you leave this field empty, no emails will be sent. This may be what you want when using a custom hook for processing the form.

Validate fields just before the form is submitted, or when the visitor leaves the form field again (on blur).

Validate form input in the browser first, before submit. The javascript automatically picks up required settings and some field-specific properties and backend validation is still applied.

Enter the ID of the page, or drag the page from the menu tree to this input field.

Save submitted data in the database. You can view this data under Top menu > Extras > FormIt.

Store uploads in designated folder (defined under Advanced). You may need to monitor and periodically clean up this folder in order to comply with GDPR retention policies.

Defaults to Send.

Where would you like to be able to use this background?

JSON array of CSS selectors. Simulates multiple sequential click interactions.

Wait for x milliseconds before starting the test. This gives pages a little breathing space to adjust after page load (things like fonts, DOM manipulation, etc).

JSON array of CSS selectors. These selectors are hidden from our analysis but retained in the original layout flow.

JSON array of CSS selectors. Simulates multiple sequential hover interactions.

JSON array of selector and string values. Simulates multiple sequential keypress interactions.

Percentage of diverging pixels allowed to pass test.

Wait for x milliseconds after interacting with hoverSelector or clickSelector. Ideal for use with a click or hover element transition.

Full site URL of the domain to compare with (the live domain for example). If you leave this empty, each page will be tested against an older version of itself.

JSON array of CSS selectors. These selectors are removed from the DOM before screenshots are taken.

Chunk containing the JSON config used for each scenario.

Enable if you want BackstopJS to find and take screenshots of all matching selectors.

Explicitly set the number of results that you expect to find with the selectors. If set to a value greater than 0, the test will fail if the number of results does not match this value.

JSON array of CSS specific selectors to capture. Defaults to the entire document if omitted. Use "viewport" to capture the viewport size.

The maximum number of capturing screens to run in parallel. This value can be adjusted as needed to increase/decrease the amount of RAM required during a test.

The maximum number of compare screens to run in parallel. This value can be adjusted as needed to increase/decrease the amount of RAM required during a test.

Choose which rendering engine to use. Puppeteer renders pages in headless Chrome, whereas Playwright also has the option to use Firefox or Webkit. See setting below.

Changing this only applies if engine is Playwright.

Choose in what format to return the test results.

JSON array of screen size objects to test against.