vBulletin 3.7.4 Released

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Scott MacVicar
    Former vBulletin Developer
    • Dec 2000
    • 13286

    vBulletin 3.7.4 Released

    vBulletin 3.7.4

    3.7.4 PL1 has been released!

    vBulletin 3.7.4 contains a number of bug fixes, details of which can be found in the bug tracker.

    The security fixes included in vBulletin the 3.7.3 PL release are also included in vBulletin 3.7.4.


    reCAPTCHA™ Changes

    From vBulletin 3.7.4 onwards a default key for reCAPTCHA™ is provided within the code, if no key is set and reCAPTCHA is the chosen method then this key will be used.

    Upgrading from Previous Versions

    3.7.4 is a maintenance release. We recommend that all customers running prior versions of vBulletin 3.7 upgrade to benefit from bug fixes and stability improvements.

    Full instructions for upgrading vBulletin are available here.


    PHP and MySQL Requirements

    Please note that vBulletin 3.7.x requires at least PHP 4.3.3 and MySQL 4.0.16 or later.

    However, we recommend that vBulletin 3.7.x is run on PHP 5.2.6 with APC (or a similar opcode cache) and MySQL 5.0.51 for best performance and stability.


    End of Life for PHP 4

    PHP 4 has now reached its end of life. We strongly recommend that customers update their servers to PHP 5.2.6 if they are still running PHP 4. vBulletin 3.7.x supports PHP 5 without any problems, though you may need to disable strict mode for MySQL, see here on how to enable 'force_sql_mode'.

    Note: We will continue to support PHP 4 in the vBulletin 3 series.


    Download vBulletin 3.7.4

    As usual, vBulletin 3.7.4 is available for all customers with valid, active licenses to download from the vBulletin Members' Area.

    vBulletin Members Area
    Scott MacVicar

    My Blog | Twitter
  • Scott MacVicar
    Former vBulletin Developer
    • Dec 2000
    • 13286

    #2
    Files Changed Since 3.7.3
    • /
      • ajax.php
      • faq.php
      • forumdisplay.php
      • group_inlinemod.php
      • index.php
      • member.php
      • moderation.php
      • profile.php
      • showthread.php
      • usercp.php
      • visitormessage.php

    • admincp/
      • misc.php
      • modlog.php
      • notice.php
      • passwordcheck.php
      • plugin.php
      • queries.php

    • archive/
      • global.php

    • clientscript/
      • vbulletin_ajax_threadslist.js
      • vbulletin_textedit.js
      • yui/animation (added)
      • yui/animation/animation-min.js (added)
      • yui/connection/connection-min.js
      • yui/dragdrop (added)
      • yui/dragdrop/dragdrop-min.js (added)
      • yui/yahoo-dom-event.js
      • yui/connection.js
      • yui/yahoo-dom-event/yahoo-dom-event.js

    • includes/
      • adminfunctions_options.php
      • class_bbcode.php
      • class_core.php
      • class_dm_user.php
      • class_dm_visitormessage.php
      • class_humanverify_recaptcha.php
      • class_postbit.php
      • class_profileblock.php
      • class_reportitem.php
      • class_upload.php
      • functions.php
      • functions_calendar.php
      • functions_faq.php
      • functions_user.php
      • init.php
      • cron/cleanup.php

    • install/ - all files
    Scott MacVicar

    My Blog | Twitter

    Comment

    • Scott MacVicar
      Former vBulletin Developer
      • Dec 2000
      • 13286

      #3
      You may discuss this release here:

      vBulletin 3.7.4 Release Discussion
      Scott MacVicar

      My Blog | Twitter

      Comment

      • Freddie Bingham
        Former vBulletin Developer
        • May 2000
        • 14057
        • 1.1.x

        #4
        Somehow, a serious, but not destructive bug worked its way into 3.7.4. After modifying a user in the UserCP, you will receive a database error when saving the user. I have updated the affected file, includes/class_dm_user.php, in the 3.7.4 download. If you downloaded 3.7.4 previous to this message, please download it again and replace the file.

        Comment

        widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
        Working...