Content BBCode 2.1.1

2.1.1 (2026-10-11)​

• declare that the add-on has no secret settings, via the hampel_admin_api_redaction code event - no effect unless an add-on that defines that event is installed

2.1.0 (2026-09-26)​

• requires XenForo 2.2.0 or later - XenForo 2.0 and 2.1 are no longer supported
• fix a TypeError which prevented a post being saved when its [xfmg] link text began with formatting, eg [xfmg=media,1][b]text[/b][/xfmg]
• fix [search] search terms: a term given in the option keeps its spaces, terms are no longer encoded twice, and Google searches no longer contain HTML entities
• fix [search=tag] links, which were built from the encoded search term
• fix the [xfmg=thumb] fallback link shown to visitors who cannot view the media item
• fix [prefix] and [tag] link text being escaped twice
• [xfmg] link text now renders nested BB code
• a search term given in the [search] option may now contain commas
• every tag now renders a plain link in signatures and emails (the simple and email renderers), as [thread] and [post] already did

2.0.3 (2025-12-11)​

• run enqueuePostUpgradeCleanUp during upgrades if we're running XF2.3+

This is a minor bugfix to resolve an error which can occur when someone uses the [XFMG=thumb] tag when XFMG is not installed.

• re-release with new addon id - changed addon title from "[thread] and [post] BBCode" to "Content BBCode"
• added SEARCH bbcode
• added TAG bbcode
• added XFMG bbcode
• added FORUM bbcode
• added PREFIX bbcode
• added RESOURCE bbcode
• tested on XF v2.0 and v2.1

• remove link class and target attributes when using SimpleHtml or EmailHtml based renderers

Note that upgrading from v1.0.0 is not supported, to upgrade to v1.0.1 first uninstall v1.0.0 and remove the addon files from the file system before installing v1.0.1 - no data will be lost. This limitation does not apply to v1.0.0a

Same version, new addon_id.

If you already have v1.0.0 installed, there is no need to upgrade. There is no new functionality in v1.0.0a. New installations should use this v1.0.0a version to ensure compatibility with future releases.

Due to the change in addon_id, upgrading from v1.0.0 to v1.0.0a is not supported - but there is no data stored with this addon, so simply uninstalling v1.0.0 and removing the old addon files from the filesystem before installing v1.0.0a will be sufficient.