Configuration

T3AS requires a few configuration steps to set up and run properly. Follow the sequence below to ensure a smooth integration.

1. Extension Settings

Configure the basic extension settings, including your API key and other required parameters.

1. Go to the TYPO3 backend.

2. Open Admin Tools > Settings.

3. Click Configure Extensions.

4. Open T3CS (ns_t3cs). Set your default AI models, then save.

5. Open aiuniverse (ns_aiuniverse). Pick the AI models for the chatbot, then click Save.

2. Dashboard

Purpose

The Dashboard gives an overview of your AI training pipeline for the current site.

What you see

• Which AI/embedding model is in use (e.g. OpenAI, Gemini, Mistral, Custom).

• Status of the Search and Chatbot modules (if installed): active/inactive, AI engine, base model, embedding model.

• Status of your data sources and training (e.g. how many items are pending, completed, or failed).

• Training Pipeline section: data sources count, queue size, and a link to CLI reference.

• Usage Analytics summary (e.g. total interactions, search queries, chat sessions over the last 7 days).

• A link to the Scheduler to run or check the automatic training task.

Scheduler link

From the Dashboard you can open the TYPO3 Scheduler and locate the automatic training task (typically named T3AS Training for this site). Use Run All or Run Task Now to process the training queue immediately.

3. Data Source

Purpose

Add and manage the sources of content that will be used for AI search and the AI search (e.g. website pages, PDFs, Q&A).

Adding a data source

1. Click + Add Source.

