The "Picket Fences" beta update lets you limit individual Big Medium accounts to specific sections of a site. Give teachers their own mini-sites at your school website, or let the PR department's publicists edit the news section of your corporate site, while restricting access to other areas. Other accounts may likewise be allowed to edit these sections or not, as you decide.
The new version also adds a variety of other features and bug fixes, noted below.
Go get it
Download the latest version of Big Medium here.
The download package includes complete installation instructions, including
info for upgrading from previous versions of the Big Medium 2 beta. Shortcut
instructions for upgrading from 2.0b45 or b46 are provided
below. (If you’re upgrading from versions earlier than 2.0b45, please follow
the instructions in the download package’s installation guide.)
The nitty gritty
Here’s what’s new in this update:
Features and changes
Section-specific account privileges. Webmasters and administrators can now
limit accounts to specific sections of a site so that they can add/edit
content only in those sections.
Customize privilege level on a per-site basis. Accounts can be assigned
different privilege levels for different sites (e.g. writer at one site,
publisher at another).
Slideshow navigation improvements. The next/previous buttons are now always
visible above the slideshow images. You can also dismiss a slideshow or
enlarged image by clicking anywhere outside of the image.
Custom text in <title> tag. HTML preferences now include a
"title tagline" option to add custom text as an element in pages'
<title> tags.
Additional display info for section pages in the edit menu. The slug names
of the section and parent sections are shown below the title to prevent
confusion among sections with the same name.
JavaScript performance improvements in the control panel for a
snappier interface.
More descriptive title tags for RSS auto-discovery links. Makes for a more
user-friendly experience when visitors subscribe to your feeds.
Bug fixes
Flash images no longer obscure slideshows or enlarged images.
Fixed bug in edit menu's "change status" screen that erroneously offered
the publish option to editors (it wouldn't actually let them publish,
but the option shouldn't have been displayed in the first place).
Fixed bug that could occasionally allow homepage or section-page links to
pages in sections where the homepage/section suppression option is on,
if the page is assigned to other sections without the suppression option.
Fixed bug that could cause a crash if a background error was encountered
when saving pages (for example, when sending new-page email alerts).
Fixed bug that caused <%today%> widget to drop some date elements
on Windows IIS servers.
Fixed bug that prevented some confirmation messages from appearing in the
control panel for Windows IIS servers.
Upgrading from 2.0b45 or b46?
If you’re upgrading from v2.0b45 or later, 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
Upload these files to the moxiebin/Modules directory, replacing the old files of the same names:
BigMed.pm
BigMed (directory and all contents)
3. Upload to moxiedata/support/assets
Upload these files to the moxiedata/support/assets directory:
lightbox_sm.js
prototype-scriptaculous.js
4. Upload to moxiedata/templates/cp_templates
Upload these files to the moxiedata/templates/cp_templates directory:
screen_account_edituser.tmpl
screen_editor_menu.tmpl
wi_account_priv_form.tmpl
wi_account_privilege_item.tmpl
5. Upload to moxiedata/templates/site_templates
Upload these files to the moxiedata/templates/site_templates directory:
base.css
HTML/wi_htmlhead.tmpl
6. Upload to bmadmin/css
Upload this file to the bmadmin/css directory:
bigmedium_cp.css (directory and all contents)
7. Upload to bmadmin/js
Upload these files to the bmadmin/js directory:
bigmedium_cp.js
bm-account.js
prototaculous.js
8. 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.0b45 or b46.