http://simplyreddot.blogspot.com/2012/03/assignit.html

http://simplyreddot.blogspot.com/2012/03/auto-order-elements-2.html

Nach Änderungen in der Navigationsstruktur müssen Redakteure die Seiten manuell neu laden, um die Änderungen angezeigt zu erhalten.

Das Script RefreshSmartEdit stellt dazu eine Lösung innerhalb eines Templates bereit, die nach dem Schließen des Navigation Manager Fensters den SmartEdit-Arbeitsbereich neu lädt und so die aktuelle Struktur anzeigt.

Die Funktion isNavigationManagerOpen veranlasst ein Reload der aktuellen Seite nach Schließen des Navigation Managers.

Es gibt noch eine weitere Erweiterung für die Verwendung des Navigation Managers im Firefox, Opera und Co.

Editors have to reload edited pages manually after they have changed the navigation structure in the Navigation Manager. This script provides an automatic reload mechanism to refresh the edited page after the Navigation Manager window is closed.

The corresponding code is shown in the upper German section

There´s another extension available that enables the use of the Navigation Manager with Firefox, Opera, etc.

The plugin is constantly updated.
Download latest version from:

http://simplyreddot.blogspot.com/2012/03/check-multiple-page-connections.html

You can also restrict category keywords the user can select, which can be handy if you are using keywords to tag up pages (e.g. for custom Verity queries in LS) or apply a taxonomy. To do this, pass in the name(s) of the Categories via the ’shownCategories’ querystring variable:

?shownCategories=Category 1~Category 2 ...

To install the plugin:
- Copy the ‘rdUICheckboxAssignKeywords’ folder in the RedDot plugins folder
- Install the plugin via the Server Manager

Scenario 1 - Dev/QA/Production:

The development of new functions and problem solving happens on the development server (Dev). After the development is finished the changes are moved to the test server (QA). Finally during the release process the changes are moved to the production server (Prod).

Every single step could introduce errors as every change has to be moved (new elements, element changes, template changes, etc.). Even more complex migration becomes if not every single change shall be moved because there are required differences between the environments.

Scenario 2 - Migration to newer version:

The migration to a new version of the Management Server (e.g. version 9 to 10) requires many tests of existing projects. Very often changes in the content classes are required to that there are differences between the different versions that cannot be migrated back. At the same time there are changes on the old server that needs to be migrated to the new server.

Only in a few situations the projects can be frozen during the migration. As soon as complex parent/child-projects exists it is nearly impossible to freeze the project work at all. This leads to projects that differ more and more between the servers.

Using the CMS Sync Tool

With the CMS Sync Tool you can synchronize the projects between multiple servers. This is especially important for content classes. Mapping the content classes is semi-automatic. This means the tools tries to find the mapping and suggests you the changes to be done. You can choose which changes you want to migrate. There is no need to have the same GUIDs between the content classes.

 

We also have a (German) white paper about using development, QA and production servers with Open Text Web Solutions Management Server: Entwicklungsumgebung für den Open Text Management Server (früher RedDot CMS)

All content elements can be copied - including Option Lists and Text placeholders. 

The plugin has been developed using RedDot CMS v10+ and works within projects that incorporate the use of single or multiple language variants.

Installation:

Download the plugin, unzip and copy the folder ‘rdUICopyElement’ into the RedDot CMS plugins folder.

How to use it

When a content element is selected under a content class in SmartTree, the option 'Copy Element' will appear within the Action Menu. Clicking on this link will automatically create a copy of the selected element.

CTW - Assign User
Do you ever had a page in draft mode, the editor is not available and someone else should edit the page? This plugin allows you to easily assign another user to a page in draft mode with only 2 clicks. Furthermore the plugin shows you who is currently editing the page with one simple click right from the location in SmartTree where the page lives.

CTW - Inherit Reference
Websites are dynamic projects and changes are usually on the top of the agenda. Pages based on content classes perfectly reflect code changes but there are changes that will not affect existing pages.

If you add a new structure element into a content class and you pre-assign a reference this assignment will not be inherited to existing pages! But who goes through all these existing pages to do the assignment? That's for sure something that has to be automated.

This plugin does exactly that. Just highlight your structure element in SmartTree and click on “CTW – Inherit Reference” to inherit the reference to all existing instances. You can skip pages with elements that already have a reference assigned or pages with sub pages.

CTW – Inherit Workflow
Similar to "Inherit Reference" this plugin allows you to inherit assigned workflows in your content classes to all existing page instances. You can of course define in which language variants the inheritance should take place. Another big time saver!

CTW – User in Group
Working with users and groups in OTWSM works not always as desired, requires much more clicks than necessary and often don't provide the expected information in its dialogs. Furthermore you always have to switch into the Server Manager to work with them.

This plugin shows you the group members right from within SmartTree. You can even add and remove group members from within the same dialog. Quick and easy without the need to switch into the Server Manager!

CTW – Search by GUID
"3EF851D21B0B41639814A9..." Hm... GUID ... ? Sooner or later you will stumble on GUIDs. But how can you find out what a GUID is representing in OTWSM? Could be a project, content class, page, element, everything.

This plugins gives you comprehensive information about the searched object and displays it in SmartTree if desired.

All plugins are easy to install and are ready to use within a few minutes. They provide an online help that describes how to use them.

Available user interface languages: English, German, French

Just send an email to plugins@code-to-web.com if you are interested in this bundle or if you have a need for a custom plugin.

PRO Edition only:
You can save your text editor settings in multiple versions and apply them at any point in your project tree. A configuration overview shows you all your configuration sets you can choose from.

You can download the plugin from here. If you are interested in the PRO edition please send an email to plugins@code-to-web.com.

http://simplyreddot.blogspot.com/2012/02/delete-all-unlinked-pages-2.html

This module is available for purchase. Please contact asowsm@opentext.com for more information.

The project needs development to achieve this aim. Join the effort on GitHub. Reach out to the contact information provided to get an introduction if you are interested.

Redakteure nutzen eine Autorenoberfläche – WSM SmartEdit – für den Internet-Auftritt und Facebook und benötigen somit keinen separaten Facebook-Zugang. Die im WCMS hinterlegten Workflows können sofort für Autoren-Prozesse rund um Facebook-Inhalte genutzt werden. Inhalte erscheinen dadurch immer qualitätsgesichert und in mehreren Sprachen übersetzt auf der Facebook Fanpage.

