Beta [NC] XFRM Thread Prefix Mapper 1.0.0b

XFRM Thread Prefix Mapper​

Automatically map XenForo Resource Manager resource prefixes to the prefixes used by their associated discussion threads.

Overview​

XenForo Resource Manager allows a category to automatically create a discussion thread in a selected forum. However, XFRM normally uses only one fixed thread prefix configured for that category.

This can become limiting when several resource types share the same category or destination forum.

For example, a single “Software” resource category may contain resources using the following resource prefixes:

• Windows
• macOS
• Linux
• Android

By default, XFRM cannot automatically assign a different thread prefix according to the resource prefix selected by the author.

[NC] XFRM Thread Prefix Mapper adds this missing mapping layer.

You can configure rules such as:

• Resource prefix “Windows” → Thread prefix “Windows”
• Resource prefix “macOS” → Thread prefix “macOS”
• Resource prefix “Android” → Thread prefix “APK”

When XFRM creates the associated discussion thread, the correct thread prefix is automatically selected.

Main features​

• Map each native XFRM resource prefix to a XenForo thread prefix.
• Global mappings that work across every applicable XFRM category.
• Category-specific mappings that can override a global mapping.
• Automatic prefix selection when XFRM creates a discussion thread.
• Automatic synchronization when a resource prefix is changed.
• Automatic synchronization when a resource is moved to another XFRM category.
• Safe handling when an associated discussion thread is manually moved to another forum.
• Synchronization of discussion threads that already existed before the add-on was installed.
• Centralized bulk-management page for every mapping.
• Validation against the prefixes allowed in each destination forum.
• Automatic fallback to the native XFRM category thread prefix.
• Warnings for deleted, invalid, unavailable or orphaned mappings.
• Automatic cleanup when resource prefixes, thread prefixes or XFRM categories are deleted.
• Dedicated administrator permission.
• Background synchronization suitable for communities with many resources.
• English phrases included by default.
• Optional French, Turkish, and Russian translation included.

Configure a mapping directly from a resource prefix​

A new setting named “Associated thread prefix” is added directly to the XFRM resource-prefix editor.

To find it:

Admin control panel
→ Resources
→ Resource prefixes
→ Edit a resource prefix

Select the thread prefix that should be used whenever a resource uses this resource prefix.

The setting is displayed only when the resource prefix is applicable to at least one XFRM category configured to create an associated discussion thread.

The “Manage all prefix mappings” button provides direct access to the centralized mapping page.


This setting defines the global mapping for the resource prefix. A category-specific mapping can still override it.

Centralized mapping management​

All mappings can be managed from one page:

Admin control panel
→ Forums
→ XFRM thread prefix mappings


This page contains two separate sections.

1. Global mappings​

A global mapping defines the default thread prefix for each XFRM resource prefix.

Example:

• Windows → Windows
• macOS → macOS
• Linux → Linux
• Others → Others

The global mapping is used in every applicable XFRM category unless a category-specific rule overrides it.

For each resource prefix, you can:

• Select a specific thread prefix.
• Select “Use the category default thread prefix”.

2. Category-specific mappings​

Each applicable XFRM category receives its own mapping section.

Only categories configured with a destination discussion forum are displayed. The page also indicates the destination forum associated with each category.

For every resource-prefix/category combination, three behaviors are available:

1. Inherit the global mapping
   No specific rule is stored for this category. The global mapping is used.
2. Use the category default thread prefix
   The global mapping is intentionally ignored. The add-on uses the native “Automatically created thread prefix” configured in the XFRM category.
3. Select a specific thread prefix
   The selected thread prefix is used only for this resource prefix inside this particular XFRM category.

Category-specific selectors only contain thread prefixes permitted in the category’s destination forum.

This makes it possible to use different thread prefixes for the same resource prefix depending on the category or destination forum.

Example:

• Global rule: Windows → Windows
• Software category: inherit the global “Windows” mapping
• Premium Software category: Windows → Premium
• Archive category: use the native category default

Mapping priority​

When the add-on determines which prefix should be applied, it uses the following priority order:

1. Category-specific mapping, when one has explicitly been configured.
2. Global mapping assigned to the resource prefix.
3. Native XFRM category thread prefix.
4. No thread prefix if none of the previous prefixes is valid in the destination forum.

Selecting “Inherit the global mapping” continues to the global mapping.

Selecting “Use the category default thread prefix” intentionally skips the global mapping and immediately uses the XFRM category default.

Destination-forum validation and safe fallback​

XenForo can restrict thread prefixes to specific forums. A mapping that is valid in one forum may therefore be unavailable in another.

The add-on checks the destination forum before applying a prefix.

If the mapped prefix is unavailable:

1. The native XFRM category prefix is attempted.
2. If the category prefix is also unavailable, the discussion is saved without a prefix.

This prevents the add-on from assigning an invalid prefix to a discussion thread.

Category-specific mapping selectors are automatically filtered so they only display prefixes accepted by the relevant destination forum.

Global mappings can cover several categories and forums. If a global mapping is unavailable in one of those forums, the management page displays a warning and recommends creating a category-specific mapping.

Automatic synchronization​

The associated discussion prefix is automatically recalculated when:

• A new XFRM resource and its discussion thread are created.
• The resource prefix is changed.
• The resource is moved to another XFRM category.
• The associated discussion-thread relationship changes.
• A mapping is modified.
• The destination forum configured for an XFRM category changes.
• The native XFRM category thread prefix changes.
• An associated resource discussion is manually moved to another forum.
• A XenForo thread prefix is updated or deleted.
• An XFRM resource prefix is deleted.

