Simply RedDot

Content Class Inspector

2012-02-24T17:17:00.002-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Displays all content class folders, content classes, and template/project variant association
Opens template as read-only directly from interface
Checks content class for possible unused elements, which slow down project performance
Copies content class folder and content class name into clipboard via easily accessible bottom

Accessibility

In SmartTree, Start -> Administer Content Classes, Action Menu, Content Class Inspector.

Slow CMS Due to .NET Preexecution

2012-02-24T16:30:00.003-05:00

If active scripting in project is configured to aspx, then a cache dll is created on the server's "Temporary ASP.NET files" folder for every SmartEdit page access, page preview and page publish. Management Server slows down as more cache dlls are created within "Temporary ASP.NET files", eventually Management Server becomes unresponsive when accessed via SmartEdit, page preview or publishing.

The solution to delete the amounting cache dlls via an automated task, preferably nightly, schedule it so it does not clash with publishing or user access time period.

7.x to 9.x SP1 (using .NET 1.1)
Create "Clear_.NET_Temp_Cache.bat" in [MS Installation Directory]\ASP\Plugins

cd "C:\Windows\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\cms"
del /S /Q *

9.x SP2 to 10.x (using .NET 3.5)
Create "Clear_.NET_Temp_Cache.bat" in [MS Installation Directory]\ASP\Plugins

cd "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\cms"
del /S /Q *

Create User-defined Job
Create user-defined job that runs nightly, schedule it so it does not conflict with existing publishing time.

Configure user-defined job to "External application", and provide path to aforementioned .bat file

For Management Server Clusters
N user-defined jobs for N Management Servers in the cluster

Delete All Unlinked Pages 2

2012-02-21T14:59:00.002-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Deletes unlinked pages in bulk
Fast, averaging 2 pages per second
Minimal server load, will not affect other users during operation
Deletes oldest page first
Provides status update

Accessibility

In SmartTree, Start -> Administer Project Structure -> Edit Special Pages -> Unlinked Pages, Action Menu, Delete All Unlinked Pages 2.

File Renamer

2012-02-20T13:52:00.001-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

View and edit all page file names of a content class
Helpful one click functionalities like use headline as file name, lower case all letters, replace invalid characters with SEO friendly characters, one click save

Accessibility

In SmartTree, Start -> Administer Content classes -> Content Class Folder -> Content Class, Action Menu, FileRenamer.

Auto File Name

2012-02-20T12:02:00.002-05:00

Download

Compatibility

7.x
9.x
10.x

Description

Automatically assign SEO friendly page file name using page headline

Accessibility

Please see readme.txt within plugin zip for easy installation instructions.

Job Report Manager

2012-02-20T10:23:00.002-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Allows the user to view all publishing job reports with ease
Light and fast to load (100 entries, 0.3 seconds)
Sortable (sorts publishing time in dsc order by default)
Support multi sort
Support multi job report deletion

Accessibility

In SmartTree, start->administer publication->job reports, Action Menu, Job Report Manager.

Retroactive References 2

2012-02-17T14:05:00.001-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Allows user to retroactively apply link or page references to anchor, list, and containers for all page instances of a content class
Can process unlimited references without server timeout
No run away processing upon closing window, which is common in most asp plugins

Accessibility

In SmartTree, navigate to a page instance, select structural element, ensure target link/page is selected in clipboard, in Action Menu, click Retroactive References 2 to bring up final confirmation screen.

TagIt

2012-02-16T17:08:00.001-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Lists all categories and keywords at once, so user can assign categories and keywords more efficiently
Highlights assigned category and keywords for better usability and faster content review
Categories and keywords fit to window size automatically

Accessibility

In SmartTree, select page, Action Menu, TagIt
In SmartEdit, please refer to readme.txt within plugin

RQLConsole

2012-02-16T13:31:00.000-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Send a RQL message via console and view RQL response
See all available server sessions for debugging and RQL development.

Accessibility

In SmartTree, Start -> Administer Project Structure -> Project, Action Menu, RQLConsole

FindIt 2

2012-02-16T13:27:00.003-05:00

Download

Screenshot

Compatibility

7.x
9.x
10.x

Description

Ability to search for code within all content classes or content classes within specific content class folder
Supports regex syntax
User can open template as read only directly from search results

Accessibility

In SmartTree, Start -> Administer Content Classes, Action Menu, FindIt 2

Management Server 10.1 with MSSQL 2008 Installation Checklist

2012-02-15T20:17:00.006-05:00

Here is a simple checklist for Management Server 10.1 installation with MSSQL 2005/2008.

Note that this checklist prepares the system for Management Server installation using local MSSQL accounts.

Download Doc

Publishing Following Pages

2012-01-31T10:04:00.001-05:00

Often, users would experience the issue of following page won't publish. This issue is actually template code related. Management Server will not publish pages that it cannot get to via link.

For example, pages are connected to lst_navigation but do not publish when "publish all following pages" option is selected.

That is because the following code is missing in the template code and Management Server cannot crawl to following pages.


<!--
<!IoRangeList>
<%lst_navigation%>
<!/IoRangeList>
-->

Duplicate Pages

2012-01-06T11:47:00.001-05:00

Most publication issues can be caused by pages connected to multiple locations. The most common symptom is having duplicate pages on the site.

