Navigation path

Links to RAPID's articles and feeds in the CWCMS

This document describes how to manage your links to RAPID's articles and feeds following the release of the new RAPID website.

 

How did it work before the release of the new RAPID website?

The most important change for all links pointing to articles and feeds from RAPID will be the format of URL.
 

How does it work after the release of the new RAPID website?

This new format of URL will impact the way you work with RAPID's feeds in your templates and in the dynamic links of your linkgroups.
 

What impact on your old developments?

You should normally not update old developments.
 

Links in your old documents

  • Old links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
  • Old links to feeds from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
 

Links in your old templates

  • Old links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
  • Old links to feeds from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
 

Links in your old linkgroups

  • Old external links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
  • An old dynamic link to a feed from RAPID should be kept as it is.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
 

Links in your old large linkgroups

  • Old external links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
  • Old dynamic links to feeds from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
 

What impact on your new developments?

You should preferably use the new format of URL in new developments.
 

Links in your new documents

  • New links to articles from RAPID should preferably be written in their new format of URL.
  • New links to feeds from RAPID should preferably be written in their new format of URL.
 

Links in your new templates

  • New links to articles from RAPID should preferably be written in their new format of URL.
  • New links to feeds from RAPID should preferably be written in their new format of URL.
 

Links in your new linkgroups

  • New external links to articles from RAPID should preferably be written in their new format of URL.
  • A new dynamic link to a feed from RAPID should preferably be written in its new format of URL.
 

Links in your new large linkgroups

  • New external links to articles from RAPID should preferably be written in their new format of URL.
  • New dynamic links to feeds from RAPID should preferably be written in their new format of URL.
 

What impact on your current developments

You should preferably keep the old format of URL for your old links and use the new one for your new links in current developments.

If you are still updating the current documents, templates and linkgroups more than one or two months after the release of the new RAPID website, we suggest planning the conversion of your old links to the new format of URL.

Please do not convert old links in documents, templates and linkgroups which have been archived or which you do not need to update on a regular basis.

 

Links in your current documents

  • Old links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
    New links to articles from RAPID should preferably be written in their new format of URL.
    Even if we do not recommend it, you can mix links in their old and new formats of URL in the same document.
  • Old links to feeds from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
    New links to feeds from RAPID should preferably be written in their new format of URL.
    Even if we do not recommend it, you can mix links in their new and old formats of URL in the same document.
 

Links in your current templates

  • Old links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
    New links to articles from RAPID should preferably be written in their new format of URL.
    Even if we do not recommend it, you can mix links in their old and new formats of URL in the same template.
  • Old links to feeds from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
    New links to feeds from RAPID should preferably be written in their new format of URL.
    Even if we do not recommend it, you can mix links in their new and old formats of URL in the same template. Please be careful not to import duplicated articles from two different feeds. You should check both old and new formats of URL for each article in the list.
 

Links in your current linkgroups

  • Old external links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
    New external links to articles from RAPID should preferably be written in their new format of URL.
    Even if we do not recommend it, you can mix external links in their old and new formats of URL in the same linkgroup.
  • An old dynamic link to a feed from RAPID should be kept as it is.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
    A new dynamic link to a feed from RAPID should preferably be written in its new format of URL.
    You can import only one dynamic link in a linkgroup. Even if we do not recommend it, you can import a dynamic link in its old format of URL in a new linkgroup.
 

Links in your current large linkgroups

  • Old external links to articles from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one.
    New external links to articles from RAPID should preferably be written in their new format of URL.
    Even if we do not recommend it, you can mix external links in their old and new formats of URL in the same large linkgroup.
  • Old dynamic links to feeds from RAPID should be kept as they are.
    Indeed, RAPID will automatically convert the old format of URL to the new one with an additional parameter (&oldURL=true) in order to return old URLs for each article of the list.
    New dynamic links to feeds from RAPID should preferably be written in their new format of URL.
    You can import several dynamic links in a large linkgroup. Even if we do not recommend it, you can mix dynamic feeds in their old and new formats of URL in the same large linkgroup. Please be careful because duplicated links are detected by considering the URL of the imported article but, as the old format of URL and the new one are not considered to be the same, the application may not be able to detect the same article in two different feeds if it has two different formats of URL (old <> new).
 

Remark about dates

As the CWCMS supports only <date/> in English, the parameters "&guiLanguage" in Rapid v1 URLs or "&locale" in Rapid v2 URLs will not work if different than "=EN" which is, by the way, the default value.