2. Choose the type of source, for example:

   • Sitemap XML – Your sitemap URL(s) (e.g. https://example.com/sitemap.xml).

   • PDF Documents – Folder path where PDFs are stored (and optionally upload PDFs).

   • TYPO3 Pages – Content from specific TYPO3 pages.

   • Web Pages – A website URL; optionally limit to a path (e.g. https://example.com/blog/*).

   • Q&A Pairs – Manual question-and-answer content.

   • Indexed Search / Ke Search / Solr – If the corresponding extensions are installed and indexed content is available.

3. Fill in the requested details (URLs, folder path, page selection, etc.) and give the source a Name (e.g. Main Website) and optional Description.

4. Set Sync interval: how often content should be refreshed (e.g. Hourly, Daily, Weekly). Custom means no automatic schedule (manual sync only).

5. Set Type (Usage): whether this source is for Search.

6. Set Enabled to on if the source should be active.

7. Click Save.

After saving, T3AS will:

• Create or update the data source.

• Sync content into the training queue (new or changed items).

• Automatically create the T3AS Training Scheduler task for this site (if it does not exist yet) and run it at the frequency you set (e.g. Hourly, Daily, Weekly). You do not need to create the scheduler task manually—it is created when the source is saved and will execute according to the chosen sync interval.

Editing or deleting a source

Use the actions next to each data source to edit (type, URLs, interval, usage) or delete it.

Important

Deleting a data source also removes its training queue and embedded data for that source.

Sync

Sync (per source or Sync all) refreshes content from the source into the training queue.

• Sync does not run AI training by itself.

• Training is performed by the Scheduler task or manually (see Training Center).

Scheduler

When you create a data source, T3AS will automatically create the T3AS Training Scheduler task for this site (if it does not exist yet) and run it at the frequency you set (e.g. Hourly, Daily, Weekly). You do not need to create the scheduler task manually—it is created when the source is saved and will execute according to the chosen sync interval.

From the Dashboard you can open the TYPO3 Scheduler and locate the automatic training task (typically named T3AS Training for this site). Use Run All or Run Task Now to process the training queue immediately.

Command-line tools

What is command-line scheduler execution?

Command-line scheduler execution means running the TYPO3 Scheduler task directly from your terminal. This is useful when you want to process the training queue immediately, without waiting for the next scheduled interval.

How to run the scheduler task

1. Open your terminal in the TYPO3 project root (where DDEV is available).

2. Run one of the commands below, based on your installation type.

3. Check the terminal output to confirm the task completed successfully.

If you are using DDEV, you can run the T3AC training task manually from the command line.

Legacy installation:

ddev typo3/sysext/core/bin/typo3 scheduler:execute --task=9

Composer installation:

ddev typo3 scheduler:run --task=9

What happens after running the command?

• TYPO3 executes Scheduler task 9 (T3AC Training).

• Items in the training queue are processed.

• You can verify progress and completion directly in the command output.

Example output

Example of scheduler task output in the terminal.

Example showing queue processing and training completion summary.

For more options and details, see the TYPO3 Scheduler documentation: https://docs.typo3.org/c/typo3/cms-scheduler/13.4/en-us/Administration/ConsoleTools/Running.html#providing-options-to-the-shell-script

4.Training Center

Purpose

View the training queue (items collected from all data sources) and control training and cleanup.

What you see

• Summary counts: Total items, Pending, Embedding (processing), Completed, Failed, and Tokens used.

• All Sources: List or summary of data sources and item counts.

• Training Queue table: Items with columns such as Item, Status, Tokens, Created, Actions.

• Filters: By data source, status (All Statuses), or search text.

• Actions: Select All, Delete, Re-queue (reset).

Queue item statuses:

• Pending – Waiting to be processed.

• Processing / Embedding – Currently being sent to the embeddings service.

• Completed – Successfully trained.

• Failed – Error during training.

Actions

Sync

Refreshes content from the data source into the queue (same as in the Data Source tab).

Reset (Re-queue)

Puts a failed or completed item back to Pending so it will be processed again on the next training run.

Delete

Removes selected queue items.

Important

Deleted items will not be trained again unless they are added again by a new sync.

Run training

Use the link to the Scheduler module and run the T3AS Training task for this site.

When the task runs, it:

• Processes all Pending queue items (generates embeddings).

• Runs cleanup of old completed/failed items according to the retention setting.

Training behaviour (simple terms)

• Only items in status Pending are processed when training runs.

• Processing means: the text is sent to the configured embeddings service, and the result is stored for search usage.

• After success, the item is marked Completed; on error, Failed.

• How often training runs depends on the Sync interval of your data sources and on the Scheduler actually being triggered (e.g. via cron).

5. Search tab

This tab is shown only if the ns_t3as (AI Search) extension is installed.

Use it to configure and manage AI-powered search: which data sources feed search and how search behaves. The available options depend on the installed version of ns_t3as.

Typical sub-tabs:

• Settings – Enable AI search globally, result style, search class (e.g. for Ke Search), custom instructions.

• Widget – Widget mode, trigger button, layout, colors.

• Questions – Predefined questions and storage.

• Reference Links to display related URLs in search results based on indexed data. When enabled, search results include clickable links from indexed sources (for example, TYPO3 pages, documents, and other indexed content). These links help users quickly access relevant information related to their search query.

6. Usage Analytics

Purpose

View recent search and search activity (if the corresponding extensions are installed).

What you see

Search

Recent searches: search term, result snippet, page, language, time.

Filtering and export

• Search queries or responses – Search within the logs.

• All Modules / All Languages – Filter by module and language.

• Export – Download analytics data.

Deletion / cleanup

You can delete individual entries (for privacy or cleanup):

• Deleting search entries affects search history.

• Deleting search entries can be per IP (all conversations from that IP).

When no data has been recorded yet, the message shown is: “No interaction logs yet. Search and search history will appear here when the modules are loaded and users interact.”

7. AILogs

Purpose

View log entries for the current site, including sync, training, and error events.

What you see

• Search: Use the search box (for example: Search in message...) to find specific log text.

• Channel: Filter by channel (default: [all]).

• Level: Filter by log level (for example: Any, Error, Warning, Info).

• Max rows: Set how many rows are shown per page (default: 50).

• Entry count: The page shows a summary like Showing up to 50 of 745 entries per page.

• Log table columns: - Time - Level - User - Details

8. AI Statistics

Purpose

View AI API usage statistics for the current site.

What you see

• API Usage summary for your search activity.

• API Requests count.

• Tokens usage details: - Total tokens - Context tokens - Generated tokens

If the selected search engine is Solr, please provide the following details in case your Solr server is secured with HTTP authentication.

• Solr Username Username for Solr authentication.

• Solr Password Password for Solr authentication.

The Hosted-Solr Server feature enables you to connect your TYPO3 instance directly to the Hosted-Solr service for improved search indexing and data retrieval. The following guide outlines how to configure T3AS and Hosted Solr in your TYPO3 instance using the Site Configuration module.

• Step 1: Open Site Configuration

1. In the TYPO3 backend, navigate to Site Management → Sites

2. Edit site configuration

• Step 2:Scroll down to the Solr section in the same T3AS tab and Configure Solr Integration

• Step 4: Define Solr Connection Settings

• Step 5: Save Configuration

Getting Started

1. Create an Account: Sign up on the Hosted-Solr platform using your email address.

2. Create a Solr Core: Once your account is active, create a new Solr core.

3. Configure in TYPO3: Add your Solr core connection details within the TYPO3 Site Settings.

This integration allows you to seamlessly manage your Solr configuration and maintain consistent communication between TYPO3 and the Hosted-Solr environment.

Verifying the Connection

After configuration, ensure that Solr is properly connected:

• Navigate to the Info module inside the Solr tab within your TYPO3 backend.

• Verify that the Solr connection status and indexing information appear correctly.

Additional Fields Support

The extension now supports fetching additional fields from Solr beyond the standard predefined set.

This means you can include custom or project-specific fields in your search configuration to enhance indexing and display flexibility.

1. Go to the Extension Settings in TYPO3.

2. Specify which fields should be retrieved from Solr.

3. Save your settings to enable greater control over search results and data output.

By leveraging this feature, you can tailor your Solr-based search experience to match the exact needs of your TYPO3 project.

Note

Several default fields are automatically included for content retrieval from Solr: id, site, type, uid, content, pid, url, changed, and access. Ensure that Solr is properly configured and that the content field is available in your Solr-indexed data.

Using ke_search and indexed_search

When configuring T3AS with ke_search or indexed_search, make sure the following conditions are met:

1. All Website Data Indexed

   • Ensure that the complete website content is indexed by the respective search extension before enabling T3AS.

2. Scheduler Execution

   • Run all required schedulers as outlined in the Scheduler configuration section to keep the data fresh and available for AI-powered search.

Injecting AI Search result in TYPO3 Search Extensions

This integration allows you to inject AI-generated results into an existing search form

Note

Make sure you have added the Search Class/id in the site settings as described in https://docs.t3planet.de/en/latest/ExtNsT3AS/Configuration/Index.html#search-engine-settings

For example, If you want to render the AI search result on below the ke_search form, Please add below code at

EXT:ke_search/Resources/Private/Templates/SearchForm.html

<f:cObject typoscriptObjectPath="lib.injectAiSearchResults" />

Enable AI Search plugin using TypoScript

To enable this, Add the following TypoScript object to any template where you want the AI Search plugin to be rendered. The searchPid value should be set to the page ID where the plugin is placed (for example: 4).

Add the following TypoScript object to any template where you want the AI Search plugin to be rendered:

<f:cObject typoscriptObjectPath="lib.renderAiSearchPlugin" data="{searchPid:4}"/>