Für den Ausgabekanal Facebook werden die bestehenden Attribute aus den Content-Klassen genutzt. Spezielle Attribute für Facebook können ebenfalls im WSM Management Server bereitgestellt und über den SmartEdit editiert werden. Bilder werden automatisch korrekt skaliert, um diese nicht mehrfach erfassen zu müssen. Über die Personalisierungsfunktionalität des Delivery Server können Benutzerinformationen aus dem Facebook-Profil aufgegriffen und für die dynamische, voll personalisierte Darstellung der Inhalte genutzt werden.

Die edicos Facebook-Bridge ist Teil der Multichannel Publishing Strategy der edicos. Erste Anwendungen, wie bei TRIUMPH die Online-Kommunikation des Triumph Inspiration Award, zeigen den Erfolg dieser Lösung. Weitere Informationen finden Sie unter  http://www.edicos.de/index/company/press.htm oder kontaktieren Sie direkt Stefan Thomé, Managing Director.

Flexibel anpassbares Bedienkonzept

• Vereinheitlichung von Bedienelementen und Funktionen (System- und individuelle Funktionen)
• Häufig gebrauchte Informationen/Funktionen sind schnell und einfach zu erreichen
• Analyse der Arbeitsweise des Kunden zur individuellen Anpassung
• Zusammenfassung von Funktionen für Gelegenheitsbenutzer (z. B. Dropdowns mit einzelnen Bearbeitungspunkten) sowie Poweruser (z. B. erweiterte Formularansicht)

ergänzt Standard-WSM-Oberfläche

• Vollständige Integration in die Templates (ohne Plug-ins)
• Nahtlose Einbettung von redaktionellen und administrativen Funktionen in die Darstellung der Website
• Komplette Workflow-Unterstützung (auch für Teile von Formularen etc.)

Wie funktioniert das eUI?

Kernstück ist das eUI Hauptmenü. Dieses Flyout wird im SmartEdit-Modus als Symbol an prominenter Stelle - stets im Blickfeld des Redakteurs - auf der Seite positioniert. Bei Mouseover sieht der Redakteur seine benutzerspezifisch gewünschten Funktionen. Die Anzahl der Klicks verkürzt sich erheblich.

Die Ansicht des eUI im jeweiligen System ist vielseitig konfigurierbar: Auf Knopfdruck wechselt die Seite zwischen Redakteursansicht und Useransicht ohne Kontrollelemente (WYSIWYG). Das Layout der Seite wird dabei nicht verzerrt, sodass der Redakteur immer die Benutzeransicht nach der Bearbeitung vor Augen hat.

Features

• Vereinheitlichung und Bündelung von Informationen und Funktionen in flexibel definierbaren Komponenten (Menüs, Anzeigen, Grafiken)
• eUI-Hauptmenü
  • Dieses Flyout-Menü wird an prominenter Stelle innerhalb der Seite untergebracht und ist stets im Blickfeld
  • Bei Mouseover werden benutzerspezifisch die gewünschten Funktionen eingeblendet
  • Schnellzugriff für Profilverwaltung oder OpenText-Administrationsdialoge
  • Konfigurierbare Ansicht der Seite: auf Knopfdruck kann zwischen Redakteursansicht, oder Useransicht ohne Kontrollelemente (WYSIWYG) umgeschaltet werden
• Die Hauptleiste enthält (Meta-)Informationen und Funktionen zur Seite, z. B. für die Navigation relevante Informationen, Pflege des Editorial Status, System-Standardfunktionen wie Publizierung, Freigabe oder Erscheinungszeitraum
• Pflege von Rich Snippets, z. B. für die Darstellung von Suchergebnissen in Google
• Beliebig erweiterbar, z. B. für Navigationspflege, Toolboxen, komplexere Informationsstrukturen, Formulare (edicos FormularEditor) etc.

edicos analysiert die spezifischen Erfordernisse und Arbeitsweisen gemeinsam mit Ihren Redakteuren, um die optimale und individuelle Ausprägung des eUI zu definieren. Weitere Informationen finden Sie auf unserer Website: http://www.edicos.de/de/loesungen-edicos-userinterface.html.

Direkt ausprobieren? Besuchen Sie unsere Demo-Website unter http://allesmachbar.net/.

SmartForm is an exciting add-on to the RedDot Content Management System. The SmartForm tool allows content editors to design forms, quickly and easily, from ready-made templates or customized fields. Using an intuitive "What You See Is What You Get" (WYSIWYG) interface, users can drag and drop fields to create forms such as: Customer Contact, Information Request, Survey, Feedback and Rating forms. Additional forms can then be developed using your existing styles for a consistent look and feel.

For more information and pricing please contact Enthink at 780-455-4515 or email info@enthink.com

With Taxonomy Manager, you can unlock the power of your information within your RedDot Content Management System by simply applying metadata from your taxonomies or other controlled vocabularies. Taxonomy Manager provides an easy and effective way to tag your content, allowing you to package your organization's knowledge in a more consumable way.

For more information and pricing please contact Enthink at 780-455-4515 or email info@enthink.com

Download latest version from: http://simplyreddot.blogspot.com/2012/02/findit-2.html

formMANAGER creates and publishes static PHP Forms. It can be integrated into RedDot CMS / OpenText Website Management as a plugin. It is proven and used by enterprise customers since 2007.

If you like to know more about it, call us or watch the video on youtube.

 When can you use a health check?

• Prior to upgrading
• Before a major relaunch
• Slow performance
• Support suggests project not product source of issues
• Been using the system for years

The new editing options are easy to use from within Open Text Web Site Management:
The page containing the image map is opened as usual in Open Text Web Site Management SmartEdit Mode. To modify the image map click the respective ImageMap-RedDot. The IMAGEMAP EXPERT editor will open in a new window. It provides all necessary tools to define active areas with different shapes.

The following shapes are available:
- Rectangle
- Circle

The freely defined image map areas can be hyperlinked to:
- an internal Open Text Web Site Management page,
- an external website,
- an Asset Manager file.

ADVANTAGES
- For the first time editors can create image maps from within Open Text Web Site Management.
- Very user-friendly interface.
- Creation of image maps via mouse control.
- Considerable time and cost savings compared to conventional approach (creation outside the CMS).
- Link consistency is maintained.
- The plugin can easily be used in all Open Text Web Site Management projects.
- No HTML knowledge necessary, no additional software needed.

jRQL benfits
This difference leads to several benefits explained in detail on the jRQL blog. The main benefits are:

• speed-up the development of new plug-ins and batch programs
• no RQL XML handling needed anymore
• provides high level functions, for instance moving a page from one mutli link to another
• helps to quick automate administrator's and author's click streams
• usable even without RQL knowledge
• provides plausibility checks and exception handling

Please refer to the blog for further jRQL API benefits.

