XF XenForo 2.2.2 Released Full Nulled 2.2.3 Patch 1

XenForo 2.2.3 is now available for all licensed customers to download. We strongly recommend that all customers running previous versions of XenForo 2.2 upgrade to this release to benefit from increased stability.

In addition to the usual bug fixes and improvements, there is a database schema change which, in some circumstances, may take time to perform. If you are running a version of MySQL below 5.7 (or equivalent) and have a particularly large xf_thread table (several million records) then we recommend performing a CLI upgrade.

Some of the changes in XF 2.2.3 include:

• When sticking/unsticking the header, ensure that child controls are updated correctly.
• Prevent text overflow with unbroken character strings when using when using the article forum preview display.
• Ensure that the article cover image notice appears using the correct row styling and only in situations where it's potentially relevant.
• Fix PHP 8 compatibility issue relating to push notifications.
• Fetch the list of unviewable forums more efficiently when searching.
• Adjust the wording of the allowed attachment file extensions option to be clearer.
• Prevent an error if a thread shown in an article preview forum is missing the first post relationship.
• Remove superfluous curly brace in poll_macros template.
• Rename the "Spin box" phrase to "Number box".
• Fix N+1 query issues when viewing article forums.
• Fix typo in the "Editor background when focused" phrase.
• Ensure content types are phrased when displayed in the spam trigger log.
• Fix N+1 query issues when viewing attempting to find new profile posts.
• With development mode enabled, ensure we load the unminified version of the select2 library.
• When viewing a full page list of reactions for a profile post comment, ensure the breadcrumbs array is correctly formed and relevant.
• Change phrase edit fields to be normal text fields to workaround an issue with some devices accessing particular punctuation or characters.
• Ensure that line breaks within inline code blocks are not doubled.
• Optimize marking multiple forums read at once.
• Ensure that CLI requests receive reasonable request path values (for URL generation purposes)
• Adjust the "expanded articles per page" wording to be clearer that it applies to preview and expanded article forum views.
• Extend handling of pasting content from the Edge address bar to ensure only the URL portion is pasted.
• Correctly display a message when a suggestion has been closed (similar to when a suggestion has been implemented).
• Prevent an error from a race condition related to search forum cache generation.
• Display an icon for search forums when displayed in a sub-forum dropdown.
• Do not require full user management permissions for username autocompletion in the control panel.
• Prevent a JS error when using select-to-quote on a code tag.
• When autocompleting a username, maintain the highlighted component when escaped characters are used.
• For API actions that require guests to have a username specified (like posting a message), allow this to be globally set via the api_guest_username parameter
• Protect against a division by zero error when running jobs/cache rebuilds.
• Improve video validation for a specific type of MP4 video file.
• Ensure that when building URLs to the external data directory, we always build the URL relative to the root XF directory.
• Fix a situation where Safari would redirect to the service worker JS file.
• Prevent Safari from scrolling to the bottom of the page when autofocusing an input within a menu.
• Fix inconsistent behavior when parsing image tags and the base URL when importing from IPS.
• Expand the allowed format for StopForumSpam API keys.
• Tweak the labels on the account privacy page for more consistency.
• Increase the length of the discussion_type field for threads to account for long thread type IDs.
• Fix a typo in class name on the forum filters popup
• Adjust the description for the "Maximum expandable BB code block height" style property to better illustrate its behaviour.
• If the Clipboard API isn't available (due to lack of HTTPS for example), ensure "Copy to clipboard" buttons are hidden
• Ensure the mobile navigation trigger has an accessible name
• Use findRelativeIf within XF.Nestable to find inputs
• Fix phrase params with profile post and profile post comment content titles
• If the GIPHY API returns an error, don't throw an exception and instead return a prettier error message.
• Allow custom statement descriptors to be set for Stripe payment profiles.

The following public templates have had changes:

• PAGE_CONTAINER
• account_privacy
• app_nav.less
• bb_code_tag_img
• bookmark_macros
• core_button.less
• core_menu.less
• forum_filters
• message.less
• node_list.less
• node_list_search_forum
• poll_macros
• thread_type_fields_article
• token_input

Where necessary, the merge system within the "outdated templates" page should be used to integrate these changes.

Some of the changes in XF 2.2.2 include:

