PHPackages                             wazum/sluggi - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. wazum/sluggi

ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility)

wazum/sluggi
============

TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects

14.4.0(1mo ago)39488.5k↓17.7%29GPL-2.0-or-laterPHPPHP ^8.2CI passing

Since Mar 13Pushed 1mo ago4 watchersCompare

[ Source](https://github.com/wazum/sluggi)[ Packagist](https://packagist.org/packages/wazum/sluggi)[ Docs](https://github.com/wazum/sluggi)[ RSS](/packages/wazum-sluggi/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (8)Dependencies (24)Versions (96)Used By (0)

 [![sluggi](Resources/Public/Icons/Extension.svg)](Resources/Public/Icons/Extension.svg)

sluggi
======

[](#sluggi)

*The URL Path Manager TYPO3 CMS deserves.*

[![Tests](https://github.com/wazum/sluggi/workflows/Tests/badge.svg)](https://github.com/wazum/sluggi/actions)[![PHP](https://camo.githubusercontent.com/fff68409e83d3ed7aa0b378c76366d72fa0fb1f875467162ce208929b7e753a7/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f5048502d382e32253230253743253230382e33253230253743253230382e342d626c75652e737667)](https://www.php.net/)[![TYPO3](https://camo.githubusercontent.com/7a7f454b121c8b45361575002b0af4cf08fdf25129d53d65595cbcaa29931e43/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f5459504f332d31322e3425323025374325323031332e342e323625324225323025374325323031342d6f72616e67652e737667)](https://typo3.org/)[![Total Downloads](https://camo.githubusercontent.com/984b02c21e8ce2c192cce99e9d68e8214e70e0aed2626c71364f571407d47a3b/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f64742f77617a756d2f736c756767692e737667)](https://packagist.org/packages/wazum/sluggi)[![GitHub Stars](https://camo.githubusercontent.com/8037d94f99709bd9e77807332096c8dd4cb1ab2ab6d0bc8f5e52b89da6d45ce1/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f73746172732f77617a756d2f736c756767693f7374796c653d666c6174)](https://github.com/wazum/sluggi/stargazers)[![License](https://camo.githubusercontent.com/77e900ae34f8da9ccccc42662fce61a94ab07ddbfe3f7d066178e824f3673dbd/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4c6963656e73652d47504c25323076322d626c75652e737667)](LICENSE)

URLs that stay in sync when titles change. Automatic redirects. Duplicate prevention on copy, move, and recycler restore. Locking, access control, conflict detection – everything you need to manage URL paths with confidence.

Note

**TYPO3 13.4** has a core bug where `TemporaryPermissionMutationService` does not grant page-level access for redirect storage. Non-admin editors without the site root page in their webmounts cannot create redirects on slug changes. Sluggi includes a workaround; this does not affect TYPO3 12 or 14.

One `composer require`, sensible defaults – [highly configurable](#configuration) when you need it.

 [**Try the interactive demo**](https://wazum.github.io/sluggi/)
 See every feature live in your browser – no installation required.

Installation
------------

[](#installation)

```
composer require wazum/sluggi
```

> **Version 14** is a complete rewrite of *sluggi* – modern, fully tested, and **compatible** with **TYPO3 12.4, 13.4.26+, and 14**.
>
> This is the version you should install regardless of your TYPO3 version. Previous major versions are no longer maintained.

What You Get
------------

[](#what-you-get)

[![sluggi editor](Documentation/sluggi_full_editor_view.png)](Documentation/sluggi_full_editor_view.png)

**Automatic sync** – Rename a page, the URL updates. All child pages follow. Redirects are created automatically.

**Conflict detection** – Duplicate URLs are caught instantly with unique alternatives proposed.

**Locking** – Pin critical URLs so nobody accidentally breaks them.

**Access control** – Let editors change the last segment only, or restrict editing based on their page tree permissions.

**Duplicate prevention** – Unique slugs on copy, move, and recycler restore. No more 500 errors from slug collisions.

**Redirect control** – Editors choose whether to create redirects when changing a URL.

**Redirect info** – See how many redirects point to a page, with a direct link to manage them.

**Any table** – Works with pages, news, events, or any record with a TCA slug field.

Features
--------

[](#features)

### Modern URL Path Editor

[](#modern-url-path-editor)

Out of the box, *sluggi* replaces the default slug field with a clean, focused interface:

[![Default view](Documentation/sluggi_default_view.png)](Documentation/sluggi_default_view.png)

### Auto-Sync: Change a Title, Update the URL

[](#auto-sync-change-a-title-update-the-url)

When sync is enabled, URL paths regenerate automatically when source fields (e.g. title, nav\_title) change. A badge on the source field shows it drives the URL:

[![Sync badge](Documentation/sluggi_sync.png)](Documentation/sluggi_sync.png)

- Per-record sync toggle – disable it for pages or records with manually crafted URLs
- Child pages update recursively when a parent path changes
- Redirects from old to new URL are created automatically via EXT:redirects
- Works for any table with a slug field (news, events, custom records)

### Lock URLs to Prevent Accidental Changes

[](#lock-urls-to-prevent-accidental-changes)

[![Locked URL](Documentation/sluggi_lock.png)](Documentation/sluggi_lock.png)

- Locked URLs cannot be edited and are skipped during auto-sync
- Optionally lock all descendant paths when an ancestor is locked
- Editing the full path auto-locks it to prevent sync from overwriting your work

### Translated Pages

[](#translated-pages)

[![Translated page](Documentation/sluggi_translated.png)](Documentation/sluggi_translated.png)

Translated pages inherit the sync and lock settings from the default language record. The toggles are disabled and display the parent's state – translations cannot override these flags independently. This ensures consistent URL behavior across all language versions.

### Non-Page Tables (News, Events, Custom Records)

[](#non-page-tables-news-events-custom-records)

[![Non-page table sync](Documentation/sluggi_non_page_sync.png)](Documentation/sluggi_non_page_sync.png)

Tables configured in `synchronize_tables` (e.g. `tx_news_domain_model_news`) get the same per-record sync toggle as pages. Editors can disable auto-sync for individual records where they've manually crafted a slug for SEO:

- Sync defaults to **on** for new records – slugs auto-generate from source fields
- Toggle sync **off** to keep a hand-crafted slug that won't change when the title is edited
- Source field badges appear when sync is active, showing which fields drive the slug
- Translated records inherit the sync state from their default language parent
- Sync state is stored in a separate reference table – no changes to your extension's database schema

### Granular Access Control for Editors

[](#granular-access-control-for-editors)

**Last segment only** – Non-admins edit just the final path segment. The parent path is read-only:

[![Last segment editing](Documentation/sluggi_last_segment_only.png)](Documentation/sluggi_last_segment_only.png)

**Full path editing** – A button lets permitted users temporarily unlock the full path:

[![Full path edit button](Documentation/sluggi_edit_full_path_url.png)](Documentation/sluggi_edit_full_path_url.png)

[![Full path editing enabled](Documentation/sluggi_transient_full_path_edit.png)](Documentation/sluggi_transient_full_path_edit.png)

**Hierarchy permissions** – Editing is restricted based on page tree permissions. Users can only modify segments for pages they're allowed to edit:

[![Hierarchy permissions](Documentation/sluggi_restricted_permissions.png)](Documentation/sluggi_restricted_permissions.png)

### Out-of-Sync URL Detection

[](#out-of-sync-url-detection)

When a page's URL path doesn't match the page hierarchy (e.g. after a page move, a manual admin edit, or a database import), *sluggi* detects the mismatch and informs the editor with a subtle amber highlight on the prefix, a one-time notification, and an inline note below the field:

[![Broken prefix](Documentation/sluggi_broken_prefix.png)](Documentation/sluggi_broken_prefix.png)

[![Broken prefix notification](Documentation/sluggi_broken_prefix_notification.png)](Documentation/sluggi_broken_prefix_notification.png)

The messages are tailored to the editor's permissions:

- Editors who can lock URLs are advised to either regenerate or lock the slug to keep a custom URL
- Editors without lock access are pointed to the regenerate button or advised to ask an administrator
- Admins see the full URL path with the mismatched portion highlighted

Locked and synced pages suppress the indicator entirely – locked pages have intentional custom URLs, and synced pages will self-correct on the next title change.

### Redirect Info

[](#redirect-info)

See at a glance how many redirects target a page, with a direct link to the redirects module:

[![Redirect info](Documentation/sluggi_redirect_display.png)](Documentation/sluggi_redirect_display.png)

Only shown to editors with access to the redirects module and `sys_redirect` table.

### Redirect Control

[](#redirect-control)

Let editors decide whether to create redirects when a URL changes:

[![Redirect modal](Documentation/sluggi_create_redirects.png)](Documentation/sluggi_create_redirects.png)

The choice applies recursively to all affected child pages. Self-referencing redirects are prevented automatically, and stale redirect cleanup only affects auto-created redirects – manually created redirects are never touched.

### Re-apply URL Paths Recursively

[](#re-apply-url-paths-recursively)

Right-click any page in the page tree and select **More options > Re-apply URL paths recursively** to regenerate URL paths for all descendant pages based on their current source fields (e.g. title, nav\_title):

[![Context menu](Documentation/sluggi_context_update.png)](Documentation/sluggi_context_update.png)

- Useful after reverting a slug change via TYPO3's undo notification, or when child pages have stale prefixes
- Slugs are regenerated from scratch using source fields – not by prefix replacement
- Hidden pages are included, locked pages are skipped (descendants still update unless `lock_descendants` is enabled)
- All changes share a single correlation ID – TYPO3's undo notification lets you revert everything at once
- Admin users only

### Copy URL to Clipboard

[](#copy-url-to-clipboard)

[![URL copied](Documentation/sluggi_url_copied_clipboard.png)](Documentation/sluggi_url_copied_clipboard.png)

### Slug Normalization

[](#slug-normalization)

TYPO3 core turns a title like "Products/Services" into `/products/services` (two segments) instead of `/products-services` (one segment). *sluggi* fixes this globally – for manual edits, auto-sync, regeneration, and page tree inline editing. Optional underscore preservation (RFC 3986) is also available.

### Duplicate Prevention Where TYPO3 Core Doesn't

[](#duplicate-prevention-where-typo3-core-doesnt)

- **Copy**: Copied pages get unique slugs in the target location
- **Move**: Child slugs update to reflect the new parent path
- **Recycler restore**: Restored records get deduplicated slugs instead of causing 500 errors

### Excluded Page Types

[](#excluded-page-types)

Remove URL paths from page types that don't need them (Sysfolder, Recycler, Spacer). An upgrade wizard cleans up existing slugs.

Configuration
-------------

[](#configuration)

All features work out of the box with sensible defaults. Fine-tune via **System > Settings > Extension Configuration > *sluggi***:

**Basic**

SettingDescriptionDefault`exclude_doktypes`Comma-separated doktypes excluded from slug path generation. The default `199,254` matches TYPO3 core's built-in exclusion of Spacer and Sysfolder (see `SlugHelper::resolveParentPageRecord()`). Add `255` to also exclude Recycler pages. If you use [b13/masi](https://github.com/b13/masi) to include sysfolders in URL paths, remove `254` from this list.`199,254``preserve_underscore`Keep underscores in URL paths instead of converting them to dashes. Useful when your URL convention or external systems require underscores (RFC 3986 compliant).Off`copy_url`Show a button to copy the full page URL to the clipboard. Saves editors from navigating to the frontend just to grab a link for emails, documents, or tickets.On`last_segment_only`Non-admin editors can only change the last segment of a URL path. The parent path stays read-only, preventing editors from accidentally breaking the site's URL hierarchy.Off`allow_full_path_editing`Show a button that lets permitted editors temporarily unlock the full path for editing (requires `last_segment_only`). The slug auto-locks afterwards to prevent sync from overwriting the custom path.Off**Sync**

SettingDescriptionDefault`synchronize`Keep URLs in sync with page titles automatically. When an editor renames a page, the URL path updates instantly – no manual work, no stale URLs. Redirects from old to new are created via EXT:redirects.On`synchronize_default`Turn on sync for every newly created page. Editors can still disable it per page for manually crafted URLs.On`synchronize_tables`Extend auto-sync beyond pages to any table with a slug field. Comma-separated list, e.g. `tx_news_domain_model_news`. Each configured table gets a per-record sync toggle so editors can opt out individually. Supports multi-field generation with `fieldSeparator`.–**Lock**

SettingDescriptionDefault`lock`Let editors pin important URLs so they can't be changed accidentally. Locked paths are also skipped during auto-sync, giving you full control over critical landing page URLs.Off`lock_descendants`When a parent page has a locked URL, protect all child page URLs too. Useful for entire sections of your site where URL stability is critical (e.g. campaign landing pages).Off**Redirect**

SettingDescriptionDefault`redirect_control`Show a modal when a URL changes, letting the editor decide whether to create a redirect. Gives editors control instead of silently creating redirects they may not want. The choice applies recursively to all affected child pages.Off`show_redirects`Display the number of active redirects targeting a page below the slug field, with a link to the redirects module pre-filtered by target page. Only shown to users with access to the redirects module. Requires EXT:redirects.OffFor deployment or version-controlled configuration, set values in `config/system/additional.php`:

```
$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['sluggi'] = [
    'synchronize' => '1',
    'synchronize_default' => '1',
    'synchronize_tables' => 'tx_news_domain_model_news',
    'lock' => '1',
    'lock_descendants' => '0',
    'last_segment_only' => '1',
    'allow_full_path_editing' => '1',
    'exclude_doktypes' => '199,254,255',
    'copy_url' => '1',
    'preserve_underscore' => '0',
    'redirect_control' => '1',
    'show_redirects' => '1',
];
```

Site Configuration: Redirects & Recursive Slug Updates
----------------------------------------------------------

[](#site-configuration-redirects--recursive-slug-updates)

*sluggi* requires [EXT:redirects](https://docs.typo3.org/c/typo3/cms-redirects/main/en-us/) which controls what happens when a page slug changes: whether child pages update recursively, whether redirects are created, how long they live, and which HTTP status code they use.

These settings are configured **per site** via [TYPO3 site sets](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSettings.html). To activate them, add the `typo3/redirects` set to your site's `config.yaml` and override the defaults in `settings.yaml`.

### Step 1: Add the redirects site set

[](#step-1-add-the-redirects-site-set)

In `config/sites//config.yaml`, add `typo3/redirects` to the `dependencies` list:

```
base: 'https://example.com/'
rootPageId: 1
dependencies:
  - typo3/redirects
languages:
  # ...
```

### Step 2: Override settings

[](#step-2-override-settings)

Create `config/sites//settings.yaml` with the settings you want to change:

```
redirects:
  autoUpdateSlugs: true
  autoCreateRedirects: true
  redirectTTL: 0
  httpStatusCode: 301
```

### Available Settings

[](#available-settings)

SettingTypeDefaultDescription`redirects.autoUpdateSlugs`bool`true`Recursively update child page slugs when a parent slug changes. Works together with *sluggi*'s auto-sync – when a title change triggers a slug update on a parent page, all descendants get their slug prefix replaced automatically.`redirects.autoCreateRedirects`bool`true`Create redirect records from old to new URL when a slug changes. Only applies in the **live workspace** – editing in a workspace does not create redirects until the change is published.`redirects.redirectTTL`int`0`Lifetime in **days** for auto-created redirects. `0` means no expiration. When set, the redirect's `endtime` is calculated as creation time + TTL days.`redirects.httpStatusCode`int`307`HTTP status code for auto-created redirects. Does not affect manually created redirects. Common values: `301` (Moved Permanently – best for SEO), `302` (Found), `307` (Temporary Redirect – the default).> **How this relates to sluggi:** When *sluggi*'s auto-sync regenerates a slug (because the page title changed), EXT:redirects picks up the change and applies the settings above. If `autoUpdateSlugs` is enabled, child pages update recursively. If `autoCreateRedirects` is enabled, redirect records are created for the old URLs. The `redirectTTL` and `httpStatusCode` settings control the properties of those redirect records. When *sluggi*'s `redirect_control` feature is enabled, editors can override `autoCreateRedirects` on a per-change basis via a modal dialog.

### Ready-to-Use Configuration Presets

[](#ready-to-use-configuration-presets)

*sluggi* ships ready-to-use presets in [`Configuration/SiteSettings/`](Configuration/SiteSettings/). TYPO3's YAML loader supports [`imports`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/YamlApi/Index.html#imports) with `EXT:` paths, so you can reference them directly from your `settings.yaml` without copying files.

Create `config/sites//settings.yaml` with an import:

```
imports:
  - { resource: 'EXT:sluggi/Configuration/SiteSettings/recommended.settings.yaml' }
```

You can override individual values after the import:

```
imports:
  - { resource: 'EXT:sluggi/Configuration/SiteSettings/recommended.settings.yaml' }

# Override just the TTL from the preset
redirects:
  redirectTTL: 180
```

**Available presets:**

PresetStatus codeTTLDescription[recommended](Configuration/SiteSettings/recommended.settings.yaml)301permanentBest for production sites where SEO matters[temporary-with-ttl](Configuration/SiteSettings/temporary-with-ttl.settings.yaml)30790 daysSites with frequently changing content (news, events, campaigns)[no-auto-redirects](Configuration/SiteSettings/no-auto-redirects.settings.yaml)––Recursive slug updates only, redirects managed externally or manually[manual-only](Configuration/SiteSettings/manual-only.settings.yaml)––No recursive updates, no auto-redirects, full manual control### How It All Fits Together

[](#how-it-all-fits-together)

What happens`autoUpdateSlugs``autoCreateRedirects`sluggi `synchronize`sluggi `redirect_control`Title changes → slug updates––**controls this**–Parent slug changes → child slugs update**controls this**–––Old URL → redirect to new URL–**controls this**––Editor chooses whether to create redirect–must be `true`–**controls this**For the full EXT:redirects documentation, see the [TYPO3 Redirects Setup](https://docs.typo3.org/c/typo3/cms-redirects/main/en-us/Setup/Index.html). For details on TYPO3 site sets and settings, see [Site Settings](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSettings.html).

Permissions
-----------

[](#permissions)

Every *sluggi* feature integrates with TYPO3's standard backend user and group permissions. You decide per user group which editors can see and use which controls – the same way you manage access to any other field in TYPO3:

FieldPermission controls`pages:slug`Edit the URL path`pages:tx_sluggi_sync`Toggle sync on/off`pages:slug_locked`Lock/unlock URLs`pages:tx_sluggi_full_path`Use full path editingExample setup for a typical editorial team:

AdminSenior EditorEditorEdit URL path✓✓✓Toggle sync✓✓–Lock/unlock URLs✓✓–Full path editing✓✓–**Admin** – Full control over all URL features.

**Senior Editor** – Can lock critical URLs before a campaign launch, toggle sync for pages with manually crafted paths, and edit full URL paths when needed.

**Editor** – Can edit the last segment of a URL (with `last_segment_only` enabled), but cannot disable sync or unlock a locked URL. URLs stay consistent without extra training.

User Settings
-------------

[](#user-settings)

Users can enable compact controls via **User Settings > Personalization** to collapse controls behind a menu icon.

Slug Source Fields
------------------

[](#slug-source-fields)

*sluggi* reads the source fields for slug generation from the standard TCA [`generatorOptions.fields`](https://docs.typo3.org/m/typo3/reference-tca/main/en-us/ColumnsConfig/Type/Slug/Index.html) configuration of the `slug` column. All referenced fields are automatically detected — they get a badge in the backend and the frontend component listens to them for real-time sync.

```
'slug' => [
    'config' => [
        'type' => 'slug',
        'generatorOptions' => [
            'fields' => [['nav_title', 'title']],
        ],
    ],
],
```

For more configuration options (e.g. multiple fields, fallback chains, field separators), see the [TYPO3 TCA slug documentation](https://docs.typo3.org/m/typo3/reference-tca/main/en-us/ColumnsConfig/Type/Slug/Index.html).

For non-page tables, add the table name to the `synchronize_tables` extension setting. The slug auto-regenerates whenever a source field changes on save, unless the editor has disabled sync for that specific record via the per-record toggle.

Requirements
------------

[](#requirements)

- TYPO3 12.4, 13.4.26+, or 14.x
- PHP 8.2+
- EXT:redirects

Suggested Extensions
--------------------

[](#suggested-extensions)

- [news-redirect-slug-change](https://github.com/georgringer/news-redirect-slug-change) – Redirects when news slugs change
- [ig-slug](https://github.com/internetgalerie/ig_slug) – Rebuild URL slugs in bulk
- [masi](https://github.com/b13/masi) – Exclude specific page slugs from subpage URL generation
- [content\_slug](https://github.com/sebkln/content_slug) – Slug field for human-readable content element anchors (`#my-section`)

Fixes for TYPO3 Core Issues
---------------------------

[](#fixes-for-typo3-core-issues)

*sluggi* works around these known TYPO3 core issues:

- [\#108375](https://forge.typo3.org/issues/108375) – When multiple pages are updated in a single DataHandler operation (e.g. recursive slug update), TYPO3 core assigns each page its own correlation ID, making it impossible to revert all changes at once via the undo notification. *sluggi* shares one correlation ID across all pages in the operation so the entire batch can be reverted with a single click.
- [\#108870](https://forge.typo3.org/issues/108870) – The "Revert update" notification after a slug change only rolls back child page slugs and redirect records, but not the parent page's own slug change. *sluggi* extends the rollback to include the parent page so the entire change is fully reverted.
- [\#106152](https://forge.typo3.org/issues/106152) – Restoring pages from the recycler does not check for slug conflicts, which can result in duplicate URLs and 500 errors. *sluggi* validates and deduplicates slugs on restore.
- [\#86740](https://forge.typo3.org/issues/86740) – TYPO3 core treats slashes in page titles as path separators, turning "Products/Services" into two URL segments instead of one. *sluggi* normalizes slashes to the fallback character globally.
- [\#103833](https://forge.typo3.org/issues/103833) – Renaming a slug back to a previous value can leave behind a self-referencing redirect. *sluggi* prevents creation of self-referencing redirects automatically.
- [\#97962](https://forge.typo3.org/issues/97962) – TYPO3 core always replaces underscores with the fallback character during slug generation. *sluggi* adds a `preserve_underscore` setting for RFC 3986 compliant URLs.
- [\#94003](https://forge.typo3.org/issues/94003) – When copying a page subtree, TYPO3 core changes the copied parent's slug immediately (e.g. appending `-1`) but fails to update child pages' slug prefixes accordingly. *sluggi* recalculates all slugs in the copied tree with correct parent prefixes.
- In TYPO3 13.4, `TemporaryPermissionMutationService` grants `tables_modify` for `sys_redirect` but does not grant page-level access. Editors without the site root page in their webmounts cannot create redirect records. *sluggi* bypasses page-level access checks for redirect creation DataHandler operations.

Upgrading
---------

[](#upgrading)

### 14.0.0

[](#1400)

**Configuration keys renamed**

The following extension configuration keys were renamed. Your existing values are **not** migrated automatically — update them manually in `config/system/additional.php` or via **Admin Tools > Settings > Extension Configuration**:

Old key (v12/v13)New key (v14)`exclude_page_types``exclude_doktypes``allow_lock``lock`**Configuration keys removed**

Removed keyReplacement`pages_fields`Configure source fields via TCA `generatorOptions.fields``whitelist`Use standard TYPO3 backend user/group permissions for `pages:slug``slash_replacement`Now always active, no longer configurable**Redirect settings moved to site configuration**

Extension-level redirect keys (`redirect_lifetime`, `redirect_code`, `redirect_force_https`, `redirect_respect_query_parameters`, `redirect_keep_query_parameters`) were removed. Use TYPO3's native per-site redirect settings instead. Ready-made presets are shipped in `Configuration/SiteSettings/`.

### 14.2.0

[](#1420)

**`exclude_doktypes` default changed from empty to `199,254`** ([\#135](https://github.com/wazum/sluggi/issues/135))

Previous versions shipped with an empty `exclude_doktypes` default, which caused sluggi's copy/move handlers to include Spacer and Sysfolder names in generated slug paths — contrary to TYPO3 core's built-in behavior in `SlugHelper::resolveParentPageRecord()`. The default is now `199,254` (Spacer, Sysfolder) to match core.

Sluggi now also overrides core's `resolveParentPageRecord()` so that *all* slug generation paths (AJAX suggestions, new pages, copy, move, sync) consistently respect the `exclude_doktypes` setting. Without this override, TYPO3 core hardcodes the exclusion of Spacer and Sysfolder regardless of configuration.

**Upgrade wizard:** Run **Admin Tools > Upgrade > Upgrade Wizard** after updating. The wizard *"Set default excluded page types for sluggi"* sets `exclude_doktypes` to `199,254` for existing installations where it was empty.

**[b13/masi](https://github.com/b13/masi) users:** If you use masi to include sysfolders in URL paths, remove `254` from `exclude_doktypes` after the upgrade. Masi uses a TCA `postModifier` (not an XCLASS), so both extensions work together without conflicts — masi overrides the generated slug after sluggi's `SlugHelper`, and both will consistently include the sysfolder when `254` is not in the exclusion list.

Support and Feature Requests
----------------------------

[](#support-and-feature-requests)

Use the [issues tracker](https://github.com/wazum/sluggi/issues) on GitHub for support questions and new feature requests or ideas concerning the extension.

Credits and Sponsors
--------------------

[](#credits-and-sponsors)

Made with love for the TYPO3 community by [Wolfgang Klinger](https://wolfgang-klinger.dev/).

Many thanks to [plan2net GmbH](https://www.plan2.net/) for allowing me to work on the extension during my working hours and for great projects where this extension is already being used in real life.

Special thanks to [TU München](https://www.tum.de/) and other German universities that sponsored my time at *plan2net GmbH* to work on this extension (*applies to previous versions*).

License
-------

[](#license)

GPL-2.0-or-later

 [![sluggi](Resources/Public/Icons/Extension.svg)](Resources/Public/Icons/Extension.svg)

###  Health Score

66

—

FairBetter than 99% of packages

Maintenance89

Actively maintained with recent releases

Popularity50

Moderate usage in the ecosystem

Community14

Small or concentrated contributor base

Maturity89

Battle-tested with a long release history

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~31 days

Recently: every ~8 days

Total

83

Last Release

55d ago

Major Versions

10.3.0 → 13.0.02024-12-18

10.3.1 → 13.0.22025-02-14

v10.x-dev → v11.x-dev2025-05-07

v11.x-dev → 13.0.32025-05-16

12.1.3 → 14.0.02026-02-09

PHP version history (7 changes)1.0.0PHP >=7.0.0

2.0.0PHP >=7.2.0

12.0.0PHP ^8.1

11.0.0PHP ^7.4

11.1.0PHP >= 7.4 < 8.3

13.0.0PHP ^8.2

v11.x-devPHP ^7.4 || ^8.1

### Community

Maintainers

![](https://www.gravatar.com/avatar/f4ea950f22b43e010ba4f0a6effb0928a6a1d11f64d36cec0d030b757bdfa85e?d=identicon)[wazum](/maintainers/wazum)

---

Top Contributors

[![wazum](https://avatars.githubusercontent.com/u/146727?v=4)](https://github.com/wazum "wazum (175 commits)")

---

Tags

cmsextensionpathphprealurlredirectsseoslugtypo3typo3-cmstypo3-cms-extensiontypo3-extensionurlurl-managementurlslugroutingredirectseotypo3Speaking URLRealURLurl segmenturl path

###  Code Quality

TestsPHPUnit

Static AnalysisPHPStan

Code StylePHP CS Fixer

Type Coverage Yes

### Embed Badge

![Health badge](/badges/wazum-sluggi/health.svg)

```
[![Health](https://phpackages.com/badges/wazum-sluggi/health.svg)](https://phpackages.com/packages/wazum-sluggi)
```

###  Alternatives

[jbroadway/urlify

A fast PHP slug generator and transliteration library that converts non-ascii characters for use in URLs.

6737.4M62](/packages/jbroadway-urlify)[pid/speakingurl

Generate of so called 'static' or 'Clean URL' or 'Pretty URL' or 'nice-looking URL' or 'Speaking URL' or 'user-friendly URL' or 'SEO-friendly URL' or 'slug' from a string.

1.1k5.3k1](/packages/pid-speakingurl)[koehlersimon/slug

Helps you managing the URL slugs of your TYPO3 site

2965.7k](/packages/koehlersimon-slug)[internetgalerie/ig-slug

Rebuild URL slugs

12861.7k2](/packages/internetgalerie-ig-slug)[clickstorm/cs-seo

\[clickstorm\] SEO - Extension for TYPO3. Enables important onpage features for search engine optimization (SEO). Expands the page settings and any desired records for example with a preview for Google search results (SERP) Structured Data (JSON-LD) and a Focus Keyword. Restrictive hreflang and canonical tags. Modules for metadata of records and alternative texts of images. Further features are shown in the extension manual.

35473.9k1](/packages/clickstorm-cs-seo)[b13/masi

TYPO3 Extend URL generation to optionally include storage folders.

24299.3k](/packages/b13-masi)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)