Table of Contents

I no longer provide a script to upgrade from version 1.x to 2.x. It was becoming too difficult to assure the accuracy of the database changes. If you want to upgrade from 1.x, post a request in the support forum and I will help you do it.

Read the release notes for the list of changes.

Upgrading from 2.3.10 or later to the current release

The release notes indicate which files have changed. Upload those files.

Upgrading from 2.3.beta4 through 2.3.9

Upload to your server all files except those in directories: addons, install, upgrade.

Upload dbupdate.php from the upgrade directory to the TalkBack directory and browse to it. Delete it when the script finishes finishes.

If you are upgrading from version 2.3beta3 or earlier...

A number of changes have been made to many scripts and templates to improve security. If you have made any changes to the scripts or default templates, you will have to redo them in the new 2.3 files. You cannot mix any earlier version files with 2.3 files. Read all of the instructions before starting to upgrade.

  1. Download a backup copy of TalkBack from your server to your PC. Backup the TalkBack database and download it to your PC.
  2. Use the admin configuration settings panel to put TalkBack into maintenance mode.
  3. Delete the TalkBack directory and all of its sub directories from your server.
  4. Upload the files in all 2.3 directories except: addons, upgrade, install and language.
  5. Upload language/english.php or the latest version of the language you are using.
  6. If you are using any of the addon scripts, copy those from the 2.3 addons directory to the TalkBack directory on your server.
  7. In the backup copy of the config.php file that you downloaded earlier, insert above the closing ?>
    // Don't change below this line!!!!
    require_once 'includes/init.php';
  8. From the backup copy that you downloaded earlier, upload: config.php, styleCustom.css, any customized templates and my-english.php.
  9. Upload upgrade/dbupdate.php to the talkback directory. Browse to it. When it finishes, delete the script from your server.

    If you are upgrading from version 2.2.8 or earlier, continue. Otherwise skip to the last step.

  10. If you are using spam words filtering, rename the spamwords.php file on your server to my-spamwords.php. Check the new “Enable spam words checking” checkbox in admin configuration settings “Spam and Moderation Settings.”
  11. If you have modified the default templates (comments-display-tpl.php and comments-form-tpl-php), rename those files on your server (for example to: my-comments-display-tpl.php). Then change the file names in the admin configurtion settings section “Template File Names.” If you have not modified them, do nothing.

    If you are upgrading from version 2.1 or earlier, continue. Otherwise skip to the last step.

  12. If you have done any customization other than CSS changes read about the script changes. You will have to redo the template customizations using the new default templates as a base. It is possible that some of your customizations (such as deleting some elements from the templates) can now me made via the new configuration settings.
  13. New styles have been added to style.css. They specify the background images for Thickbox and the first page and last page links that were added to the comments template. If the path to your TalkBack directory is not /talkback/:
    • Download your styleCustom.css file from your server.
    • Copy the new styles (they are at the top of style.css) to your styleCustom.css file.
    • Change the path in the background image URL’s in styleCustom.css.
  14. Edit your config.php file:
    • Insert these lines into it:
      $config['tb_path']     = "/talkback/";
      $config['default_language']  = "english";
      $config['message_panel_tpl'] = "message-panel.php";
      $config['admin_email']       = "your email address";
    • Delete the $config['language_file'] entry.
  15. I have streamlined the insertion of the head section tags. Instead of copying the block of stylesheet and script tags into the head section of pages, you need now only insert one include statement in the head section.
    • Edit your pages that have comments. Replace the original TalkBack stylesheet links and script tag with:
      <?php include "relative path/head-inc.php"; ?>

      The relative path is to the TalkBack directory from the directory in which your page resides. if you are using any of the optional variables ($tb_template, $tb_closed or $language) they should also be inside the PHP tag.

    • Are you already using Thickbox, Greybox, Lightbox JS, any other “lightbox” or javascript library other than Jquery on your website? If so, read “Lightbox conflicts and problems” in the user guide.
  16. Rename the language/my-language.php file on your server to my-english.php. See the user guide > About language files if you want to use multiple language files.
  17. Upload populate-counts.php (in the upgrade directory) to your TalkBack directory and browse to it. It updates a comment count field in the new articles/page table. Delete the script from your server when it has finished.
  18. Review the new configuration settings and adjust them for your installation. Edit the preview panel configuration seting: change it from comments-preview.php to comments-preview-tpl.php.

    If you are upgrading from 2.0, continue. Otherwise skip to the last step:

  19. Edit the admin_date and comments_date configuration settings because the legal values changed in version 2.1. The old format string parameters will no longer work. The new parameters are preceded by a % sign. Read the user guide > Dates - formatting for full information.
  20. If your site is not in English you may want to edit the date_locale configuration setting. Read the user guide > Dates - language for more information.
  21. Browse the admin panels and comments pages to be sure everything looks okay. Enter some test comments and replies. Put TalkBack into operational mode if there are no problems. If you have any problems or questions, ask for help in the support forum.