When a resource discussion is manually moved, the add-on validates the mapped prefix against the thread’s new forum.

If the mapped prefix is not available there, the add-on uses a valid fallback or removes the prefix. If the discussion is later moved back to a compatible forum, the correct mapped prefix can be restored automatically.

Only linked XFRM resource discussions are processed. Normal forum threads are not affected.

Synchronizing existing discussion threads​

The mapping page contains a “Synchronize existing threads” button.

This can be used after:

• Installing the add-on on an existing community.
• Creating or modifying several mappings.
• Changing the prefixes allowed in a forum.
• Moving resources or discussion forums.
• Importing existing XFRM content.

The synchronization is processed through the XenForo job system instead of blocking the Admin control panel.

Resources are processed in batches of up to 100 items. The job can resume between executions and can be cancelled through XenForo’s job interface.

Saving modified mappings also queues synchronization automatically, so using the manual button is generally only necessary for verification or maintenance.

Mapping warnings and automatic cleanup​

The centralized page displays warnings when it detects situations requiring administrator attention, including:

• A global mapping pointing to a deleted thread prefix.
• A global mapping unavailable in one or more destination forums.
• A category-specific mapping pointing to a deleted thread prefix.
• A category-specific mapping unavailable in its destination forum.
• An orphaned mapping whose resource prefix or XFRM category no longer exists.
• A mapping that is no longer applicable to the selected XFRM category.

Orphaned mappings are removed when the mapping configuration is next saved.

When a mapped XenForo thread prefix is deleted, affected mappings are reset safely and discussion synchronization is queued.

When an XFRM resource prefix or category is deleted, its category-specific mapping records are also cleaned up.

Administrator permission​

Access to the centralized mapping page is protected by a dedicated administrator permission:

Manage XFRM thread prefix mappings

This is an administrator permission, not a front-end user-group permission.

It can be configured from the administrator account permissions in the Admin control panel.


Administrators without this permission cannot access or modify the centralized mapping configuration.

The native XFRM category setting is still supported​

The add-on does not remove or permanently replace XFRM’s native “Automatically created thread prefix” setting.

That setting remains available as a fallback.

It is used when:

• The resource prefix has no mapping.
• A mapping explicitly selects “Use the category default thread prefix”.
• The mapped prefix is unavailable in the destination forum.
• The resource does not have a native XFRM prefix.

This means the add-on can be introduced progressively without requiring every existing resource prefix to be mapped immediately.

Typical use cases​

This add-on is particularly useful when:

• Several resource types share one XFRM category.
• Several XFRM categories create threads in the same forum.
• A software category contains Windows, macOS, Linux and Android resources.
• A content marketplace uses different resource prefixes for different platforms or providers.
• The same resource prefix requires a different thread prefix in different categories.
• Existing resource discussions need to be updated after prefix rules change.

Installation​

1. Upload the contents of the add-on’s upload directory to the XenForo installation directory, or use XenForo’s archive installer.
2. Install [NC] XFRM Thread Prefix Mapper from the Admin control panel.
3. Verify that the relevant XFRM categories are configured to create discussion threads.
4. Edit an XFRM resource prefix or open Forums → XFRM thread prefix mappings.
5. Configure the desired global and category-specific mappings.
6. Save the mappings.
7. Optionally run “Synchronize existing threads”.

Tested on​

• XenForo 2.3.10
• XenForo Resource Manager 2.3.10

XenForo Resource Manager is required because the add-on extends its resource-prefix, category, resource-item and discussion-creation systems.

Language support​

English is included as the default add-on language.

You have 3 other’s language:
extras/NC_XFRMThreadPrefix_Francais.xml
extras/NC_XFRMThreadPrefix_Russian.xml
extras/NC_XFRMThreadPrefix_Turkish.xml

It can be imported into the French language from the XenForo Admin control panel.

Important compatibility note​

The add-on supports the native single-prefix system provided by XenForo Resource Manager.

Third-party multi-prefix add-ons are not required and are not currently supported.

This add-on does not:

• Add multiple prefixes to a resource or thread.
• Create resource prefixes or thread prefixes automatically.
• Modify ordinary non-XFRM discussion threads.
• Modify XenForo or XFRM core files.

Frequently asked questions​

Does it work when multiple resource types use the same forum?
—> Yes. This is one of the main purposes of the add-on. Each native resource prefix can generate a different thread prefix while all discussions remain in the same forum.

Does it update threads that already exist?
—> Yes. Use “Synchronize existing threads”. Mapping changes also queue an automatic synchronization job.

What happens if a mapped prefix is not allowed in the destination forum?
—> The add-on attempts to use the native XFRM category prefix. If that is also invalid or not configured, no prefix is applied.

What happens if a mapped thread prefix is deleted?
—> Affected references are reset safely and synchronization is queued. The management page can also report invalid or missing mappings.

Can one resource prefix use different thread prefixes in different categories?
—> Yes. Configure a global mapping, then add category-specific overrides where necessary.

Does it replace the native category thread-prefix setting?
—> No. The native XFRM setting remains the fallback and can also be selected explicitly for individual category mappings.

Does it affect categories that do not create discussion threads?
—> No. Categories without an associated discussion forum are ignored.

Does it support third-party multi-prefix add-ons?
—> No. The current version intentionally supports only the native XFRM resource-prefix field.

I want to clarify that the add-on comes from a forum I've since closed; the language translations are done by Google Translate because I’m French.