You have recently ungraded your IBM Connections environment to release 3.x. Users who had access rights of “Author” are no longer able to see or edit draft or published documents in the blog.
Users who were previously able to view and edit blog entries are now unable to since the upgrade. If these users access the Entries page of the blog, the entries that used to be listed are no longer listed. These users are Authors of the blog. Owners can view and edit the entries just fine.
via IBM Authors are unable to view or edit blog entries after upgrading IBM Connections – United States.
I get this question, or at least a variation of this question asked all the time. With many different blogging options for the Enterprise, what’s one to do?
Domino Blog is designed for individuals or a team blog. While many of the features compare, it’s not a solution you would want to deploy across an enterprise. Every blog has it’s own NSF database so it does not scale for an enterprise. An administrator will need to create the NSF on a server and then modify the ACL for the blog author(s). Also, there is no concept of a roll-up or aggregation of all the blogs.
Connections stores all the blogs in a single RDB with a federated search across all active blogs. Any user can easily create their own blog and manage it from a web UI. The solution sounds simple enough when you take a step back and really take a look at what your blogging requirements are for your organization.
Recently a customer of mine using Lotus Connections had an issue with attaching MS Office files to blog entries. They had no problems attaching jpg, jpeg, gif, png, pdf files (or other non MS files). Well here’s the solution. You need to configure the WAS MIME settings. Here are the steps you need to follow.
- Go to WAS admin console.
- Click on “Environment”
- Click on “Virtual host”
- Click on “default_host”
- Click on “MIME”
- Add the MS Office file extensions to the list
I’ve included a screenshot of where in the WAS admin console you need to make this change.
This sounds like an open and shut case, but upon further review, it’s not so clear. Or is it? Let me give you some background information. Company XYZ hires a Web Designer (John Doe) and as part of his responsibility, was to create and update a company blog. John Doe creates Company XYZ blog using WordPress.com and the company website links into this blog. Creates it using his name as the username, provides a password, provides his personal email address. John Doe starts blogging for several months. Some of the blog entries are his own opinions, others are on topics that his company has asked him to blog about. Company XYZ business starts to slow down, so layoffs are inevitable and low and behold, John Doe doesn’t make the cut. The union between the two is amicable, but two weeks later Company XYZ notices that several blog entries from the previous months have been deleted, and John Doe has decided to change his password to the blog site. Company XYZ is irate and contacts John Doe, and John Doe gives them the single finger salute.
So who owns this blog? Initially I thought, Company XYZ because they pay John Doe a salary to create and update the blog. Then I looked up the definition of what a blog is and suddenly it’s not so clear since John Doe has contributed some of his own topics and his own opinions on this public blog site which he has created using his own name.
So who owns this blog? I’d be interested in your thoughts on this and what the best way is to resolve and prevent this type of scenario from occurring again. For now, Company XYZ is currently going to seek legal counsel, and John Doe has moved on to other endeavors.