What Should Corporations Do With Their Blogs | chrisbrogan.com

What Should Corporations Do With Their Blogs | chrisbrogan.com.

I was fortunate to be able to call together a great group of people at a moment’s notice to host a flash panel at the Pepsico Podcast Playground at SXSW. I wanted to talk about a Wall Street Journal article where AMD blogged about something and then Intel said blogs weren’t the place to talk about important issues. I pulled together George Smith, Jr, from Crocs, Christopher Barger from GM, Keith Burtis from Best Buy, Bonin Bough from Pepsico, Pat Moorhead from AMD, and Morgan Johnston from JetBlue for a conversation.

What follows is a video from the flash panel. I hope you’ll watch it and share your thoughts.

[vimeo]http://vimeo.com/3737019[/vimeo]

UMW Blogs support videos for WPMu 2.6

Jim Groom

Jim Groom, who administers the UMW group of WordPressMU blogs has placed a whole slew of videos online, which help users with WPMU, as well as migrate from WPMU-1.3.3 to WPMU-2.6.

Click on image to view site

The inimitable Andy Rush (a.k.a. EduRush) and I have been working diligently to create a whole slew of screencasts documenting the new interface for WPMu 2.6. We’ve finished a whole bunch of them over the last week or so and published them on the now official UMW Blogs Screencasts site, so below is a list of the screencasts we have created. All of the screencasts are Creative Commons and while they’re currently published as SWF files, we will be uploading them all to Blip shortly. Keep in mind that these screencasts are specific to the UMW Blogs installation, but they still may prove useful for anyone who wants to point people to a quick overview of the administrative backend, the changes between versions WPMu 1.3.3 and 2.6, and a very tab-specific discussion of the how to manage a WordPress blog.

WordPressMU Bug Trac for fixing target=”_blank”

W3C - World Wide Web ConsortiumOnce upon a time, we had a vexing problem where we couldn’t set the @target (OT: @target is tech-speak/jargon/euphemism for ‘target attribute’). Actually, you could set it, but when you ‘saved’ the post or story, TinyMCE (that nifty toolbar interface for formatting blog posts used by WordPress and a million other places). Here’s where I figured out what was wrong. I don’t know why they ‘broke’ the @target attribute, although I do know that the ‘target’ attribute was deprecated in HTML 4.01, as well as XHTML 1.0. However, there are ways around it, like via JavaScript and XHTML modules which are pretty darn cool.

Anyway, when we upgrade WordPressMU to the next version, we’ll likely need to ‘fix’ this again, so here’s $98 bucks worth of direction:

Changeset 1022 – WordPress MU Trac – Trac

Just change this:

$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array()
),

to this:

$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array(), ‘target’ => array()
),

NOTE: This change was downgraded to determine if it inexplicably affects bandwidth performance.

WordPressMU Bug Trac for fixing target=”_blank”

W3C - World Wide Web ConsortiumOnce upon a time, we had a vexing problem where we couldn’t set the @target (OT: @target is tech-speak/jargon/euphemism for ‘target attribute’). Actually, you could set it, but when you ‘saved’ the post or story, TinyMCE (that nifty toolbar interface for formatting blog posts used by WordPress and a million other places). Here’s where I figured out what was wrong. I don’t know why they ‘broke’ the @target attribute, although I do know that the ‘target’ attribute was deprecated in HTML 4.01, as well as XHTML 1.0. However, there are ways around it, like via JavaScript and XHTML modules which are pretty darn cool.

Anyway, when we upgrade WordPressMU to the next version, we’ll likely need to ‘fix’ this again, so here’s $98 bucks worth of direction:

Changeset 1022 – WordPress MU Trac – Trac

Just change this:

$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array()
),

to this:

$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array(), ‘target’ => array()
),

NOTE: This change was downgraded to determine if it inexplicably affects bandwidth performance.

TinyMCE – The WYSIWYG Editor for WordPress

TinyMCE EditorTinyMCE is a powerful WYSIWYG editor control for web browsers such as MSIE or Mozilla that enables the user to edit HTML contents in a more user friendly way. The editor control is very flexible and it’s built for integration purposes (usage within systems like Intranets, CMS, and LMS, for example).

TinyMCE:Installation – Moxiecode Documentation Wiki

This is the Text Editor available for WordPress posting (Visual Edit mode). Pretty neat. Perhaps we’ll add a few items…

Here’re some more interesting TinyMCE links:

Perhaps, if I can ever find some time, I’ll be able to play around with this stuff.