Ted Hardenburgh read the technote saying soft-deletes were not supported in the 8.x mail template. Then he sat down to figure out what that really means. He kindly posted up his findings.

In case you didn’t see the letter from IBM, Gregg Eldred has posted the highlights and a PDF of the full letter. The changes are to be implemented February 16 with the hope of improving customer service.

David Killingsworth installed the SuperAdmin application from OpenNTF and ran it through it’s paces. He offers his opinion on what is good, and not so good, about it and how it might complement the Notes Administrator Client.

Mary Beth Raven wants your input before making a change to the Notes client. If you’ve embedded Sametime connect in the Notes client, and go into Offline mode, do your users expect to stay connected to Sametime?

We’re back from Lotusphere. Last week, I gave you an overview of Notes and Domino 8.5.1 and promised that you’d learn more about SAP integration, some open source stuff, mobile, and Sametime. That’s what’s in this week’s installment.

Read this DominoPower article.

Today’s topic is "User-based hide whens" in Flex. Jake Howlett explains how to use this feature to determine what buttons a user should be able to see on their screen.

Robert Ibsen Voith is trying to create a web calendar using Dojo. So far it works fine in Firefox and Opera. But Internet Explorer seems to get indigestion. Do you have any ideas what went wrong?

Rob McDonagh and Julian Robichaux demoed this Lotus Notes 8.x plug-in at Lotusphere. Now Julian has posted some information and a download link on his blog.

Well, we’re getting there. Most of the big internal changes to the database have been implemented and we’re just going around and finding some of the remaining cross-references that didn’t show up during our initial scan. Some pages may not load properly or links may result in errors. We should have all that resolved within a few hours, since it looks like the tough part of the job actually worked pretty nicely.

Thanks for your patience. The net result, although you won’t see too many new features, is that our internal database structure will be more reliable and a serious failure point (old, legacy code) has been removed and replaced with a much more robust design.

Back to work…

We’re doing some very deep maintenance today on the ZATZ sites, upgrading a legacy system that’s been driving some of our sites for more than a decade and that has gotten extremely long in the tooth. Because we have to go in and touch every single page on every single site that we’ve ever published, there may be some intermittent performance hits throughout the day. You may also notice instances where the page numbers or next/prev buttons show up twice. That’ll be resolved as we traverse the pages thoughout the day.

Thanks for your patience. Hopefully, everything will be running smoothly within a few hours.