For example: Both page 1 and page 2 are connected to multiple locations with different publication package at each location, so the pages will get published twice, each time to a different location.

Obsolete Solution (Not working in 9 or 10)
Edit the content class of "RSS Listing", use preexecution to replace islink=2 with islink=10 to trick CMS into thinking the following pages are references, hence not to crawl and publish following pages.

All Version Compatible Solution
Use the list to pull info_page_guid from the connected page.


<!IoRangeList>
<!IoRangeNoRedDotMode><!IoRangeRedDotMode><!--<%lst_pages%>--><!/IoRangeRedDotMode><!/IoRangeNoRedDotMode>
<li><%!! Context:Pages.GetPage(Guid:<%inf_page_guid%>).GetUrl(Bool:True) !!%></li>
<!/IoRangeList>

Page 1 and page 2 still get published according to different publication packages, but links generated always point to the pages' main link

SyntaxHighlighter for RedDot

2011-12-08T16:32:00.001-05:00

Just want to share the RedDot syntax for SyntaxHighlighter. Please no hotlinking. I only have limited bandwidth per month.

Files to include on HTML page:

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shCore.js' type='text/javascript'></script>
<script src='https://sites.google.com/site/simplyreddot/shBrushRedDot.js' type='text/javascript'></script>
<link href='http://alexgorbatchev.com/pub/sh/current/styles/shCore.css' rel='stylesheet' type='text/css'/>
<link href='http://alexgorbatchev.com/pub/sh/current/styles/shThemeDefault.css' rel='stylesheet' type='text/css'/>
<link href='https://sites.google.com/site/simplyreddot/shCoreRedDot.css' rel='stylesheet' type='text/css'/>
<script type='text/javascript'>
 SyntaxHighlighter.all();
</script>

Case escape HTML code in:

<pre class="brush: RedDot">
...
</pre>

Managing JS CSS XML as content classes in 10.1

2011-12-08T15:46:00.001-05:00

Problem

Management Server treats all page instances as HTML pages and like to search for <head> and <body> tag to inject javascript code into them. The issue is most noticeable in version 10.1.
If <head> and <body> tag are not found, MS injects those tags along with javascript snippets to the top of the page.
For CSS and JS pages managed in MS and linked via anchor, this invalidates the CSS and JS, hence user would notice some CSS styles not being applied, and JS library/function not loaded.

Solution

Include this code at the bottom of any CSS or JS content class that have page instances referenced/connected via anchor in NOT Publish Mode to avoid invalidation.

/** <html><he<!IoRangeNoRedDotMode><!/IoRangeNoRedDotMode>ad></head><body></body></html> **/

Navigation Emulation

2011-12-07T16:48:00.001-05:00

What is it?

Allow a page, even a non navigation page, to display the exact navigation area as displayed on any page.

Why is it useful?

When a page is not in navigation manager, the page cannot display navigation because it is not part of navigation manager.

However, a page should not be in navigation manager simply because it needs to display navigation. For example, news article pages should not be in navigation manager because number of navigation pages in navigation manager negatively impacts project performance.

However, news article pages must display navigation area for the shake of accessibility. Hence, news article page can use navigation emulation to emulate the navigation of its parent page, the new archive page.

Simple Method

<!IoRangeDynLink>
<!IoRangeNoRedDotMode><!IoRangeRedDotMode><%anc_link%><!/IoRangeRedDotMode><!/IoRangeNoRedDotMode>
<%!! Navigation:OutputArea(LeftNavArea, Bool:True, Guid:<%inf_page_guid%> !!%>
<!/IoRangeDynLink>

Advanced Method

<reddot:cms>
 <if>    
  <query valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage).GetRootIndex().Id" operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
   <!-- This Page is in Navigation Structure -->
   <htmltext>
    <%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.Id, Bool:False) !!%>
   </htmltext>
  </query>
  <query valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage).GetRootIndex().Id" operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
   <!-- The Page 1 Level Up is in Navigation Structure -->
   <htmltext>
    <%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.MainLink.OwnerPage.Id, Bool:False) !!%>
   </htmltext>
  </query>
  <query valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id" operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
   <!-- The Page 2 Levels Up is in Navigation Structure -->
   <htmltext>
    <%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.Id, Bool:False) !!%>
   </htmltext>
  </query>
  <query valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id" operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
   <!-- The Page 3 Levels Up is in Navigation Structure -->
   <htmltext>
    <%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.Id, Bool:False) !!%>
   </htmltext>
  </query>
  <query valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id" operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
   <!-- The Page 4 Levels Up is in Navigation Structure -->
   <htmltext>
    <%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.Id, Bool:False) !!%>
   </htmltext>
  </query>
  <query valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id" operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
   <!-- The Page 5 Levels Up is in Navigation Structure -->
   <htmltext>
    <%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.Id, Bool:False) !!%>
   </htmltext>
  </query>
 </if>
</reddot:cms>

What a project start page should look like

2011-12-07T12:17:00.000-05:00

Start page should never be a navigation page
Anchor should be used instead of list because anchor allows individual publication package, authorization, and workflow for each section.
CSS and JS should never be connected directly to a page. They should only be connected to one location and referenced by other pages.