Dont forget read our Rules! Also anyone caught Sharing this content will be banned. By using this site you are agreeing to our rules so read them. Saying I did not know is simply not an excuse! You have been warned.
XenForo 2.3.2 is now available for all licensed customers to download. We strongly recommend that all customers running previous versions of XenForo 2.3 upgrade to this release to benefit from increased stability.
One-click upgrade to XenForo 2.3.2
Directly from your admin control panel
If you are a XenForo Cloud customer, your upgrade will be scheduled automatically.
Some of the changes in XF 2.3.2 include:
Make PCRE character class check more robust.
Do not attempt to redefine UTF-8 string shim functions if they already exist
Rename search forum node type handler as expected
Fix utf8_isASCII return type
Fix an issue where the batch size for search rebuilds could grow unbounded
Strip BBCode from trending content article displays
Fix a regression with PWA orientation/screen rotation
Set recommended PHP version dynamically
Fix profile post position tracking
Use absolute URLs in approval item emails
Fix behavior of API keys with all scopes allowed
Fix thread context support for featured and trending widgets
Apply inline style to document.head correctly
Fix type error for file clean counts.
Attempt to have Cloudflare Rocket Loader automatically ignore scripts
Don't try to ping IndexNow if no API key is set
Gate search engine indexing settings for threads behind their own permission
Fix error on shared IPs list when matching user has been deleted
Allow the variation menu to open above fixed notices
Fix saving permissions from the edit user page
Fix passing \DateTime objects into \XF\Language::getDateTimeParts
Use XF custom events for overlay and transition events
Hydrate user relations when setting up base user
Redirect to the first active option group when viewing an option
Fix behavior of search short-name conversion
Handle older SMTP option values more gracefully
Fix responsive sidebar margins
If a user can see the thread created by a report, respect their auto watch preference
Mark threads as nofollow if they are non-indexable
Support WebP images when uploading images for featured content
Address several issues with XF.ajax
Address even more one-click upgrade issues when caching is enabled
Fix attachment list filter bar dates being displayed in wrong timezone
Fix using hotkeys to submit a message in the plain text editor
Fix event handling on auto-complete autosubmission
Fix importing webp smilies
Fix implicit join behavior of finder order clauses
Fix addon_get_install_data code event description
Only process the color scheme mixin when variations are enabled
Position BBCode quote expansion link at bottom of quote
Fix some issues when toggling variations when an active variation is selected
Pass handler in params when rendering thread edit extra data templates
Include type data definitions when rendering thread edit extra data templates
The following public templates have had changes:
PAGE_CONTAINER
app_body.less
bb_code.less
embed_view
featured_content_edit
helper_js_global
helper_thread_options
page_view
payment_initiate_twocheckout
profile_post_macros
service_worker_offline
setup.less
style_variation_macros
thread_list_macros
trending_content_item_thread
two_step_totp
Where necessary, the merge system within the "outdated templates" page should be used to integrate these changes.
As always, new releases of XenForo are free to download for all customers with active licenses. You may now upgrade from your admin control panel or grab the new version from the customer area.
Current requirements
Please note that XenForo 2.3 has higher system requirements than earlier versions.
The following are minimum requirements:
PHP 7.2 or newer (PHP 8.3 recommended)
MySQL 5.7 and newer (Also compatible with MariaDB/Percona etc.)
All of the official add-ons require XenForo 2.3.
Enhanced Search requires at least Elasticsearch 7.2.
Installation and upgrade instructions
Full details of how to install and upgrade XenForo can be found in the XenForo 2 Manual. We strongly recommend upgrading directly from within your control panel.
It's time to party like it's 20222023 2024! Today we are very pleased (and relieved) to announce the stable release of XenForo 2.3.0 and our official add-ons. It has been a long time coming so we thank you for your patience and support.
There are a myriad of new features and improvements. Here's a brief overview of our favourites:
Style variants with Dark mode
Improved performance
Featured content
Image optimization
Automation with webhooks
SSO with OAuth2
Passwordless logins with passkeys
Trending content
This is not an exhaustive list of what's new in 2.3, and you can read more about the above and other new changes/improvements features in the Have you seen...? forum.
As always, new releases of XenForo are free to download for all customers with active licenses, who may now grab the new version from the customer area or upgrade from your Admin control panel (Tools > Check for upgrades...).
Today we are releasing XenForo 2.3.0 Release Candidate 5. While the majority of this release is focusing on bug fixes and stability, there are a few noteworthy changes.
Automatic legacy file clean up
XenForo installations after upgrading to XenForo 2.3 will have a number of files sitting in the file system which are no longer used. Any XenForo installation that has been around for a while, will to a lesser extent, have a similar issue. These files on their own shouldn't present any issue, but at the same time, keeping them around doesn't make much sense either.
There are three approaches to cleaning up legacy files automatically.
During one-click upgrade
One-click upgrades now have a special step for removing files that were present in the version you are upgrading from, which are no longer present in the version being installed. We already know we have write access to the files in your file system at this point so there should not be any issue in deleting these files in most cases.
During manual upgrades
After each upgrade, we also enqueue a job to do a file clean up based on a list of files enumerated from the hashes.json file. Anything in your src/vendor, src/vendor-patch and src/XF directory that is not listed in hashes.json will be removed automatically if possible. If it is not possible, we will log an error in your server error log.
By running a command
If write access is an issue, you can log in to your server shell/CLI and simply run the following command:
Bash:
php cmd.php xf:file-clean-up XF
As long as the CLI user has write access to your XenForo directory, the old files will be removed.
Cleaning up files manually
If all else fails, and you still wish to delete legacy files, we recommend the following approach:
Close your forum
Delete the contents of the following directories:
src/vendor
src/vendor-patch
src/XF
Re-upload the files from your current release
Cleaning up files for official add-ons
We will automatically attempt to clean up files for official add-ons as well after each upgrade. Again, if we run into write issues during the clean up process, an error log will be logged in your server error log. You can run the same command listed above (with either XFRM, XFES, or XFMG instead of XF as an argument), or follow the manual clean up steps above for the relevant add-on under src/addons.
Cleaning up files for third party add-ons
Developers who wish to trigger an automatic clean up of their own files, can do so by calling the following from within their add-on Setup class in the postUpgrade method:
PHP:
$this->enqueuePostUpgradeCleanUp();
Trending content support for add-ons
Starting with Release Candidate 5, we have added support for trending content to XenForo Resource Manager and Media Gallery.
Persistent file names for attachments
We have changed the way that file names for attachments are saved on the file system. Each attachment will now get a random file_key value, which is used to determine the file name on the file system. For older attachments this will default to the current file_hash value. The primary driver for making this change is so that the URL or path to specific attachments or thumbnails will no longer change after being optimised (which would change the file_hash value, and therefore the file name).
And that's all for this week. More specific details regarding bugs fixed in this release can be found in the resolved bugs forum.
This is pre-release software. It is not officially supported.
We do not recommend running it in production.
Please remember that this is pre-release software. It contains known bugs and incomplete functionality. We do not recommend running pre-release software in a production environment, and support is limited at this time to questions here on the community forums.
Add-ons and custom styles may be broken after upgrading to 2.3. You must test your add-ons thoroughly or look for updates. Be especially careful with add-ons that cover similar features to ones that are added to 2.3; these may conflict with the core XenForo data. If data conflicts are found, they will need to be resolved in a new add-on release or by removing the add-on before upgrading to 2.3.
If you choose to run pre-release software, it is your responsibility to ensure that you make a backup of your data. We recommend you do this before attempting an upgrade. If in doubt, always do a test upgrade on a copy of your production data.
To address a backwards compatibility issue with some add-ons, we are today releasing XenForo 2.3.0 Release Candidate 4. If you are running Release Candidate 3 already we encourage you to upgrade as soon as possible. If you were previously affected by issues with certain add-ons or experience other issues, please let us know via a bug report in the first instance.
This release also fixes the issue with admin search returning an error.
Shortly after the release of Release Candidate 1, we identified an issue related to editing node-like permissions. A very minor bug was surfaced by the changes today. Specifically one of our view class names was using a \ instead of a :
Due to a localised shortage of version numbers (we cannot increment the version to a patch release for release candidates) we have released Release Candidate 2 to address this.
