Xenforo Core Full Package Nulled

Xenforo Core Full Package Nulled 2.3.6

No permission to download
XenForo 2.3.5 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.

In addition to the usual bug fixes, XenForo 2.3.5 includes a critical security fix for any customers making use of OAuth2 where client applications may be able to request unauthorized scopes. This will affect any customer using OAuth2 clients on any version of XenForo 2.3 prior to 2.3.5.

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.5 include:


The following public templates have had changes:

  • code_editor.less
  • connected_account_associated_x
  • connected_account_macros
  • core_button.less
  • editor_insert_gif
  • helper_js_global
  • login
  • passkeys_macros
  • post_article_macros
  • share_page_macros
  • style_variation_macros
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.


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.
  • Like
Reactions: mydavidmy
XenForo 2.3.4 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.

Some of the changes in XF 2.3.4 include:

  • Include embed.php in hashes.json
  • Fix error thrown when feed entry is missing an ID
  • Use AbstractCollection for type hint on addContentToBookmarks method
  • Fix deprecated usage of str_replace with API scopes
  • Improve PHP 8.4 compatibility
  • Output hsla in the color picker when an alpha channel is present
  • Ensure URLs are valid when analyzing image usage
  • Coerce nestable group to a number before peforming strict comparison
  • Gracefully handle guest username and style variation containing invalid UTF-8
  • Attempt to work-around abysmal Firefox form field retention heuristics
  • Gracefully handle when an avatar cannot be processed
  • Allow changing style variation when the previously selected style is forced to the default style
  • Increase date input width further to accomodate Firefox icon clipping
  • Fix editor autofocus behavior when in BBCode mode
  • Add a note about some permissions not being applicable to guests
  • Fix triggering Facebook embeds for document
  • Fix calculation of local load time from navigation timing API
  • Fix behavior of preview buttons
  • Consider read-only number-box inputs as disabled
  • Make required and recommended function checks more robust
  • Allow null unique ID when enqueuing a job later
  • Make report creation notifications easier to extend
  • Attempt to work around aggressive Firefox auto-complete heuristics when editing a user
  • Fix broken JS handlers when loading comments via AJAX
  • Fix an issue with editing newly translated phrases
  • Split ExifReader library out of attachment manager bundle
  • Attempt to work around aggressive Firefox auto-complete heuristics on control panel index
  • Fix number input buttons when step is set to any
  • Fix some icon usage analysis issues when editing and deleting editor drop-downs and BBCodes
  • Only record icon usage for active BBCodes and editor dropdowns
  • Omit itemid microdata attribute when there is no valid user
  • Ensure all control panel functionality is covered by permissions
  • Handle invalid multiquote input more gracefully
  • Attempt to avoid featured content carousel pager text overlap
  • Only try to remove double quotes from URL strings once
  • Set default color picker color to white instead of transparent
  • Fix some issues with the JS icon renderer and BBCode previews
  • Handle invalid session IDs more gracefully
  • Do not mark unhidden usernames as aria-hidden
  • Fix direction of back arrow on RTL languages
  • Improve text node handling in XF.setupHtmlInsert
  • Ignore Thumbs.db in style archive validator
  • Fix structured list icon end cell padding
  • Fix an issue with deferred resize event listener after autofocus
  • Skip any file duplicates when importing banned emails
  • Mark multiple consecutive asterisks as an invalid term word on MySQL full-text searches
  • Make the default table collation configurable
  • Fix calculation of report closure notifiable users
  • Ensure PayPal products are created with a unique ID.
The following public templates have had changes:

  • PAGE_CONTAINER
  • approval_queue_macros
  • carousel.less
  • core_input.less
  • fancybox.less
  • helper_attach_upload
  • lightbox.less
  • message_macros
  • profile_post_macros
  • structured_list.less
Where necessary, the merge system within the "outdated templates" page should be used to integrate these changes.
If you are a XenForo Cloud customer, your upgrade will be scheduled automatically.

Some of the changes in XF 2.3.3 include:

The following public templates have had changes:
  • PAGE_CONTAINER
  • account_banner
  • app_nav.less
  • conversation_message_macros
  • core_block.less
  • core_button.less
  • core_input.less
  • core_tab.less
  • editor_override.less
  • helper_js_global
  • member_view
  • passkeys_macros
  • post_macros
  • profile_post_macros
  • tag_macros
  • token_input
update to xf 2.3.2
update to xf 2.3.0
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.
Firstly, to clarify some concerns that have arisen:

1. If you did a normal upgrade (either uploading files or via your admin control panel) you do not need to manually edit any files to receive the security fixes.
2. If you upgraded to the initial 2.2.16 release, you are fully protected against the security issues that were being addressed.

Secondly, a second patch is being released to address some minor bug fixes that may not have been correctly applied when upgrading to XenForo 2.2.16. This is only applicable if you performed a normal upgrade to 2.2.16, and this patch is not security related or affected by the security fixes.

You can download that now from your customer area or perform a one-click upgrade through your admin control panel. You can go to Tools > Check for upgrades in order to see the second patch release.

If you are running XenForo Cloud, the fixes have been applied automatically.
As we get ever closer to the fabled "release candidate" stage and the eventual stable release, today we are releasing the eighth beta for XenForo 2.3! Nothing particularly noteworthy this week other than a number of bug fixes.

We strongly recommend anyone testing 2.3 during this beta period upgrade as each beta version is released.
Welcome to 2.3.0 Beta 7! Since our last release we have been mostly focusing again on bug fixes and stability, though we do have an interesting change to note related to multibyte strings, specifically URL romanization. If available, we now use the intl extension and perform a multi-layered process for normalizing and transliterating strings. This is now much more intelligent as it handles some special cases for certain locales (based on the default language of the forum).

We also have a new option for controlling the output of emojis in URLs. You can leave them URL encoded, remove them, or convert them to a string based on the emoji name. This also requires the intl extension.
Top