WordPress Connector
The WordPress Connector is a PHP plugin installed directly inside WordPress, not a Java connector plugin. It hooks into WordPress publish, update, and delete events to keep the search index synchronized with your content in real time.
Unlike the AEM and Web Crawler connectors (which are Java JARs loaded via -Dloader.path), the WordPress Connector is a PHP plugin that you install in your WordPress wp-content/plugins/ directory. It communicates directly with Viglet Turing via HTTP, no dumont-connector.jar needed.
Unlike the AEM and Web Crawler connectors, the WordPress plugin is not part of the Dumont connector application: it runs entirely inside WordPress and sends content directly to Turing via HTTP. No dumont-connector.jar is needed.
How It Works
The plugin integrates with WordPress hooks to automatically push content to the search index:
- On publish: When a post or page is published, the plugin extracts its content and sends it to Turing
- On update: When published content is modified, the index is updated automatically
- On delete: When content is trashed or deleted, it is removed from the index
- On status change: When a published post is changed to draft or private, it is removed from the index
- Manual bulk indexing: The admin panel provides buttons to index all posts or all pages in batches of 250
There is no scheduled or cron-based indexing, everything is event-driven or manually triggered.
Installation
- Copy the
viglet-turing-for-wordpressplugin folder to your WordPress installation:
wp-content/plugins/viglet-turing-for-wordpress/
-
Activate the plugin in WordPress Admin → Plugins
-
Configure the connection in Settings → Viglet Dumont
Configuration
Server Settings
| Field | Default | Description |
|---|---|---|
| Host | localhost | Turing server hostname |
| Port | 2700 | Turing server port |
| Path | /dumont | Base path for the indexing endpoint |
| Site Name | (required) | Semantic Navigation Site name in Turing |
Indexing Options
| Field | Description |
|---|---|
| Post types | Which content types to index (posts, pages, custom post types) |
| Remove on delete | Automatically remove from index when content is deleted |
| Remove on status change | Remove from index when status changes from published to draft/private |
| Index comments | Include post comments in the indexed content |
| Custom fields | Additional WordPress custom fields to include in the index |
| Excluded IDs | Post IDs to exclude from indexing |
Search Display Options
| Field | Description |
|---|---|
| Results per page | Number of search results to display |
| Show facets | Enable faceted navigation on the search results page |
| Facet fields | Which fields to show as facets (categories, tags, author, type) |
| Spellcheck | Enable spelling suggestions for search queries |
| Max tags | Maximum number of tags to display in facets |
Indexed Fields
The plugin extracts and sends these fields to Turing:
| Field | Source |
|---|---|
| id | WordPress post ID |
| title | Post/page title |
| content | Full post content |
| contentnoshortcodes | Content with WordPress shortcodes removed |
| permalink | Canonical URL |
| author | Author display name |
| type | Content type (post, page, custom) |
| date | Publication date |
| modified | Last modification date |
| categories | Category names (multi-valued) |
| tags | Tag names (multi-valued) |
| numcomments | Comment count |
| comments | Comment text (if comment indexing is enabled) |
| Custom fields | Any configured custom fields |
Multisite Support
The plugin supports WordPress multisite installations. When activated network-wide, it can index content from all blogs in the network, including blogid, blogdomain, and blogpath fields for each document.
Admin Panel Actions
The plugin adds action buttons to the WordPress admin settings page:
| Action | Description |
|---|---|
| Ping | Tests the connection to Turing |
| Index all Posts | Bulk indexes all published posts (batches of 250) |
| Index all Pages | Bulk indexes all published pages (batches of 250) |
| Delete all | Removes all WordPress content from the Turing index |
| Optimize | Triggers index optimization on the search engine |
Architecture
The plugin includes its own PHP HTTP client library (DumontPhpClient) for communicating with Turing:
viglet-turing-for-wordpress/
├── viglet-turing-for-wordpress.php # Main plugin (hooks, indexing, search)
├── viglet-turing-options-page.php # Admin settings page
├── DumontPhpClient/
│ └── Viglet/Dumont/
│ ├── Service.php # HTTP client for Turing
│ ├── Document.php # Document model
│ ├── Response.php # Response parser
│ └── HttpTransport/
│ ├── Curl.php # cURL transport
│ ├── CurlNoReuse.php # cURL without connection reuse
│ └── FileGetContents.php # file_get_contents fallback
└── template/
├── turing4wp_search.php # Search results template
├── search.css # Search results styling
└── autocomplete.css # Autocomplete styling