jRQL functionality
I work on jRQL since 2004. Over the years I added functionality from SmartTree, SmartEdit and ServerManager.

To be more precisely I want to list the main areas where jRQL can automate tasks you might find interesting.

• login via logon GUID and session or via user name and password
• getting and setting most content element types (default values always considered), StandardFields, Text, Image, Media
• create,delete and restore pages
• connect, disconnect, reference and move pages on links
• browse and manipulate content class elements
• create and browse publication setup
• get workflow state and submit, release and reject pages
• create publishing jobs for LV and PV combinations
• get and change language variants
• full internationalisation support, read and write of UTF-8 included
• simultanously access to different projects on same and on different MSs

For a introductionary tutorial how to work with jRQL API, please refer to categories API* on the jRQL blog. You might also be interested in the general concepts of jRQL.

What you get
jRQL consists of about 110 classes for the core components (see javadoc) of OT MS and 63 utility classes (see javadoc). The range goes from a lightweight class like Plugin (14 methods) to the most extensive class Page (314 methods).

Java developers can browse the javadoc online or download the jRQL Eclipse project with connected javadoc and with all example code used in the tutorial. 

The tutorial and the presentation mentioned below show only a small part of the jRQL API, the most part of the jRQL API is still hidden. You can see the full potential only browsing the javadoc documentation for the classes. Start your javadoc browsing with the following main core and utility classes:

• Page
• MultiLink superclass of List and Container
• TemplateElement
• Project
• PageArrayList

The jRQL API is the basis for all jRQL plug-ins. They can be used without any Java know-how. You found the description of it in the Plug-ins* categories on the jRQL blog. You can download all jRQL plug-ins with an automatic installer routine.

See the most interesting jRQL plug-ins I added to the solution exchange by searching for jRQL.

In the jRQL presentation (in German) starting with slide 31 I give some examples how I use jRQL API inside Hapag-Lloyd. 

The biggest high level functionality is the possibility to crawl all physical pages below a given page and invoke a self written page action for every page found. I used it for a comprehensive page statistics.

There are 2 reasons why a page can be in draft: it is newly created and it has been updated. This plug-in handles both in a different way:

• all newly created pages will be deleted again
• for all updated pages an undo changes will triggered

After this plug-in finishes you list of draft pages is empty!

This plug-in can be called from authors as well, you only have to integrate it into SmartEdit.

Benefits
The list of draft pages can be quite crowded for the following reasons:

• many pages are created by API or plug-ins by authors you want to get rid of (maybe they are not correctly created)
• authors often collects unwanted pages in draft state they don’t want anymore. From an amount on they don’t want do it one by one, because of the high workload.

This plug-in makes it easy for you to clear your draft pages all together with one click only. This is especially of great benefit if the author did not enter the mandatory elements!

Location in SmartTree
You found the plug-in under Administer Project Structure > Project. You can use it on SmartEdit as well, but I can not recomend a plug-in target for this plug-in. At Hapag-Lloyd I added it to the Tasks dialog of MS as a little hack.

How it works
First you need to confirm, that you want to get rid of all your pages in state draft of current project. The plug-in did not provide the list of draft pages.

After clicking on button Reset all draft pages the plug-in will come back to you with this result screen.

It lists all reset pages together with the action (undo or delete). From all pages it displays the headline and page ID.

It present the totals how many pages were deleted and on how many undo changes were called.

There can still be pages in draft afterwards, if the authorization of the the users has changed in between. This is the reason, why it checks again how many pages are even afterwards in draft.

Installation
This plug-in can be installed using the combined setup routine for all jRQL API based plug-ins. This setup contains all 18 plug-ins, but it's your choice which plug-ins you want to install.

Follow the instructions in the jRQL blog to download the installer and import the plug-ins you want.

The jRQL plug-ins addresses the following areas

• authorization plug-ins
• publication on pubishing reports plug-ins
• content classes plug-ins
• pages and multi links plug-ins

About jRQL API, this plug-in and Open Source
You can use this in contrast to most other MS plug-ins this plug-in depends on the underlaying general purpose Java API jRQL, but is still be easy to install.

The plug-in itself is Open Source and can be changed as you need while the jRQL API is distributed without source code.

Contact me
Please contact me via the jRQL blog. I don't want to put my address in clear text.

It shows a matrix of all elements by name and type and checks every Template Variant source code of the selected content class if the element is used. An element is considered to be used, if the element value itself or the red dot for this element is used.

The interpretation is up to the admin. Even an element is not used in any Template Variant, it cannot be deleted.

Benefits
After a while working on different content classes (or after creational work on new content classes) it is a good time for a re-factoring usually. This plug-in helped me a lot to identify unused elements, which I can delete. This keeps the number of elements as small as possible and didn’t confuses the content class developer with not needed elements anymore.

Location in SmartTree
You found the plug-in under Administer Content Classes > Folder > at every content class.

How it works
First, you need to navigate to the content class you want to investigate. Start the plug-in and it will immediately collect all content class elements and template variants and comes back to with a 2 dimensional matrix between these both.

(The title of this plug-in still uses the old name template instead of content class, because of the time of writing this plug-in this was the correct name.)

Beside element name and type you get right of column “Used?” one column for every Template Variant the selected content class have.

Each of this Template Variant columns show yes on an element row, if the element itself or it’s red dot is used, otherwise it will be blank. Blank means the element is not used!

Very important is the 3. column, because it aggregates all Template Variant column values. A no in 3. column is displayed in yellow, because these are the elements which might be deleted, because they are unsed.

Installation
This plug-in can be installed using the combined setup routine for all jRQL API based plug-ins. This setup contains all 18 plug-ins, but it's your choice which plug-is you want to install.

Follow the instructions in the jRQL blog to download the installer and import the plug-ins you want.

The jRQL plug-ins addresses the following areas

• authorization plug-ins
• publication on pubishing reports plug-ins
• content classes plug-ins
• pages and multi links plug-ins

About jRQL API, this plug-in and Open Source
You can use this in contrast to most other MS plug-ins this plug-in depends on the underlaying general purpose Java API jRQL, but is still be easy to install.

The plug-in itself is Open Source and can be changed as you need while the jRQL API is distributed without source code.

Contact me
Please contact me via the jRQL blog. I don't want to put my address in clear text.

This plug-in shows for a selected content class all container and list elements where the selected content class is among the list of preassigned content classes. See the documentation in the jRQL blog.

Benefits
If you work with content class preassignment, this might be a handy tool for you to check if your preassignment are still correct and consistent with other ones.

