The big news in the web-design world this week is the release of
Firefox 3. Big Medium 2.0.2 keeps pace with the scrappy new browser
by patching some significant compatibility bugs under the new Firefox. If you’re
planning to upgrade to Firefox 3 — and why wouldn’t you? — this update is
highly recommended.
Safari users get some love, too. Big Medium’s WYSIWYG rich-text editor is
now available in Safari 3.0 and later, as well as all of the previously
supported browsers.
The rich-text editor also gets some shiny new features, including full-screen
editing and a new “show blocks” mode for reviewing document structure.
Plus: Lots and lots of other changes and a slew of bug fixes.
Go get it
Download the latest version of Big Medium here.
The download package includes complete installation instructions, including
notes for upgrading from previous versions of Big Medium.
Shortcut instructions for upgrading from 2.0 or 2.0.1 are
provided below. (If you’re upgrading from a version prior to 2.0,
including a Big Medium 2.0 beta version or release candidate,
please follow the full installation instructions in the download package;
along the way, those instructions include special notes for upgrading.)
The nitty gritty
New features
Big Medium’s WYSIWYG rich-text editor is now available in Safari 3.0 and
later, in addition to other previously supported browsers.
The rich-text editor now offers a full-screen mode and also a “show blocks”
mode to review the content’s HTML block elements while still editing in
rich-text mode.
Added option to the “Images” screen of sites’ HTML preferences
to enable/disable image enlargement for non-gallery images for the entire
site or for individual sections.
Added a new link-sorting criterion, “first published,” to allow
earliest-first sorting by publication date.
Added “Check for update” option in the “Settings” menu of the Big Medium
control panel so that you can quickly find out if there’s a new version
of Big Medium available.
Changes
In the <%navigation%> and <%subnavigation%> widgets, sections
containing subnavigation menus now receive the bmn_parent class and
may be styled via the li.bmn_parent CSS selector.
The rich-text editor now has a separate “blockquote” button to distinguish
quotes from simple indentation.
Rich-text editor dialogs now open in lightbox-style windows instead of
pop-ups. Looks nicer, works faster.
Transitions between slideshow images are now much faster; the animation
resolves more quickly, and height and width are adjusted simultaneously.
Search results no longer automatically direct you to the URL if there’s
just one search result, if that URL is an external link or a document (this
redirect still occurs when it’s an internal link).
E-mail alerts for new comments now include the site name in the subject
and intro text.
Tab labels are more descriptive in the dialog for attaching
authors, images, documents, etc. to content. Instead of just “New” and
“Library,” the tabs now say “New image” and “Image library,” for example.
When adding an author to a page, the “add author” dialog now opens in the
“People library” tab instead of the “New person” tab.
Image numbers in gallery slideshows no longer use English, in
order to be more internationally friendly. Instead of “Image 2 of 10,” for
example, it displays “2/10”.
Added an atom:link rel=”self” tag to RSS feeds to make the feed easier
to cache and improve portability, per the
RSS board’s best practices recommendations.
The “include related links with link text” option for the <%links%>
widget now appears in the “Widget: links” panel instead of the “General”
panel of the “Links” HTML preferences.
Big Medium now accepts UNC-format filepaths
(e.g. \\drivename\path\to\directory) for Windows servers.
During Big Medium server setup, the setup wizard now requires that
you use the same domain name for both the bmadmin and moxiebin URLs.
Bug fixes
Fixed bug that prevented the WYSIWYG CSS style editor from working in
Firefox 3.
Fixed bug that prevented the rich-text editor’s “paste from word” feature
from working in Firefox 3.
Fixed bug that could cause a crashing error in some page-builds, particularly
for search result pages, in servers running Perl 5.8.0.
Fixed bug that prevented some Windows servers from saving data files.
Fixed bug that displayed the “add a comment” link on pages that have
comments but where comments are closed. (For pages that already have
comments when you upgrade to this version, the link will still be
displayed until a comment is added, deleted or edited on the page.)
Fixed several bugs related to opening new windows when the “new windows”
option is selected for external links:
New window now opens for <%authorlink%>, <%spotlightimage%> and
<%bigmedium%> widgets, as well as links in comments and search
results, when appropriate.
Fixed bug that caused all new-window links to fail to open a new
window when the Big Medium-powered site was in a window that
had itself been opened for a new-window link. (Big Medium always
tries to use the same target window to open external links. However,
when a Big Medium site was opened in that window, the target window
was not changed to another window, so the links incorrectly opened in
the same window as the Big Medium site.)
New windows are now properly opened for aliased sections in:
<%navigation%><%subnavigation%><%sitenamelink%><%sitelogo%><%homelink%><%sectionlink%><%mainsectionlink%><%parentlink%>
Fixed bug under Internet Explorer 6 that could cause JavaScript errors
when opening a link in a separate window when that window already has
a page from another website domain open.
If a new window is blocked by a pop-up blocker, Big Medium will
still try to open the window via the browser’s default
target behavior
Fixed bug that prevented link images for link pages from opening in a new
page even when the individual link is specifically set to open in a new
window.
Fixed bug that caused the edit screen in some browsers, notably Internet
Explorer, to break when pullquotes, author blurbs or media captions included
HTML forms. The edit screen no longer previews these text elements if they
contain HTML forms or scripts.
In the base styles for public sites, added a workaround for a Mozilla bug
that adds borders to hidden fields when you apply styles to the input css
selector.
Fixed bug that could cause extra space to appear at the top of the
navigation widget in Internet Explorer.
Fixed bug in image enlargement that could cause Safari to open enlarged
images in the incorrect size.
Fixed bug in captions of enlarged images under Internet Explorer, which
caused apostrophes to display incorrectly as '.
Fixed bug under Internet Explorer that prevented the URL from appearing
as a tooltip for hotlinked images.
Fixed bug that prevented custom translations of Big Medium’s JavaScript
text from applying changes to the “high/low priority” slider text and
the mini-library “Find” text.
Fixed bug that caused field-validation error messages to be badly formatted
for directory path fields.
Fixed formatting problem (too many line breaks) in the help text for the
server path fields in the Big Medium setup wizard.
Upgrading from Big Medium 2.0 or 2.0.1?
Important: After upgrading, clear your browser cache, and
be sure to ask all other editors to do the same.
If you’re upgrading from v2.0 or v2.0.1, you can update to the new
version by following the instructions below. (If you’re upgrading
from a version prior to 2.0, including a Big Medium 2.0 beta version
or release candidate, please follow the full installation
instructions in the download package; along the way,
those instructions include special notes for upgrading.)
To upgrade from v2.0 or v2.0.1:
1. Set your FTP client to “plain text” or “ascii” mode.
2. Upload to moxiebin/Modules directory:
BigMed.pmBigMed (directory and all contents)HTML (directory and all contents)URI.pmURI (directory and all contents)
3. Upload to moxiedata/support/assets directory:
bm-ie.jsbm.jslightbox_sm.js
4. Upload to moxiedata/templates/cp_templates directory:
wi_prompt_slider.tmplwi_prompt_system_time.tmpl
5. Upload to moxiedata/templates/site_templates directory:
base.cssHTML (directory and all contents)RSS (directory and all contents)
6. Update the bmadmin/index.html file with your site’s moxiebin URL.
Open bmadmin/index.html in a text editor and follow the
instructions in the file to update the two marked URLs with the full
URL to your server’s moxiebin directory.
7. Upload to bmadmin directory:
css (directory and all contents)index.htmljs (directory and all contents)
8. Set your FTP client to “binary” or “automatic” mode.
9. Upload to bmadmin directory:
wysiwyg (directory and all contents)
10. 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
11. Clear your browser cache
Clear your browser cache, and ask other Big Medium
editors to do the same.
This completes the update from v2.0.
Tags:
bigmedium
