4 replaced http://tridion.stackexchange.com/ with https://tridion.stackexchange.com/
source | link

Escaping would be a way as @user978511 suggests@user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meet your requirements.

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meet your requirements.

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meet your requirements.

3 edited body
source | link

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meatmeet your requirements.

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meat your requirements.

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meet your requirements.

2 added update based on comment,
source | link

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meat your requirements.

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Escaping would be a way as @user978511 suggests, but RSS feeds are valid XML, so you can simply keep the tridion:href attribute in your links as long as you add the appropriate namespace to your XML.

The correct namespace for the tridion prefix would be http://www.tridion.com/ContentManager/5.0, you can add that to the rss root element of your feed XML:

<?xml version="1.0" ?>
<rss version="2.0" xmlns:tridion="http://www.tridion.com/ContentManager/5.0">
    ...
</rss>

Update

You will need to adjust your Component/Page Template to keep the tridion:href attribute from being resolved. Most likely you currently have the Default Finish Actions Template Building Block in your Component Template, which contains the Link Resolver TBB, and that is responsible for resolving the link.

If you require a specific output, you have to create a custom Component Template (and possibly also a custom Page Template with that) to ensure you meat your requirements.

1
source | link