Because the MS do not offer such a back reference out of the box, I see a need to write this scanning routine to find all lists or containers where a content class is preassigned.

If I need to change something on the preassignment I used this plug-in’s result as a working list. Copying this list of preassigned to Excel and go through the found elements one by one and correct it.

Location in SmartTree
You found the plug-in under Administer Content Classes > Folder > at every content class.

How it works
First navigate to the content class, whom preassignment you want to check. This plug-ins uses the old name Template instead of content class, because of the time it was written.

The folder and the content class is echoed back to you. Furthermore you can choose what folders you need to scan.

Use <all folders> if you are unsure. If you know, that only a specific folder needs to be scanned, you can select it from the list. This will, of course, speed up the search.

Because this scan can take several time, the plug-in keeps you informed about the progress.

After it finishes the search you get the following result table of all elements having image_block preassigned.

At the bottom you found the total number of elements found. You can use this list as a working list copying it to Excel and go through it one by one.

Installation
This plug-in can be installed using the combined setup routine for all jRQL API based plug-ins. This setup contains all 18 plug-ins, but it's your choice which plug-ins you want to install.

Follow the instructions in the jRQL blog to download the installer and import the plug-ins you want.

The jRQL plug-ins addresses the following areas

• authorization plug-ins
• publication on pubishing reports plug-ins
• content classes plug-ins
• pages and multi links plug-ins

About jRQL API, this plug-in and Open Source
You can use this in contrast to most other MS plug-ins this plug-in depends on the underlaying general purpose Java API jRQL, but is still be easy to install.

The plug-in itself is Open Source and can be changed as you need while the jRQL API is distributed without source code.

Contact me
Please contact me via the jRQL blog. I don't want to put my address in clear text.

• Page Id
• Page headline
• Content class name
• Created by user name
• Created on date
• Last changed by user
• Last changed on date
• State (draft, released)
• Released on date

Depending on your display settings “Unreleased pages” get even unsubmitted pages from other authors. This makes this plug-in a perfect tool for all support persons.

Benefits
You get a fast overview of a bunch of pages linked to a list or container, instead of getting only the headline of a single page. This plug-in centralize a lot of data, which normally are wide spread into different dialogs and takes too much time to collect. From my experience the headline itself is not enough to get an overview on pages other authors created.

If you have to support authors within workflow, I recommend this tool to get the full overview of the pages and which pages are changed last. You can see immediately which pages are at which step in the workflow and are ready to answer questions on the phone quickly.

This plug-in works in SmartEdit as well. See below how to activate it.

Location in SmartTree
You found the plug-in under Administer Project Structure: at every List or Container.

How it works
Immediately after click on the plug-in title it will start immediately to collect all page details information. In contrast to other plug-ins there is nothing dangerous happening and no other data needs to be request, so this plug-in rushes ahead without further click needed.

The plug-in tells you at the bottom of the page the full amount of pages linked to this list or container.

Make this plug-in available for SmartEdit authors
This plug-in is not but can be easily activated in SmartEdit as well. Simply add the plug-in target ioDevDialogEditMultiLink and your authors using SmartEdit will get this plug-in on the list or container menu.

Installation
This plug-in can be installed using the combined setup routine for all jRQL API based plug-ins. This setup contains all 18 plug-ins, but it's your choice which plug-ins you want to install.

Follow the instructions in the jRQL blog to download the installer and import the plug-ins you want.

The jRQL plug-ins addresses the following areas

• authorization plug-ins
• publication on pubishing reports plug-ins
• content classes plug-ins
• pages and multi links plug-ins

About jRQL API, this plug-in and Open Source
You can use this in contrast to most other MS plug-ins this plug-in depends on the underlaying general purpose Java API jRQL, but is still be easy to install.

The plug-in itself is Open Source and can be changed as you need while the jRQL API is distributed without source code.

The functionality could be easily extended. Simple enhance the showChildDetails.jsp in the webapp jrql with other page details. Please refer to the available methods on class Page, for instance Page > getFilename().

Contact me
Please contact me via the jRQL blog. I don't want to put my address in clear text.

It shows a table with following columns:

• Element name
• Element type
• One value for all LVs
• Different values per LV

Please have in mind, that headline elements are treated differently from version 9.0.1.49. This attribute is moved from headline elements to the content class itself.

Benefits
The MS decides after the content class element attribute “language-variant independent” if a page of this content class will appear in the translation editor’s list of pages waiting for translation.

This is quite difficult to handle, because a typical content class has a quite big amount of elements. Checking each of them to decide if the setup is correct wastes a lot of time.

This plug-in collects this attribute’s value and present it to you for an perfect overview and checks of the translation editor setup.

Location in SmartTree
You found this plug-in under Administer Content Classes > Folder > at every content class.

How it works
First you need to navigate to the content class you want to check. Start the plug-in and immediately afterwards it will collect the needed information. The result is presented to you in the following table.

Important notice for headline elements
Don’t forget to check the state of the content class attribute “Adopt headline to all language variants”. This is introduced in V9.0.1.49. Since that version the headline elements are not included into the table.

It marks elements green, if a red dot in Smart Edit is included in the Template Variant of project’s display Project Variant. This means that the translator can access it, what is treated green = correct.

It marks elements in red, where no red dot is found. This is often wrong, because a translator will get this page for translation, but cannot access the elements needed for translation.

At the bottom the plug-in summarize the totals of all elements at all, how many of them having the same value on all language variant and how many have different values.

Installation
This plug-in can be installed using the combined setup routine for all jRQL API based plug-ins. This setup contains all 18 plug-ins, but it's your choice which plug-ins you want to install.

Follow the instructions in the jRQL blog to download the installer and import the plug-ins you want.

The jRQL plug-ins addresses the following areas

• authorization plug-ins
• publication on pubishing reports plug-ins
• content classes plug-ins
• pages and multi links plug-ins

About jRQL API, this plug-in and Open Source
You can use this in contrast to most other MS plug-ins this plug-in depends on the underlaying general purpose Java API jRQL, but is still be easy to install.

The plug-in itself is Open Source and can be changed as you need while the jRQL API is distributed without source code.

Contact me
Please contact me via the jRQL blog. I don't want to put my address in clear text.

By using the comfortable multi-selector you can select and remove several keywords at once. The translation interface allows you a manual translation of keywords into all required languages. Especially maintaining multiple-language projects will be much easier this way. Working with our KEYWORD EXEPRT will save your time and money!

FEATURES

• plugin for Management Server (from v7.5)
• multiple selection of keywords
• internationalization/translation of keywords

ADVANTAGES

