LDAP users editing html elements 6.2.0020

This bug seems to affect 6.2 Revision 0020 versions of SiteManager.  T4 are aware of the bug and will be releasing a new build later in the month.

The problem is that when the LDAP import is run, the HTML Editor (WYSIWYG) for new Users is not being set correctly. The Users therefore cannot modify content with HTML elements. Any new users after an LDAP import will need to have their editor set.  T4 are doing a new build with this bug fix included.  The fix can be applied yourself everytime an LDAP import is done. You can do this by running a SQL query on your database, or by manually editing each user’s profile and selecting the editor (make sure to click update).

SQL can be used: update users set html_editor=4 where html_editor=0

Highlighting the current category in the Media Library

I’ve just made an update to my post about Tweaking the SiteManager UI in Firefox from January 2008.

Tweak not working

For months now — I guess since our update to version 6 point something — I noticed that my original Media Library tweak was no longer working, it wasn’t highlighting which category I was currently viewing. So I dusted down Firebug and did some investigating.

I guess the original tweaks worked in Site Manager version 5.x.

The fix

It looks like TERMINALFOUR changed the class applied to the currently selected Media Library category. The following should work in Stylish … at least, it works for me!

a.nodeSel {
background-color: #950004 !important;
color: #fff !important;
padding: 2px !important ;
}

Example

What it does, is gives the currently selected category a dark red background, and displays the text in white.  Like this:

If you’re not sure how to make this work then check out the original article: Tweaking the SiteManager UI in Firefox.

Gareth @ St Andrews

Problems downloading items from the Media Library in IE

We’ve had an issue for a wee while now whereby if you were using Internet Explorer then you couldn’t use the Download links in the Media Library to download a file.  With a little insight from TERMINALFOUR and a poke around in the configuration settings this issue has now been resolved.

The problem

What happened in IE was that if you clicked on the Download link (either when right-clicking a Media Library item or while modifying a Media Library item, see screenshot below) then a blank page would open.

Download link in Media Library

It worked as expected, however, in Firefox.

The solution

It turns out that the solution can be found within Site Manager handlers’ configuration (TOOLS > CONFIGURATION > Handlers tab).

Site Manager configuration

1. Go to TOOLS > CONFIGURATION.
2. Click on the HANDLERS tab.
3. Locate the Download Handler.
4. Click on Configure.
5. Make sure “Download Method” is set to Attachment.
6. Click UPDATE.

The problem was that our Download Method was set to “Inline”.

Download handler - set Download Method to Attachment

Interestingly, there’s a letter answered in this month’s .net magazine about a very similar issue involving the content-disposition HTTP header.

Converting designs into SiteManager Styles

Printing out a screenshot and scribbling on it

This morning my task is to convert a static HTML design for a new website so that it can be managed within TERMINALFOUR SiteManager. I may of course be stating the obvious to all readers, but this may help someone.

Header and footer

In creating a new SiteManager style you first need to decide how to break up the page into header and footer, so that the appropriate code can be dropped into those fields within the SiteManager Style dialog.  This depends on where the main content is going to be, with the code above it being the header, and the code below being the footer.

Links, menus, sections

With that decided you then need to work out where the various links, menus and sections on your design are coming from.  Are they going to be pulled in with a top content item from another section, for example, or from a related content sub-section; do the links need to be hard-coded (in the case of a link to a site managed in another SiteManager channel) or dynamically generated by SiteManager using a navigation object, etc.

Print it out

I’ve find the easiest way, by far, to plan the job is to take a screenshot of your design, print it out — we have a colour A3 printer here which is perfect for the task — and then get scribbling on the page.  I use coloured highlighter markers too to distinguish different kinds of treatment, e.g. blue for hard-coded links, green for new navigation objects, yellow for main content, etc.

I also make sure that I write on the print-out which unseen elements within the <head> section need to be updated/created, e.g. CSS styles, meta tags, RSS links, etc.

Build it

Once I’ve mapped out what I need to do it’s then just a case of starting somewhere and creating the new navigation objects as required.  I always start at top-left and work in a clockwise direction.  I also code it in my text editor of choice (Blumentals WeBuilder, thanks for asking) as I find it easier to manage code in that environment (and we also commit all our code to a Subversion repository) and then when finished cut and paste it into SiteManager.

I hope that’s of help to someone.

Gareth @ St Andrews

PureText deals with Mozilla problem pasting from Word

One issue we’ve encountered with copying and pasting from Microsoft Word into Mozilla Firefox 3 is that it brings with it a whole load of Word-specific code, e.g.:

<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:PunctuationKerning/> ...

which can lead to unexpected results on the published page. Even using the “Remove all formatting” button doesn’t remove the unwanted Word-generated XML code.

PureText

However, I’ve discovered a small Windows application called PureText by Steve Miller that runs in the system tray/notification area that addresses this issue.

