Global Moxie

The “Fish and Chips” update is a bug-fix update and the third release candidate for Big Medium 2.

As noted in previous release announcements, Big Medium now requires Perl 5.6.1 or higher; if you’ve been running Big Medium on a server with Perl 5.6.0 or earlier, you’ll need to upgrade your Perl installation in order to continue. Not sure what version you have? Download the compatibility checker from the system requirements page.

• Complete list of changes

Get after it

Download the latest version of Big Medium here.

The download package includes complete installation instructions, including notes for upgrading from previous versions of the Big Medium 2 beta.

Shortcut instructions for upgrading from 2.0rc1 or 2.0rc2 and for upgrading from 2.0b50, b51 or b52 are provided below. (If you’re upgrading from a version prior to 2.0b50, please follow the full installation instructions in the download package; along the way, those instructions include special notes for upgrading.)

The Nitty Gritty

Here’s what’s new in this update:

• Fixed bug that could cause crash in search results page when the homepage's utility template contained UTF-8 characters.

• Fixed bug that could cause occasional crashes when building pages with Markdown-formatted text and UTF-8 characters.

• Fixed bug in copy-to-site feature that left the old publication date in place when setting the copy of a published page to unpublished status. (The updater script also cleans this up by resetting these pages' incorrect publication times.)

• Fixed bug that could prevent an import from completing for sites with duplicate filenames for document downloads.

• Fixed invalid HTML syntax in one-click editing toolbar for Windows servers.

Upgrading from Big Medium 2.0rc1 or 2.0rc2?

If you’re upgrading from v2.0rc1 or v2.0rc2, you can update to the new version by following the instructions below.

1. Set your FTP client to “plain text” or “ascii” mode.

2. Upload to moxiebin/Modules directory:

• BigMed.pm
• BigMed (directory and all contents)
• HTML (directory and all contents)

3. Upload to moxiedata/templates/site_templates/HTML directory:

• wi_htmlhead.tmpl
• wi_oneclick.tmpl

4. Run the updater

Browse to the bm-update.cgi file in your site’s moxiebin directory. For example:

http://www.example.com/cgi-bin/moxiebin/bm-update.cgi

This completes the update from 2.0rc1 or rc2.

Upgrading from 2.0b50 or later?

This update’s changed files are scattered far and wide throughout the installation, so you may find it simplest simply to follow the full installation instructions in the download package (along the way, those instructions include special notes for upgrading).

However, if you’re determined to upload only the changed files, and if you’re upgrading from v2.0b50, b51 or b52, you can update to the new version by following the instructions below. (For earlier versions, follow the full installation instructions in the download package; along the way, those instructions include special notes for upgrading.)

To upgrade from v2.0b50, b51 or b52:

1. Confirm the language setting for your site(s)

Your site’s language setting is in the “Documents and Page Header” screen of HTML preferences. The default is English. If your site is in a different language or if you have otherwise changed this setting, make sure that it is set to the correct language.

2. Set your FTP client to “plain text” or “ascii” mode.

3. Upload files to moxiebin directory:

Upload all moxiebin files except for the Modules and plugins directories. Be careful not to remove or replace bm-setup.pl.

4. Set permissions on moxiebin files.

This is for Unix servers only. (On Windows? Skip ahead to step 4.)

Set permissions on all files in the moxiebin directory, except for bm-setup.pl, to chmod 0755. Leave bm-setup.pl permissions as-is.

5. Upload to moxiebin/Modules directory:

• BigMed.pm
• BigMed (directory and all contents)
• CGI (directory and all contents)
• HTML (directory and all contents)
• Lingua (directory and all contents)
• Log (directory and all contents)
• Text (directory and all contents)

6. Upload to moxiedata/templates/cp_templates directory:

• screen_editor_menu.tmpl
• screen_help_markdown.tmpl
• screen_libeditor_menu.tmpl
• screen_moderate_menu.tmpl
• shell_cp_bottom.tmpl
• wi_pagenav_menu.tmpl
• wi_themes_preview.tmpl

7. Upload to moxiedata/templates/site_templates directory:

• base.css
• HTML/_tool_print.txt
• HTML/wi_htmlhead.tmpl
• HTML/wi_oneclick.tmpl
• HTML/wi_search_result.tmpl
• HTML/wi_search.tmpl
• JS (directory and all contents)
• RSS/wi_short_description.tmpl

8. Upload to moxiedata/support/assets:

• bm.js
• lightbox_sm.js

9. Upload to bmadmin/css directory:

• bigmedium_cp.css

10. Upload to bmadmin/js directory:

• bigmedium_cp.js
• bm-editor.js
• bm-theme.js

11. Upload to bmadmin/wysiwyg/editor/dialog directory:

• fck_paste.html

12. Change your FTP client to “automatic” or “binary” mode.

13. Upload to bmadmin/img directory:

• bmcp_default_theme.jpg
• favicon.ico

14. Upload to bmadmin/themes directory:

• _general (directory and all contents)

15. Run the updater

Browse to the bm-update.cgi file in your site’s moxiebin directory. For example:

http://www.example.com/cgi-bin/moxiebin/bm-update.cgi

This completes the update from 2.0b50 or later.

Tags: beta, bigmedium