• one click operation for setting multiple keywords 
• a foreign language translation allows international editors a simple and intuitive handling of keywords
• save time with multiple selection and translation
• intuitive handling

Online business intelligence has come a long way and any kind of Web metrics tools can be obtained at little or no cost.

Nevertheless, most of these tools are designed for site administrators. Little or no convenience is there when one needs to organize and present contents on basis of the rich set of statistics these tools provide.

Even if a Web service API allows one to interact with such tools, the limitation on the granularity one can achieve with an API call or the performance overhead of making the call itself present some serious deterrents to a seamless incorporation.

This document shows you how easy and convenient it is to take advantage of LiveServer's out-of-the-box functionality to set up universal page hit counting; since the hit count persists in LiveServer, it is indexed and can be used by Verity Search to sort contents on basis of page views.

Such a handy feature can be implemented on a search result page where matching contents can be sorted on basis of popularity.

SECTION B - HOW

B.1 DEFINE THE HIT COUNTER AS A CONTENT ATTRIBUTE

The first step is to configure a universal content attribute designated to represent page views. In the example we are going to illustrate, such attribute is defined as "pageview".

Go to LiveServer server administration menu and select "Assign Content Attributes" under Connectors->Search Engines:

B.2 MAP THE HIT COUNTER AS AN INTEGER IN VERITY SEARCH
 
Once the configuration dialog opens, proceed to define the properties of "pageview":

Content attribute - the name we have decided to assign to the attribute we are defining, in this particular case, the hit counter.
Search engine field - the name under which this content attribute is stored in Verity Search Engine. It is not mandatory to have the same name as the content attribute.
Search engine field type - Verity Search is capable of conducting SQL syntax complex search on contents deposited in LiveServer; however, this capacity is only enabled on content attributes that are mapped as search engine fields. All else is text based search.

In this particular case, we select Integer as the search engine type for "pageview" simply because we want to be able to use this attributes as a real numeric, not just a string literal that represents the numeric.

Once it is mapped as an Integer, we will be able to use SQL syntax on it when conducting search, such as > (greater than), <(less than), =(equal) or !=(not equal).note 1

Note 1. The SQL syntax listed here is for narrative purposes and do not represent the actual syntax required by LiveServer query dynaments. Please consult your LiveServer dynament menu for relevant information.

B.3 EMBED THE HIT COUNTER DYNAMENT IN PAGES

In all pages that require the hit counter, we will need to embed a simple dynament that increment the hit counter value and persist it in data base:

This simple dynament broken down and explained as follows:

<rde-dm:attribute mode="write" op="increase" attribute="content:pageview" value="1" />

mode - Whether the dynament is supposed to read or write the attribute value into the page's metadata.
op - How the value is written. In this particular case, the value is to increase.
value - By how much.

B.4 SEE THE COUNTING ACTION

Upon this point, we have defined the counting mechanism (the dynament) and its corresponding data field. Now you can fire up your browser, visit the page(or pages) that have the aforementioned dynament embedded.

Depending on how many times you've viewed (loaded ) a specific page, when you go into content administration and click on that page's "Attribute" tab, you will see the "pageview" value:

Please note the aforementioned dynament can be embedded from RedDot CMS page template; it does not have to be manually inserted on page instances in LiveServer.

To put the counter on the page itself, a simple dynament as follows will do it:

<div>This page has been viewed <rde-dm:attribute mode="read" attribute="content:pageview" tag="notag" /> times.</div>

In a query dynament, you can specify [sortedby="pageview" sortorder="desc"] to achieve search result sorting by content popularity.

There were issues with the redlining implementation until Management Server release 10.1. It was decided to fully replace the existing implementation with a new one that does structural HTML differentiation and that operates on the documents HTML tree structure instead of comparing pure text. The new redlining component visualizes both text and structural changes in Web content.

The Redlining Patch is compatible with the existing redlining component to ensure easy replaced in Management Server installation prior to version 10.1.

Der Navigation Manager funktioniert laut Spezifikation nur im MS Internet Explorer. Durch diese Erweiterung kann der Navigation Manager-Funktionalität auch in anderen Browsern verwendet werden. Getestet ist die Erweiterung für MS-Internet Explorer 6, 7, 8, Firefox 3.6, Opera 10.10 und Konqeror 4.4 im Open Text Management Server Version 9.0.1.x und 10.1.x. Sie sollte ebenso in der Version 7.5.x anwendbar sein.

Zur Installation muss die Datei Event.js (in ZIP Datei RedDot_NavigationManager enthalten), heruntergeladen werden und die Originaldatei

%PATH%\CMS\ASP\Navigation\Library\Events.js

ersetzen. Diese wurde im Originalcode nicht geändert, sondern nur um einen Teil für die zusätzlichen Browser erweitert (ab Zeile 86).

Stellt sich die Frage, wie der Navigation Manager im Management Server Version 10 aufgerufen werden kann, da dieses nur über das Kontextmenü möglich ist und daher bei den genannten Browsern nicht funktioniert. Hier bietet sich z.B. ein eigener RedDot an (N-RedDot, u.g. Platzhalter RedDot_NavigationManager), der den Navigation Manager öffnet. Siehe RedDot_NavigationManager im Download Bereich.

Es gibt noch eine weitere Erweiterung zur automatischen Aktualisierung des SmartEdit-Bereiches nach Änderungen im Navigation Managers.

The Navigation Manager is specified for use with the MS Internet Explorer only. This extension enables MS-Internet Explorer 6, 7, 8, Firefox 3.6, Opera 10.10, and Konqeror 4.4 to use the functionality within Open Text´s Management Server Version 9.0.1.x and 10.1.x. It should also work in version 7.5.x.

The attached file Event.js is to replace the original file

%PATH%\CMS\ASP\Navigation\Library\Events.js

The original code was not modified but added with additional functions for the other browsers (added code starts in line 86).

Finally the Navigation Manager in Management Server Version 10 needs to be called through the context menu but this menu entry is not shown in other browsers beside the MS IE. Therefore a new red dot has been proposed/generated/introduced (N-RedDot, RedDot_NavigationManager image placeholder) to call the Navigation Manager directly within an opened page.

There´s another extension available that refreshes the SmartEdit page after using the Navigation Manager.

When working with Management Server / RedDot CMS, there are numerous tasks which are dead simple, but hard to automate via scripting. Content migrations, redesigns or the set up of a new project from scratch are good examples. Sometimes there's time consuming tasks, but your inhouse cms resources are booked out or too valuable/expensive for this kind of job. The idea behind the OpenText RedDot Content Workers is to have a cheap team of low level editors who are already trained in SmartEdit (very roughly in Navigation Manager and SmartTree) so that they can instantly step in a start working.