• Fix opt-in functionality of the entity changelog behavior
• Properly sort columns for forum default sort orders
• Handle heading BB codes without a type option
• Apply base URL to relative notice display images
• Do not escape moderator log list entry action texts after stripping tags
• Catch class load errors when applying session activity details on PHP 7+
• Throw exceptions correctly in the alert API controller.
• Ensure that the "no matches" message in article preview forums always spans the full width.
• When merging posts, force the target post to be visible if it will become the first post of the thread.
• Disable user mention parsing within custom BB codes that disable auto linking or BB code parsing
• When setting a default title for avatars, do not override a custom version
• Use the correct forum type node icon in the sub forum menu/list
• Fix typo that prevents alerts from being marked as unread if a confirmation message is shown.
• Ensure the UI properly respects an explicit request to mark an alert as read or unread when a confirmation message is shown.
• Fix StylePropertyMap entity ParentProperty relation conditional
• Fix dynamic redirects for alert and conversation read state toggles
• Correct a few typos in some CLI commands
• Fix invalid format specifier in error trace argument builder
• Break the phrase import query into chunks to avoid a MariaDB performance regression.
• Fix a MySQL 8.0.22 incompatibility with the 1.x to 2.x upgrade code (related to phrase renames).
• Allow previewing to work when composing entirely in the BB code editor
• Respect API permission bypass when checking alert viewability
• Fix some sort callbacks on PHP 8+
• Fix PHP 8 compatibility in XML utilities
• When a username change request requires moderator approval, log the IP the request was received from.
• Remove user profile banners when banning users with the spam cleaner
• Prevent an error caused by GCM push notification subscriptions.
• When quoting a post, do not include quote tags if they would be empty
• Give MySQL an index hint to improve performance of newest thread API requests (with no other filters)
• Prevent an error in the structured data of questions if the plain text version contains no content
• Fix issue that prevented the RTE from being programmatically focused
• Relax validation of URLs in BB code content as users may submit URLs that are missing URL encoding in some scenarios.
• When a profile banner is applied, ensure that the text stroke applied to the username respects user group-based username CSS modifications.
• Prevent an error when rendering article previews if the thread's first post is not set correctly
• Prevent double URL autolinking when an unfurled URL contains a URL within it.
• Ensure that Facebook embeds are always responsive.
• Fix permission check when removing tags with the tag changer service
• Do not grant the change username permission to the unconfirmed user group when upgrading to 2.2 (from 2.1 or earlier). For existing upgrades, remove the permission from this group explicitly. If you wish to allow unconfirmed users to change their usernames, the permission will need to be explicitly re-added after upgrading to 2.2.2.
• Ensure that the RTE preview tab does not expand unexpectedly if there are no right aligned toolbar icons.
• Fix typo in overlay click options list.
• Ensure that BB code blocks (code, quote, and similar) do not appear behind floated images.
• Prevent an error when fetching a post that contains an embedded video via the API.
• Prevent invalid characters from being displayed in certain cases when highlighting search results.
• When clicking "more options", ensure that thread type-related fields don't come from a saved draft
• Render push templates with the receiver as the visitor
• Apply a content type to the username change entity.
• Ensure that banned users do not receive an activity summary email.
• Fix a situation where the "display children in navigation" option for node-based navigation entries does not work.
• Apply explanation tooltips more consistently to the account header section.
• Allow Google Analytics 4 measurement IDs as well as Universal Analytics property IDs.
• Allow passing through JS options for sticky submit rows
• Provide an option to use the given user's language when calling \XF::asVisitor()
• Ensure post ad positions are retained in article template extensions, and exclude them from appearing in article forums with an expanded display
• Disable auto closing HTML tags in the template modification find and replace inputs.
• When importing from another XF installation, properly rewrite quotes which are missing a member ID

The following public templates have had changes:

• PAGE_CONTAINER
• _help_page_bb_codes
• account_alert_toggle
• account_alerts_mark_read
• attachments.less
• bb_code.less
• codemirror.less
• conversation_mark_unread
• core.less
• core_bbcode.less
• editor.less
• editor_base.less
• fa.css
• font_awesome_setup
• forum_post_thread
• member.less
• member_macros
• member_tooltip
• member_tooltip.less
• member_view
• message.less
• node_list.less
• node_list_forum
• notice_macros
• post_article_macros
• post_macros
• setup_fa.less
• thread_type_fields_poll
• thread_view_type_question

Where necessary, the merge system within the "outdated templates" page should be used to integrate these changes.

XenForo 2.2.1 is now available for all licensed customers to download. We strongly recommend that all customers running previous versions of XenForo 2.2 upgrade to this release to benefit from increased stability.

Most importantly, this release fixes two potential security vulnerabilities in XenForo.

The issues are XSS vulnerabilities. XSS (Cross Site Scripting) issues allow scripts and malicious HTML to be injected into the page, potentially allowing data theft or unauthenticated access.

XenForo extends thanks to security researcher Vincent ibn Winnie for reporting the issues.

We recommend doing a full upgrade to resolve the issues, but a patch can be applied manually. See below for further details.

