Global Moxie

The "JP Is Forty" beta update fixes minor issues in the rich-text editor and makes the site importer add all imported images, documents and people to the media library. Specifically, the rich-text editor fixes are:

• In Internet Explorer, clicking anywhere in the edit field now gives you the edit cursor; previously you had to click in a line of text (or, in the case of empty fields, on the very first line of the field).

• The right-click menu has been re-enabled on plain text, allowing you to cut, copy and paste via the contextual menu.

Get after it

Download the latest version of Big Medium here.

Please note: This update contains a considerable number of JavaScript updates, some of which may not be updated in your browser by a simple page refresh. Please have all of your organization’s editors follow these browser update instructions.

The download package includes installation instructions, including info for upgrading from previous versions of the Big Medium 2 beta. If you’re upgrading from 2.0b30 or later, see the shortcut instructions below:

• Upgrading from 2.0b39?
• Upgrading from 2.0b37 or b38?
• Upgrading from 2.0b30 through b36?

Upgrading from 2.0b39?

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

1. Upload files to moxiebin/Modules

Upload these files via “plain text” or “ASCII” FTP mode in the moxiebin/Modules directory, replacing the old files of the same name:

• BigMed.pm
• BigMed/ImportV1.pm

2. Upload files to bmadmin/wysiwyg

Upload these files via “plain text” or “ASCII” FTP mode in the bmadmin/wysiwyg directory, replacing the old files of the same name:

• bmconfig.js
• editor/css/fck_editorarea.css

3. 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

4. Ask editors to clear browser cache

Please ask all of your site’s Big Medium editors to follow the browser update instructions.

This completes the update from 2.0b39.

Upgrading from 2.0b37 or 2.0b38?

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

1. Upload files to moxiebin/Modules

Upload these files via “plain text” or “ASCII” FTP mode in the moxiebin/Modules directory, replacing the old files of the same name:

• BigMed.pm
• BigMed/App/Web.pm
• BigMed/App/Web/Themes.pm
• BigMed/Content.pm
• BigMed/Format/HTML.pm
• BigMed/ImportV1.pm

2. Upload files to bmadmin/js

Upload these files via “plain text” or “ASCII” FTP mode in the bmadmin/js directory, replacing the old files of the same name:

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

3. Upload files to bmadmin/wysiwyg

Upload these files via “plain text” or “ASCII” FTP mode in the bmadmin/wysiwyg directory, replacing the old files of the same name:

• bmconfig.js
• editor/css/fck_editorarea.css

4. Upload file to moxiedata/templates/cp_templates

Upload this file via “plain text” or “ASCII” FTP mode in the moxiedata/templates/cp_templates directory, replacing the old file of the same name:

• screen_themes_remove.tmpl

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

6. Ask editors to clear browser cache

Please ask all of your site’s Big Medium editors to follow the browser update instructions.

This completes the update from 2.0b37 or 2.0b38.

Upgrading from 2.0b30 through b36?

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

1. Update bmadmin/index.html

Inside the bmadmin directory, locate the file named index.html. In a text editor like Notepad or BBEdit, open the index.html file in the bmadmin directory on your local hard drive. You must update two URLs in this file to reflect locations on your web server. The domain names that you use should be the same as the ones you use in the “Settings>Big Medium Server Info” screen.

The first URL is marked with this comment in the file:

*******************************************************************
UPDATE THE “ACTION” URL TO POINT TO THE DOMAIN WHERE BIG MEDIUM IS
INSTALLED. FOR EXAMPLE:
http://www.example.com/cgi-bin/moxiebin/bm-login.cgi/login-verify
*******************************************************************

and again:

*******************************************************************
UPDATE THE “HREF” URL TO POINT TO THE DOMAIN WHERE BIG MEDIUM IS
INSTALLED. FOR EXAMPLE:
http://www.example.com/cgi-bin/moxiebin/bm-login.cgi/login-reminder
*******************************************************************

2. Upload in “plain text” or “ASCII” FTP mode:

• moxiebin/bm-library.cgi (Unix: set permissions to 0755)
• moxiebin/Modules/BigMed.pm
• moxiebin/Modules/BigMed (directory and contents)
• moxiedata/templates (directory and contents)

3. Upload in “binary” or “automatic” FTP mode:

• moxiedata/support/assets (directory and all contents)
• bmadmin (directory and all contents)

4. Clear browser cache

Before running the updater, please follow these browser update instructions.

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

6. Ask other editors to clear browser cache

Please ask all of your site’s Big Medium editors to follow the browser update instructions.

This completes the update from 2.0b30 or later.