Our offer:

• "Copy and paste" content migrations
• Building a project structures in SmartTree / Navigation Manager based on an Excel file
• Manual QA and corrections after script based content migration
• Any time consulming job which is quickly explained

Our team:

• trustworthy, highly dedicated digital natives
• basically trained in SmartEdit, SmartTree and Navigation Manager
• Language skills in German, English and Polish
• Backed up with high level support by a CMS Senior Consultant

Interested?
Call: +49 160 96589735

Core Features:

• Native search by id or headline supporting wildcards
• Cascading filters depending on search results
• Sorting results by various parameters
• State management. 
• The native paging guarantees high performant response.
• CTM package check (optional)
• Smart Edit translation marking (optional)
• Smart Edit CTM package marking (optional)
• One-Click content adoption of selected content from source to target language (including image and media elements)

Core features:
Integrated wildcard search for users assigned to current project
Integrated security check for page ownership or administator rights to perform the task

This Software is provided "AS IS" without any warranty of any kind. If you encounter any bugs or require any new features, please feel free to contact Open Text Global Service.

The way the module is designed, it also allows completely new concepts which still are open topics to the core product:

• Global Elements (per project, even per server)
• Custom Form Modes
• Support for Radiobuttons, Checkboxes, etc.
• No more optionlists ! (Time consuming and error prone)
• many many more :)

Core features:

• HTML/XML PlugIn building
• FakeReddot generator handling authorizations and locks
• Build-in session handling
• jQuery/jQueryUI automatically included
• Examples for e.g. Tabs, Accordion included
• Including of external data (e.g. XML from fileystem or CMS elements)
  • More to come (e.g. LDAP, Webservices, Databases)
• XML/XSL Rendering of data selections
• Full multi language support

Optional features:

• Action extension by programming own dlls and dynamically including them (similar to custom RenderTags)
• Requires C#/.NET know-how
• Usage of build-in RQL Api and/or Database Handler
• Usage of own C#-APIs
• Session Handling performed by DialogEngine

Core Features:

• Restriction on uploadable filetypes per AssetManager
• Configuration and control of file names
• Configuration and control of assetmanager attributes
  • usage of: Input fields, dropdowns, checkboxes and radiobuttons
• CrossBrowser java based dropzone
• Configuration inheritance
• Administration UI

The FileUploader is available as mass or single upload version and is integrated into ImageGallery and ImageSelector (OTGS Modules), if required and available.

Core Features:

• CrossBrowser (java-based) Dropzone file upload.
• XML-based modyfiable gallery definition language (GDL:Gallery Definition Language) 
• Otional  thumbnail generation using ImageMagick. 
• Single CMS-page per gallery
• Own translation view allowing gallery texts to be translated in a split mode
• Optional integration into FileUploader Module (offered seperately).

Useful fields of application could be to maintain your corporate design in size in styling where the image provider and uploader is not responsible for the fitting of images but the selector and editor of a specific page is.

This module allows to make freely definable versions of an image selectable where dimensions can be predefined at the content class. The main image is selectable as usuals from the asset manager (or uploadable using the FileUploader) where the perfect fit image size based on the main image can be selected via radio buttons. If the selection does not suit the predefined sizes needs, a crop dialog automatically prompts where the editor has to selected a valid image area based on the predefined mandatory image dimensions. The selected area will be stored in a defined location within the asset manager of the main image. Attributes will be copied so that the image becomes a valid child selection of the main image.

Core features:

• Selectable objects configurable per project
• Drag&Drop user selector
• Typeahead filter supporting wildcards

The report also provides various stats and figures which can also help identify the status of each pages as well as their workflow details which enables and empowers end users to identify where to locate pages and which users are involved in the release and completion of the content. 

Some of the reports included in this plug-in allows the end user to modify certain contents straight from within the report. Print functions have also been implemented which imports the reports into easy to use MS Excel format for further manipulation and formatting. This plug-in encompasses various reporting aspects and categories based on client needs which ranges from workflow, page status, expiration, linking & appearance, filename, URL status, user based reports and various project based reports.  

OTGS Management Server Reports also has a plug-able design so you or services can build new reports to fit you needs.

This module is available for purchase in North America and Australia. If you are interested in this module please contact asowsm@opentext.com

Core features:

• Treeview of complete page object
  • States of all subpages displayed
• Available actions (restrictable and groupable): save, release, discard, reject, submit for translation, publish and delete
• Evaluation of authorization packages
• Diplay of missing mandatory fields
• Restriction of available languages and project variants when publishing or translating
  • (Restriction per language if required)

Core features:

• Two step synchronization:
  • Step 1: ContentClasses using selective and automated TreeExport
  • Step 2: Online adaption of structural preassignments (e.g. references and content class preassignments) 
• Including page definitions
• Protocols documenting sync actions (when and by whom)
• Recently changed classes displayable and selectable
• Sync automatically creates a new version if content class versioning is activated
• Support of Master->Child szenarios
  • Packages can be imported into child project to update content element preassignments (step 1)
  • A child project on server 1 can update its corresponding childproject on server 2 in step 2 (requires name uniqueness for content classes)
• Support of manual package import if the servers do not see themselves in the network

• CVS-Support including asset assignments to image and media elements
• Automated checking of transport packages
• Manual single class checkin

The module does not synchronize content.

Core features:

• Overview of project and dialog languages
  • display order and dialog language apperance configurable per project and globally (as default)
• Data import and export as xml (for external translation)
• XML importable eg. into Microsoft Excel (see screenshot)
• partial re-import 
• (optional) Build-In Google-Translate translation for dialog languages

OpenText Professional Services has developed a prebuilt Responsive Web Design based on Twitter Bootstrap. This contains samples for best practices in navigation, site structure, and template design. This solution also contains several common content class types including tabs (with stateful editing enhancement), accordions, photo gallery, filmstrip, video, news articles, events listings, and jQuery Full Calendar Event Calendar. Reskinning it can be as easy as buying a Bootstrap design from existing communities or a few days of professional services with OpenText's Creative Services. 

This solution is available for purchase from OpenText, in North America contact your account executive to purchase ask for pricing referencing:

P-RDT-RWDPROJ (Web Site Management Responsive Web Design Pre-Built Project for WSM )

In other regions contact your OpenText Professional Services team.

Please follow the Find Out More link to download the plugin. Note, an Open Text Knowledge Center login is required.

Advantages:

• automatic documentation,
• consistent standard of projects,
• summary of single project configurations and content-classes,
• time-savings in comparison with manual compilation