Some of the other changes in XF 2.2.1 include:
Fix erroneous phrase in success alert when posting a reply before registering
Ensure that service worker offline caching does not trigger session activity updates (or various other assertions)
Allow insertTable and xfBbCode commands to be added to custom dropdowns. Prevent paragraphFormat command being added.
Empty the mail queue when upgrading to 2.2 due to underlying Swiftmailer changes and catch errors (as well as exceptions) during mail sending to prevent queue items from becoming stuck.
Only bail out of toggling the editor preview when the editor is empty if you are not already previewing.
Fix displaying emoji phrases when the shortname contains an accented character and fix issue with accented shortname emojis from being converted.
Bail out of matching a URL to BB code media sites if the string matches censor words.
More consistently apply permission dependencies when passing from global to content-level permissions. Display permission changes due to failed dependencies when analyzing.
Expose unread state for conversations and conversation messages
Bypass global visibility check when trying to validate usernames for registration
Add missing phrases when Gravatar rebuild is run.
On the registration form, update the username field's explain text as usernames can be changed now
Ensure article preview images aren't underlined when hovered over
In the RTE, do not parse for emojis when smilies are disabled. This is consistent with how BB code is normally rendered.
Ensure that Attachment::getDirectUrl only returns raw display URLs when the attachment is viewable
Remove content voting links from HTML if the visitor cannot use them
Apply width: auto to the small logo to ensure it maintains the correct aspect ratio when resized
Fix email sharing link
Add PHPDocs to noPermission() and notFound() controller methods
The following public templates have had changes:
alert_post_pre_reg
app_nav.less
attachment_macros
content_vote_macros
message.less

Today, after a refreshingly short beta and release candidate phase, we are excited to announce that XenForo 2.2.0 is now prepared, seasoned, baked and served, replacing XenForo 2.1.11 as our primary supported XenForo version.

This release adds a collection of great new features to XenForo, including the ability to repurpose forums as article repositories, a new way to encourage guest users to register, a progressive web app and a completely redesigned rich text editor. Check out the following list for some highlights:

• Forum and thread types system
• Updated rich text editor
• User profile banners
• Username change requests
• Search forums
• Forum SEO controls
• Writing before registering support
• Progressive web app
• Activity summary emails
• Style archive import and export
• REST API additions
• Profile post attachments

This is not an exhaustive list of what's new in 2.2, and you can read more about the above and other new changes/improvements features in the Have you seen...? forum.

We have also added preliminary support for the upcoming major release of PHP 8.0.

Today we continue the release candidate stage of XenForo 2.2 with Release Candidate 2. We recommend that all customers running previous 2.2 versions upgrade to this release.

This release is similar to the previous betas, but indicates that we are now a step closer to the stable 2.2.0 release. This is still considered a pre-release version, so we do not recommend running it in production and ticket support for this version is not yet available.

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.

Today we're happy to announce the next step towards a stable and supported release of XenForo 2.2 by moving onto the "release candidate" stage. We recommend that all customers running previous 2.2 versions upgrade to this release.

This release is similar to the previous betas, but indicates that we are now a step closer to the stable 2.2.0 release. This is still considered a pre-release version, so we do not recommend running it in production and ticket support for this version is not yet available.

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.2. 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.2; 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.2.

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.

After last week's Wednesday-which-was-sort-of-Tuesday-a-bit release, we are back on our regular Tuesday release cycle with 2.2.0 Beta 6. We are hopeful that this may be our final beta release before we move to a Release Candidate stage.

We strongly recommend anyone testing 2.2 during this beta period upgrade as each beta version is released.

More specific details regarding bugs fixed in this release can be found in the resolved bugs forum.

This past Monday was a bank holiday in the UK, so as far as the working week goes, today is Tuesday, which means it's time for Beta 5. This release fixes a number of bugs found since the previous release.

We strongly recommend anyone testing 2.2 during this beta period upgrade as each beta version is released.

More specific details regarding bugs fixed in this release can be found in the resolved bugs forum.

Today, we continue the beta stage of XenForo 2.2 with Beta 4. This release fixes a number of bugs found since the previous release.

We strongly recommend anyone testing 2.2 during this beta period upgrade as each beta version is released.

More specific details regarding bugs fixed in this release can be found in the resolved bugs forum.

This is beta software. It is not officially supported.
We do not recommend running it in production.

It's been a week since our last beta release, so today, in the interest of maximising the time customers get to test the software before it becomes our supported version, we're rolling up all the changes we've made since then and calling it XenForo 2.2.0 Beta 3. We have been concentrating mostly on the core code during this time, so this release includes changes solely to XenForo itself with the exception of a bug fixed in Enhanced Search.

We strongly recommend anyone testing 2.2 during this beta period upgrade as each beta version is released.

Specific details regarding bugs fixed in this release can be found in the resolved bugs forum.