The application runs as a single executable file (i.e. you don’t need to install it) and when you’ve copied your text from Microsoft Word, rather than pasting it with the standard Ctrl+V instead you use Windows key+V.

This effectively does the same as pasting the text into Microsoft Notepad, then selecting it all and copying it out again, removing all the formatting in the process.

My initial tests have been encouraging.

Gareth @ St Andrews

T44U

We’re just back from the T44U Conference in Dublin. It was great to meet up with so many users and renew acquaintances with many familiar faces.

There was a lot to take in with information about 6.2, discussions on the direction for 7.0 and news on the launch of the Extranet. We certainly left with a few new ideas and a positive outlook on the coming developments.

There was some discussion of the creation of a T4 user group which seemed to be welcomed by all. We at Strathclyde (and I imagine across the Scottish Web Folk T4 users) would certainly be supportive of this. Until then I’ll reiterate the invitation for any institutional users of T4 to feel free to contribute to this Blog and if the main Scottish Web Folk meeting is splitting into software specific streams including T4 then anyone should feel welcome to pop along.

Follow up to “How to reorder Media Library categories”

This is intended as a follow up to the highly informative “How to reorder Media Library categories” with some more media library hacks.

1. Other ways to access the Media Library

An interesting way to access the media library is to use the following url:

http:///terminalfour/SiteManager?ctfn=hierarchy&sid=3335

You can also use

http:///terminalfour/SiteManager?ctfn=hierarchy&sid=3335&PIntLoc=3335

This gives you the hierarchy view of the Media Library as opposed to the modify section view so moving, duplicating and so on are now possible.

(The 3335 is our media section id see “How to reorder Media Library categories”.)

2. Set group access to Media Library sections

You can also go into the Media Library sections and set up group access to them. This speeds up user configuration and management.

1. Navigate to relevant section.
2. Go to group tab.
3. Assign group.
4. Update.

Result when user is assigned to group they automatically get media library access.

3. Preview the Media Library

It is also possible to preview you media library from this view. (This requires write-access to the database.)

1. Add a new channel in the usual way.
2. For the root select any section.
3. Now in the database using the id of the channel, update the channel table to make the root value the media section id (e.g. 3335).
4. Add the formatter you require to the media template.
5. Add your style to the root media section.
6. Preview away.

Harry @ Strathclyde

TERMINALFOUR on Twitter

T4 on Twitter

Nice to see @TERMINALFOUR on Twitter. With a Web 2.0-style icon too. Get following!

Ignore name on publish

Screenshot of Environment variables screen

One really useful feature of SiteManager is the ability to specify section names that you would not like published to the server. A perfect example is sections that are being used to store related content.

Example

On our website at St Andrews if we want contact information to appear in the right-hand sidebar then we simply add a sub-section called rel_contact and we have a navigation object that pulls that content into a particular place in the style.

We’ve defined quite a few names for related content, almost all of them begin rel_…, e.g. rel_documents, rel_forms, rel_internal_links, rel_javascript, etc. Obviously, we don’t want these sections to be published so we simply add these section names we don’t want published out in the ignore-name-on-publish variable.

Configuration

You can setup this feature using an environment variable within TOOLS > CONFIGURATION > ENVIRONMENT (tab).

The variable name is ignore-name-on-publish-x, where x is the number of the channel that you wish to exclude these from.  So if your main website is published on channel 1 then the variable name would be ignore-name-on-publish-1.

Caveats

Now, should you move to a new website design, published on a different channel, make sure you remember to create a new ignore-name-on-publish-x variable otherwise your new site will be littered with unrequired directories.

This is the bit that we missed.  We didn’t realise that the number at the end referred to the channel.  You can get the channel ID from the URL when you go to TOOLS > CHANNELS

And while I’m at it, also make sure that if you are switching over from one channel to another that you change the output directory on the old channel.  Because if you leave it, and it’s pointing to the same directory as the new channel then there is a chance that if you publish out the old channel (by accident, or curiosity, or whatever) then you’ll be left with a right mess!

Can you tell that I’m speaking from experience here?

Don’t schedule content to expire during the Middle Ages!

Well, that’s been an interesting day!

We experienced an interesting issue with SiteManager today which resulted in it going off-line for a couple of hours, during which it was caringly poked and prodded at by both TERMINALFOUR and our 1337 ninja Oracle squad until it was coaxed back to life.

It turns out that the issue was that someone had accidentally scheduled a piece of content to expire sometime in the Middle Ages (1008) rather than this year (2008).

So SiteManager’s scheduler passed this date to the Oracle database which sent it right back saying that it couldn’t process this date.  So SiteManager passed it back to Oracle (without closing the connection) which sent it back, which then sent it back to … you get the idea.

In the end we ran out of memory because of all the open connections to Oracle.

TERMINALFOUR tell us that they’ve added a feature to prevent this issue (entering dates in the past) in SiteManager 6.2.

In the meantime, just make sure your users are working in this century … obviously apart from those still using IE6! ;)

Gareth @ St Andrews