• A big fat clickable Open/Close button for the page
• A number of customisable clickable buttons that can trigger any RQL plugins/scripts that you wish to integrate into your project
• Basic page information that is displayed to the user regardless if the page is open or closed.

The toolbar has gone through a number of different incarnations since the initial version – most of which were around improving performance (it now uses asynchronous AJAX calls to obtain page information via RQL). Installation is a piece of cake too – just a simple cut and paste job.

What versions of the CMS are supported?

At this point in time, the toolbar is only supported in RedDot CMS Version 10+ – and requires the use of ‘master/foundation’ page project setups. I have no plans to make it work with target containers – as I’m a firm believer of staying well away from them from a usability and maintenance perspective!

As mentioned, you can customise the bar in any way you like. Everything is controlled using JavaScript/JQuery and CSS. All you need to do is create a new button (using the Photoshop template provided), add the required HTML/CSS and attach a jQuery event to it. (As an example of how to do this, ive included two plugins as part of the installation – ‘checkbox keyword assignment’ and ‘one click page workflow submission’.

Installation

1. To install, simply unzip the file into the plugins directory. Make sure that the ‘rdToolbar’ is sitting in the root of plugins folder.

2. Add the required javascript and CSS for the toolbar – id suggest adding this in a global location where it can be referenced across the whole site (such as a header/JS/CSS container)

<script type="text/javascript" src="/cms/plugins/rdtoolbar/common/js/jquery.pack.js"></script>
<script src="/cms/plugins/rdtoolbar/common/js/rdToolbarStatus.js" type="text/javascript"></script>

<link rel="stylesheet" type="text/css" href="/cms/plugins/rdtoolbar/common/styles/menu.css" media="all" />
(make sure that references points to the location of your plugins directory)

3. Add the following code directly after the body tag.

<!IoRangeRedDotMode>
<div style="display:none;"><!IoRedDotOpenPage></div>
<div id="reddot-menubar"></div>
<script type="text/javascript">
jQuery(document).ready(function() {
// set up page variables
rdToolbarStatus.vars.pageguid = '<%!! Context:CurrentPage.Id.ToString(N).ToUpper() !!%>';
<!IoRangeRedDotEditOnly>rdToolbarStatus.vars.pagemode = '1'<!/IoRangeRedDotEditOnly>
rdToolbarStatus.vars.defaultextension = '.htm';
// run the plugin
rdToolbarStatus.init();
});
</script>
<!/IoRangeRedDotMode>

Theres no need to add any placeholders for this to work. Just cut and paste directly into your foundation templates

RedDotAutoLabel is an inline plug-in for Management Server that labels RedDots automatically with the Placeholder Description thus cutting development time and removing clutter from the Content Class.

Without RedDotAutoLabel...

<!IoRangeRedDotMode>
<div class="smartedit-block">
<!IoRedDotOpenPage> [<!IoRangeNoEditMode>Open<!/IoRangeNoEditMode><!IoRangeRedDotEditOnly>Close<!/IoRangeRedDotEditOnly> <%hdl_PageTitle%>]
</div>
<!/IoRangeRedDotMode>
<!IoRangeRedDotEditOnly><div class="smartedit-block"><!IoRedDot_hdl_PageTitle> [Edit Page Title]</div><!/IoRangeRedDotEditOnly><h1><%hdl_PageTitle%></h1>
<!IoRangeRedDotEditOnly><div class="smartedit-block"><!IoRedDot_txt_Body> [Edit Body Text]</div><!/IoRangeRedDotEditOnly><%txt_Body%>

With RedDotAutoLabel...

<!IoRedDotOpenPage>
<!IoRedDot_hdl_PageTitle><h1><%hdl_PageTitle%></h1>
<!IoRedDot_txt_Body><%txt_Body%>

Pre-requisites

RedDotAutoLabel requires jQuery.

Usage

1. Extract the plug-in to your PlugIns folder.
2. Add the following code to the <head> area of your Content Class(es):

<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"></script>
<!IoRangeRedDotMode>
<script src="/CMS/PlugIns/RedDotAutoLabel/RedDotAutoLabel.js"></script>
<link rel="stylesheet" type="text/css" href="/CMS/PlugIns/RedDotAutoLabel/RedDotAutoLabel.css" />
<!/IoRangeRedDotMode>

Inserting Auto Labels

Nothing! Just insert the RedDot Placeholder and provide a meaningful Description on the Placeholder. The plug-in will do the rest:

<!IoRedDot_hdl_PageTitle>

You don't even need !IoRangeRedDotMode tags as the only code generated is the RedDot Placeholder which is - of course - removed automatically.

Removing Auto Labels

The plug-in assumes that labels are the more desirable state (if you're using it, then it makes sense that you'd want them in most cases). If you don't want a label on a particular RedDot, just wrap the RedDot Placeholder in a "NoAutoLabel" Class:

<!IoRangeRedDotEditOnly><span class="NoAutoLabel"><!IoRedDot_anc_Link></span><!/IoRangeRedDotEditOnly>

Customising

You can change the look and feel of RedDot Labels by customising the styles in RedDotAutoLabel.css.

You can change the Label itself by modifying the jQuery in RedDotAutoLabel.js.

Limitations

Labels will be added to every RedDot regardless of whether a Description is entered. In the abscence of a Description, the Placeholder Name is inserted. The obvious exception to this is if you use the NoAutoLabel class.

There are some Placeholders that you can not set Descriptions on natively (as I was reminded by Jian). The "Set Element Description" plug-in provides this functionality to all Placeholders that don't natively expose the Description attribute and can be downloaded from the Downloads section above.

Replace template while importing in element properties

Hilights:

1. Uses Jquery and AJAX to send RQL
2. Easy to install
3. Other than RQL communication, all processing are done client side.  Minimal server load.
 

Installation:

1.  Unzip zip (including folder within) to Management Server plugins directory
2.  Import plugin via Server Manager interface
3.  Assign plugin to project
 

Accessibility:

In SmartTree, select template, "Replace Template Plus" from action menu

http://simplyreddot.blogspot.com/2012/02/retroactive-references-2.html

This sample dialogue/plugin first checks if the form has been submitted. If not, then some HTML form elements are displayed (figure 1). If the form has been submitted, the form values will be received and can then be used for any RQL based logic.

As this sample is based on an original Management Server dialogue, the look and feel of your application is very similar to the look and feel of the Management Server. So just delete the stuff you don't need and start programming.

• Remote control via SOAP
• High objective context with value holders and xml data binding
• Dynamic building of RQLs with builder pattern support
• RQLs execution are managed by controller pattern, so you have access to every past RQL result

This library uses the Apache Axis 1.4 library to communicate with the Management Server via the SOAP specification. This requires that your Management Server installation has been done with SOAP Support enabled. There are also plans to eventually support remote calls over a native http interface in the near future as well.

This project is built via Apache Maven, meaning that if you add it as a dependency to another Maven project, its dependencies will be managed automatically for you. For example, Maven will download the relevant Castor and Apache Axis libraries for you. Currently this API is targeted for Open Text Web Site Management Server versions 7.5 and newer.

For more inforamtion and download take a look at the project page

The plugin is constantly updated.
Download latest version from:

http://simplyreddot.blogspot.com/2012/02/rqlconsole.html

Even if you don’t care about SEO, such as if you have an Intranet, there is still great benefit in having human readable and friendly URLS that represent what the page is about rather than those ugly random characters (called GUIDS).

The module works on versions of RedDot CMS from 7.5 upwards and Open Text Web Solutions Suite 10.1

What kind of difference will it make to site traffic?

A lot. There’s no exact science to this because of other factors that also make a difference but from our experience you can expect at least 30% improvement to traffic simply as a result of making the URLs more search engine friendly. Combined with other factors such as page structure and the results can improve beyond that. So if that sort of traffic improvement appeals to you weigh it up against the cost of this module.

How much is it?

We’re selling the module for US$2,000 and it is licensed for each installation of the CMS. Review the licensing in the package for complete details.

How do I get it?

Just send us an email with your name and organisation to enquiries@areeba.com.au and we’ll send you out the product with full documentation and a licence to trial it. If you’re happy with the module, and I’m sure you will be, just wire us some money and the module will be fully licensed for commercial use.

How long will it take to install?

We’ve prepared comprehensive step-by-step documentation and you should be able to get the module up and running on your projects in less than an hour.

What if I have an existing project with lots of pages?

If you’re starting a new project the SEO module is almost an essential starting point and nothing more is required.

However, if you have an existing project with lots of pages Areeba have also built a script which we’re licensing separately for US$2,000 which will go through the entire project and assign the friendly filename on every page for you. So you would back up the project, run the script and re-publish the project. The script is not essential but is a real time saver for existing large projects and if you have multiple projects.

SmartAPI is the extension of SmartEdit and SmartTree in regard of developing. Where SmartEdit allows you to edit conveniently and SmartTree makes administration in your browser possible, SmartAPI creates a comfortable programming interface for the OpenText WSM Management Server.

The complete library is written in C# / .NET and can be used from within the CMS as plugin or from an external .NET (web) application. As .NET is being used there is no break in the technology you use and the application can be hosted directly in your Windows Server in the IIS. You do not need any other hardware or server installed.

The goal of SmartAPI is to provide a comfortable, fully object-oriented and well-tested library for all developers and users of OpenText WSM. There is no expensive in-house development necessary but you can choose a ready-to-use library that just works.

Our motivation

A lot of our customers have developed there own solution to use the RQL interface by using PHP, Java, and .NET applications and libraries. Those applications are developed among their daily business and sometimes lacks of a good concept as well as testing.

Internally, we at erminas have developed a fully object-oriented library for the Management Server the solves these issues. We are using this library for internal projects, our products as well as for our customers. We decided to release this library to give more developers and companies the chance to take advantage of such a library.

SmartAPI can be downloaded and used free of charge as it is licensed as GPLv3. You can develop your own application using SmartAPI and distribute them as long as they are licensed as GPLv3 as well. If you do not want to distribute your own source code there is also a commercial license that you can find at License. We are happy to welcome other developers to join us developing this libary, you can find more information at Contribute.

Current state and further development

For releasing the SmartAPI as an Open Source project we have decided to redesign parts of the API. A first state is finished and released today. This first version includes fundamental functions for Content Classes, Pages, and Workflows. All functions are tested thoroughly using our internal test projects.

The next steps are to create a Management Server test project that we can distribute. Together with this CMS test project we release our .NET test project which is currently strongly bound to our internal test projects. After that, we extend the library to meet our customers and product requirements. We are looking forward to your suggestions and input to this library.

Due to the German origin of this plugin the more detailed description is following in German language. Comments and variables in the source code are German, too. Don't be annoyed, please.

 
Dieses Plugin wurde entwickelt um SmartEdit Benutzern die Möglichkeit zu geben, den Inhalt einer Seite von der deutschen in die englische Sprachvariante zu kopieren. Dafür benötigt man hiermit keinen Translation Manager. Im Dialog zum Anlegen der englischen Version wird zunächst überprüft, welche Sprachvarianten z.Z. zur Verfügung stehen. Dann erhält man die Option, den deutschen Inhalt zu übernehmen.
 

Gestartet wird das Plugin im SmartEdit über >Aktionen >Plugins >Englische Version pruefen und setzen. Nach dem Schließen empfiehlt es sich unten links die Sprachversionsauswahl zu betätigen und auf Englisch umzuschalten, da durch das mehrfache hin- und herschalten im Plugin ein
undefinierter Zustand entsteht.
 

Alternativ kann man die Seite englische_version_1.asp aufrufen und dort die Seiten-ID der zu übersetzenden Seite angeben.
 

Es wurde genau für unsere Bedürfnisse programmiert und daher sind einige IDs und die Kopierrichtung von Deutsch nach Englisch fest im Quellcode verdrahtet. Entsprechende Konstanten sind jeweils im Kopf der asp-Seiten vorhanden und müssen angepaßt werden.
 

Im Zip-Download gibt es eine readme.txt mit einer kurzen Installationsanleitung. 

Das Plug-in wird "so wie es ist" zur Verfügung gestellt. D.h. es gibt keinen Support dafür und es kann keine Gewähr für die Funktion und keine Haftung bei Fehlfunktion gewährt werden.

All cms pages that build your foundation page are determined automatically and displayed (including the current status) in a convenient way. Submitting all changed or new pages needs only one click.

Download and install the TinyMCE plugin

• Produces clean and valid XHTML code
• MacOS and Windows Compatible Editor (FireFox recommended for MacOS)
• Integrated Asset manager for images
• Linking to an asset (ex: pdf)
• Referencing a page
• Save without closing the window
• Full code cleanup based on CMS template permissions  (see Customizing the Editor)
• Only Edit via Form functionality requires changes to RedDot code - basic editting supported in multiple browsers by default

This module is available for purchase in North America. If you are interested in this module please contact asowsm@opentext.com

Note:
Currently the solution provides offline only template editor access, with no active synchronization to obtain content class templates.