Changes can be viewed through TS Change Management System:
http://www.pubapps.vcu.edu/changes/plannedChange.aspx?processFlag=1&dID=11926

User Description: CMSE10 & CMSP10- Add RAM – It has been determined that CMSE10 & CMSP10 need additional RAM to eliminate performance issues from hard disk paging.  The VMs will be briefly shut down to be reconfigured.  This outage will affect production OpenText WebCMS functions.  This has been coordinated between VCUTS UCC staff and VCUTS Web Services staff.

I found this article but it didn’t work on my webconfig.

Then I found another article on the OT KC that broke out the values into ASCII. Put the code in the same place mentioned in the above article, only format it as follows:

<Replace trim="true"> <OldValue>//&#60;!&#91;CDATA&#91;</OldValue> <NewValue><![CDATA[]]> </NewValue></Replace> <Replace trim="true"><OldValue>//&#93;&#93;&#62;</OldValue> <NewValue><![CDATA[]]> </NewValue></Replace>

The page views are recorded so that the Knowledge Base Topic page can return a list the most popular Articles and Article Indexes at bottom of each Topic page.

Additionally, the CMS editors can add “Related topics” to help guide their users.

This has been useful in providing the end users of the website quick access to frequently asked questions, as well as guidance on finding information related to their query.

By default, this tracking system is always “on”. However, sometimes, the content is set up in a way that showing top articles does not make sense. Or the topic has no “Related” information.

Here is how the CMS editor can turn that section “off”.

1. In the CMS, open the KB Topic page for editing. How do you know if the page is a KB Topic page? Open the page for editing > at the top of the screen choose “Properties”. Content Class should be “Foundation/KB Application Home”. Examples of this page: Blackboard, PMIT, Technology Resource Needs Form

2. Open the Form for Editing (red dot with the F)

3. The second choice is “Hide top articles in this section?”. By default this is set to “show”. Choose “hide” in the drop down menu.
 

4. Clear Tasks through the Tasks button on the left and publish page.

• OpenText (formerly RedDot) is VCU’s officially supported CMS.
• The CMS currently has 28 sites in production, up from 15 sites in November 2009.
• As of July 10, 2010, the CMS has 244 user accounts.
• We are currently testing version 10 and hope to have this rolled out by January 2011.
• Last May we virtualized the servers, splitting the editing from the publishing. The application was also moved to a new server. This has helped speed up the CMS experience.
• Departments wishing to use the CMS should contact Tiffany France or submit
  a help desk ticket.

In order for a page to publish, it must be linked to a list or an anchor somewhere in the structure. (There are exceptions to this rule, though none of the current projects at VCU fall in this realm).

Disconnect/Reconnect Page
When you receive this error, the first thing you should try is going into SmartTree and selecting the page. Next, double click the page to put it in the clipboard. In the action menu choose “Disconnect Page from List”. Making sure that the disconnected page is checked in the clipboard, go up to the list that contained the page originally and reconnect the page with “Connect to Pages in Clipboard”. Try to publish again.

Show Element in Template
If you are still receiving the “page not linked” error, open your template. Make sure the list or anchor element is present in the template. The element MUST be placed on the page to be recognized and published by the CMS. If you do not want the contents of the list or anchor to show on the page, either comment them out or set them to show in SmartEdit Only. Republish.

To prevent this happening, this code tricks the page into thinking the page is referenced instead of copied. Therefore it keeps the correct path:

<reddot:cms>
  <foreach itemname=”item” object=”Context:CurrentPage.Elements.GetElement(lst_departmentallist).Value” countername=”counter”>
    <htmltext>
<li><a href=”<%!! Store:item.GetUrl() !!%>”><%!! Store:item.Headline !!%></a></li>
    </htmltext>
  </foreach>
</reddot:cms>

When developing a template, you can preset an element’s content for all new pages by selecting an instance of that element that is already populated on an existing page. Double click the instance to put in the clipboard. In the content class template, expand until you find the element, and choose “Reference Element in Clipboard”.

The problem is that this will only affect FUTURE pages. What if you already have 100 existing pages that need the same reference?

I recently installed two plugins: “Reference Link” and “Reference Page”

By running these plugins you will automatically replace the specified element’s content with the “referenced” element content on ALL pages using that template. This is a HUGE time saver.

The plugin has to be enabled on your project. Please contact Tiffany France if you would like this plugin to be turned on.

Note: Use the same link above to unsubscribe from the list.

Read more about VCU TS Mailing Lists/ListSERVs.

Over the winter break, the CMS experienced periodic outages. The system was reset this morning and appears to be working fine.

Here is what is coming up for 2010:

1. The Computer Center, Server guys in Web Services, and I are working on bringing up a new box for the CMS. This new server is faster and larger. When the new box comes online, it will feature OpenText version 10. We have been holding off on this upgrade due to some initial bugs in the product. Version 10 offers an AJAX interface that is expected to be more intuitive for the end user. Each project will be moved over one by one. All projects contain their own unique code which must be tested in the new environment before it can be released. Additionally, the user interface is significantly different, we want to ensure the users are well trained on the new system before we move the project.
2. I am now suggesting that departments use the new TinyMCE editor due to the massive benefits for the end user. Over the coming months the spell checker will be installed and tweaked for performance. If your project is using the TinyMCE, please spell check your content before bringing it into the CMS project.
3. A Slideshow Pro module that incorporates the asset manager has been built and tested. Departments wishing to use Slideshow Pro must purchase a license from their website. The module was built in house, demos are available before purchasing license. Licenses are about $30. The module is based on the Flash Slideshow Pro product.