إعلان XenForo Release Edition 2.3.8 Preview

[Binkaddas]

XenForo Release Edition 2.3.8 Preview

What's new in 2.3.8 vs 2.3.7 (observed from your diffs)

1) Templates/Templater

• The template lexer adds support for the ?? (null coalescing) operator, enabling expressions like {$a?? $b} in templates.
• New template functionsare added (declared in Templater), including:
  • array_diff
  • array_reverse
  • array_sum

2) API (Search extensions)

New search-related components appear, eg:

• src/XF/Api/Controller/SearchController.php
• src/XF/Api/Controller/SearchesController.php
• src/XF/ControllerPlugin/SearchPlugin.php

These typically indicated extended/standardized search handling at the API level and via controller plugins.

3) New CLI rebuilds and background jobs

Added maintenance facilities:

• CLI rebuild commands:
  • RebuildMessageCounts.php
  • RebuildReactionScore.php
• New job:
  • src/XF/Job/MessageCount.php

4) Webhook criteria expansion

Webhook filtering criteria are extended (examples include):

• Post, ProfilePost, ProfilePostComment
• Report
• User, UserUpgrade
  ...providing more granular event filtering.

5) Vendor/dependency updates

There are meaningful updates under vendor dependencies (e.g., AWS SDK-related items, doctrine deprecation handling, CSS parsing libraries), suggesting 2.3.8 is more than a minor patch.

---

Recommendations for a NEW INSTALL

If your goal is a fresh install:

1. Do not use the 2.3.8 archive you provided for a clean install (missing install/ and entry scripts).
2. Use an official full package from a trusted source (ideally xenforo.com).
3. Post-install best practices:
   • Set correct permissions for data/and internal_data/
   • Enforce HTTPS and secure your web server rules (block direct access to internal_data)
   • Install add-ons/styles gradually and test compatibility

---

Recommendations for UPGRADING from 2.3.7 to 2.3.8

If your production site is on 2.3.7 and you want to upgrade:

Safety checklist

1. Full backs
   • Database
   • data/, internal_data/, add-ons, customizations
2. Test on staging first
   • Clone the site to staging and run the upgrade there before touching production
3. Confirm package type
   • If you're using an upgrade/patch package: copy only the integrated directories/files (eg, src/, js/, styles/, library/) per instructions
   • Avoid “blind overwrite” with an complete package
4. Verify add-on/style compatibility
   • Essentially anything touching templates, search, and webhooks
5. Run rebuild tasks where appropriate
   • Since 2.3.8 adds message count/reaction score rebuild utilities, consider running relevant rebuilds after upgrading

---

Critical notes

• Your archive identifies itself as “2.3.8 (Preview)” → preview buildings may change behavior and can be less stable than official releases.
• Because your 2.3.8 archive is not a full install, it’s:
  • Not suitable for fresh installations
  • Potentially fine for upgrading only if it is a legitimate, correct upgrade package
• Security: matching “common malware/backdoor patterns” against 2.3.7 did not show obvious suspicious deltasin the core. Still:
  • If the source isn’t official, you should verify checksums and/or scan with AV/IDS before production use.

 

[shqawe]

مشكور على الموضوع يا ابو محمد

وما اشوف في الترقية اي تحديثات تستاهل الترقية

وفيه شيء يخوف من هالترقية موضوع النقطة رقم 2 في توصيات الترقية يقولك جرب الترقية على نسخة من موقعك قبل الترقية للموقع الرئيسي

يعني ممكن يكون فيها مشاكل خصوصاً للي تراخيصهم منتهية او مركبين نسخ منزوعة.

فانصح اي احد يبي يرقي للنسخة 2.3.8 انه يجرب قبل ﻻيرقي واذا صمم يرقي ياخذ نسخة كاملة من الموقع يعني نسخة من ملفات المنتدى ونسخة من قاعدة البيانات خصوصا ً للاخوان اللي نسخهم ماهي مرخصة.

احترامي وتقديري
اخوك
شقاوي