What's New in Outbound Feeds

Developers

After deploying these updates, you may optionally set the height and width values for your ans-feature-block.

You can now define a resizerURLs object for each site's siteProperties in the blocks.json of your Outbound Feeds bundle to specify Resizer v2 URLs for each OBF environment.

Developers

To set the Resizer URLs per environment, add a resizerURLs object within each site's siteProperties to your blocks.json. Within that object, add keys relating to your environments, such as org-outboundfeeds-sandbox and org-outboundfeeds. The values are the Resizer v2 URL for each environment. For local development, you can also add a localhost key and the Resizer v2 URL for the environment you set your local to fetch content from. The following example is using sandbox for localhost.

"siteId": {
    "siteProperties": {
      ...,
      "resizerURLs": {
        "org-outboundfeeds-sandbox": "https://org-site-sandbox.web.arc-cdn.net/resizer/v2",
        "org-outboundfeeds": "https://org-site-prod.web.arc-cdn.net/resizer/v2",
        "localhost": "https://org-site-sandbox.web.arc-cdn.net/resizer/v2",
      },
    }
}

Replace the org and site values with what is specific to your configuration per site, and your Production resizerURL can be the domain you use rather than the raw Arc CDN.

Then remove the existing resizerURL because the resizerURLs object takes priority over it and is not used when resizerURLs is defined.

Additionally, for local development, add a environment/localhost.js with the variables:

module.exports = {
    RESIZER_TOKEN_VERSION: 1,
    SIGNING_SERVICE_DEFAULT_APP: "resizer",
    BLOCK_DIST_TAG: 'stable',
}

Refer to the Outbound Feeds Resizer v2 Configuration Guide for the full details on OBF 2.x setup.

Outbound Feeds 2.0 now includes support for Resizer V2, along with compatibility for both Engine 4 and Engine 5. This enhancement ensures Outbound Feeds can leverage the latest image resizing capabilities and performance improvements offered by Resizer v2. 

Developers

Configuration update for Outbound Feed Blocks

With the new update, outbound feed blocks automatically use Resizer V2 when you make the following changes are made in your outbound feeds feature pack.

environment/*.json updates to make:

blocks.json updates to make:

For each of your sites you may have a resizerURL key defined. This needs updated from https://{yourCDN}/resizer to https://{yourCDN}/resizer/v2 

After making the updates to your environment.json file(s), you must re-deploy your bundle in order for OBF 2.0 blocks to install with the latest published packages under the BLOCK_DIST_TAG.

Note: External images, like channel logos, do not pass through the resizer. Only ANS-based image data is resized. These URLs instead return as the raw URL they were entered as.

Configuration update for Custom Feed Blocks

To use Resizer V2 in your custom outbound feed blocks, you must define the environment variables listed previously. 

If you have custom content sources or custom feed blocks, you must update them to use the new signing service pattern. 

You will also need to update any OBF feed dependency versions defined in your package.json.

Refer to the Outbound Feeds Resizer v2 Configuration Guide for the full details on adopting Resizer v2.

Engine Compatibility

Engine 4 and 5 are available to deploy your OBF feature pack with. These versions introduce Node 16 and 18 compatibility, respectively. If you’ve added dependencies to your feature pack for custom development, you should verify in local development that your dependencies are compatible with Node 18 if deploying with Engine 5 and Node 16 or if deploying with Engine 4.

Invalid characters, like a backspace within an article, are now appropriately handled and do not cause an error in the feed. 

Update 2/20/24: The Arc-provided blocks in the 1.15 version of Outbound Feeds has been validated to be compatible with Engine 3, Engine 4 and Engine 5 – you may choose to deploy it with any of these options. However, if you have Custom Blocks you may need to make code changes to ensure they are compatible with these newer Engine versions. See our guide on migrating to Engine 5 for more details about changes in those Engine versions that may require updates in your custom code. 

Developers

To ensure your XML output type is up to date, upgrade the @wpmedia/feeds-xml-output dependency in your package.json to its stable version in your OBF bundle by running npm install @wpmedia/feeds-xml-output@stable. You should redeploy your bundle to get the latest outbound feeds blocks with this fix. 

This release fixes a bug where sub-sections of the Sitemap Section block had priority and changefreq values reversed. Now, those values are consistent across parent and child sub-sections.

Outbound feed users

None

Release schedule by region:

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Release schedule by region:

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Release schedule by region:

An issue was discovered with the new “Sitemap Section” block. If you don’t set a value in Feed Path the URL will be invalid. This is now fixed and an empty Feed Path produces a valid URL. If you have already added the block, you need to redeploy the bundle to get the fix. If you have not added the block no action is required. The Sitemap Section block is now available that produces a sitemap from your site service hierarchy with links to your website’s sections. This is in addition to the Sitemap Section Front Index block that produces a sitemap index of your sections. To start using this new block, you’ll need to add the new block to your repo and deploy a new bundle.

"@wpmedia/sitemap-section-feature-block",

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Release schedule by region:

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Release schedule by region:

“@wpmedia/feeds-source-single-content-block”

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Release schedule by region:

Reminder

If you have not added the resolver create, edit and delete privileges to your developers in your OBF environments, you must enable these privileges immediately in the outboundfeeds environment or you won’t be able to add or change any resolvers. For more information on privileges in Outbound Feeds, see Introduction to PageBuilder Privileges.Introduction to PageBuilder Privileges

Update to the latest 3.x engine version when deploying your bundles. And don’t forget to update your local OBF environments .env FUSION_RELEASE and update your dependencies with npm install @arc-fusion/cli@latest to keep your dev environment up to date.

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Mobile and Amazon feeds will also be custom-built and maintained by you.

Sandbox: Wednesday, December 1, 2021

Production: Wednesday, December 8, 2021

Bug Fixes

Other Improvements

The PageBuilder Editor 3.8 Release includes resolver enhancements. With this release, you can specify a default outputType for each resolver. Once you remove the required outputType parameter and add a default outputType to a resolver, requests will no longer require an outputType parameter. Currently this is only available for templates, so requests for pages like robots.txt and ads.txt still require an outputType parameter.

Changes to Resolver Privileges

With the PageBuilder Editor 3.7 Release, Add and Edit Resolvers and Delete Resolvers privileges were released. With this release, these privileges are now implemented and a user will need them in order to create, edit, and delete resolvers. Previously, users with the Developer Tools privilege had access to all resolver actions. Users with the Developer Tools privilege now only have read-only access a resolver’s configurations.

(ACTION REQUIRED) To make changes to your resolver functionality, you must enable these privileges immediately in the outboundfeeds environment. For more information on privileges in Outbound Feeds, see Introduction to PageBuilder Privileges.Introduction to PageBuilder Privileges

Reminder

Update to the latest 3.x engine version when deploying your bundles. And don’t forget to update your local OBF environments .env FUSION_RELEASE and update your dependencies with npm install @arc-fusion/cli@latest to keep your dev environment up to date.

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Sandbox: Wednesday, November 10, 2021

Production: Thursday, November 11, 2021

Bug Fix

Fixed 414 responses from the content sources used in the Sitemap Index by day feed.

Important Dates Ahead & Reminders

The deactivation dates are fast approaching and to help you migrate to Outbound Feeds.

November 30, 2021

By November 30, 2021, all remaining outbound feed configurations will be removed from our legacy systems if it’s now supported with the Outbound Feeds 1.X Product.

Reminder

Update to the latest 3.x engine version when deploying your bundles. And don’t forget to update your local OBF environments .env FUSION_RELEASE and update the @arc-fusion/cli package to get quicker start-up times.

Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Sandbox: Wednesday, October 13, 2021,Updated - Thursday, October 21, 2021

Production: Wednesday, October 27, 2021

Performance Improvements

Once you deploy this release, test all of your OBF resolvers in use with custom queries. ***This change MAY impact your existing resolvers.

Bug Fixes

1. Fixed a bug with the collections content source that prevented searching by alias.

2. (NEW) Fixed a bug with the content source if there is no data returned by Content-API.

Important Dates Ahead & Reminders

The deactivation dates are fast approaching and to help you migrate to Outbound Feeds.

November 30, 2021

Reminder

Update to the latest 3.x engine version when deploying your bundles. Don’t forget to update your local OBF environments .env FUSION_RELEASE and update the @arc-fusion/cli package to get quicker start-up times.

NEW. Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

NEW. A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of its normal support process. The turnaround time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. If your latest bundle isn’t running the most recent engine version you can deploy the same bundle and pick the latest engine version. If it’s already running the latest version, click the ellipsis on the live bundle and select duplicate to redeploy the bundle with the latest version of OBF. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Sandbox: Thursday, September 23, 2021, Updated on Monday, September 27, 2021

Production: Wednesday, September 29, 2021

A new Alexa block is now available that is designed to allow you to create a flash briefing skill to provide Alexa customers with news headlines and other short content. Once Alexa users update their preferences, they will be able to say “Alexa, give me my flash briefing” to hear your latest news stories.

The Alexa flash briefing requirements are unique so some sort of curation should be considered. For example using a collection or filtering articles by a specific section or tag. You could also filter for articles that contain an audio element. If an article includes an mp3 audio file it will be played by Alexa, otherwise Alexa will use text to speech on the article body. Care should be taken to keep the articles length within the 4,500 character limit and avoid elements that might not translate to speech well like Twitter and Facebook embeds, raw html blocks, and html lists.

The standard Alexa feed is a platform level Arc feed block designed to integrate with the Amazon Alexa Flash Briefing Skill. To start using the Alexa block, you’ll need to add this block to your repo and deploy a new bundle.

“@wpmedia/rss-alexa-feature-block”

Easy to follow detailed instructions for this new feed are available in the Alexa Feed Configuration Guide.

Minor Enhancements and Bug Fixes

1. Added support for child sections to the Sitemap Section Front Index block. The Sitemap Section Front Index block now includes child sections in its output.

2. Added capability to remove (enter a blank) in the RSS credits and description custom fields to remove them from a feed.

3. Updated custom field names and groupings. We have changed some Custom Field names and groupings to be more consistent and better reflect their functionality.

4. (NEW) Fixed the incorrect raw_html element format in the rss-fbia-feature-block.

5. In Engine 3.1 we’ve included a fix for resolvers to support default parameter values. To take advantage of these improvements in OBF be sure to use the latest 3.x engine version when deploying your bundles. And don’t forget to update your local OBF environments .env FUSION_RELEASE and update the @arc-fusion/cli package to get quicker start-up times.

Important Dates Ahead

The deactivation dates are fast approaching and to help you migrate to Outbound Feeds, we’ve documented. Here the steps you’ll want to complete to ensure your services continue to run smoothly. Contact Arc XP Customer Support if you need assistance with your OBF migrations.

November 30, 2021

By November 30, 2021, all remaining outbound feed configurations will be removed from our legacy systems if it’s now supported with the Outbound Feeds 1.X Product.

NEW. Q: How do I submit a request to redirect my legacy Partner Feeds to Outbound Feeds (OBF)?

NEW. A: Clients may request redirects from the legacy feeds path to the OBF product paths by opening an ACS ticket. ACS will implement the redirects as part of their normal support process. Turn around time for a redirect request is five business days.

The following redirect lines are supported. These paths correlate to the STANDARD arcio/OBF feeds that are provided out-of-the-box. In addition to these clients may ask for a single top level path in ArcIO to be redirected to the SAME top level path in OBF. Rules may be implemented all at once or line by line as needed by the client.

In the case where clients are requesting a custom top level path to be redirected, we will use this template with customer provided path and outputType values:

Additional information on redirects from the legacy outbound feeds platform to OBF is available Here.

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. Download the bundle, rename the zip file, and upload it. When you name the new bundle be sure to only include letters, numbers and dashes. The Deploying New Features guide includes step-by-step instructions on how to deploy the new features in each release.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News and Most Read feeds are not included in the initial offering. If you already have these feeds set up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom-built and maintained by you.

Sandbox: Wednesday, June 16, 2021

Production: Wednesday, June 23, 2021

We’ve added more out of the box feed templates. The ANS feed type is available now and provides a standard ANS Block and a JSON output type to provide a JSON feed format.

We’ve also enhanced the video encoding configuration options to add the ability to specify which video encoding to display for inline videos in all RSS based feeds.

To start using these new blocks, you’ll need to add the blocks below to your repo and deploy a new bundle.

"@wpmedia/ans-feature-block",
"@wpmedia/json-output-block",

Your updated blocks.json in your outboundfeeds repo should look similar to this.

"blocks": [
    "@wpmedia/feeds-source-content-api-by-day-block",
    "@wpmedia/feeds-source-content-api-by-day2-block",
    "@wpmedia/feeds-source-content-api-by-day3-block",
    "@wpmedia/sitemap-index-by-day-feature-block",
    "@wpmedia/feeds-source-content-api-block",
    "@wpmedia/feeds-source-collections-block",
    "@wpmedia/site-hierarchy-content-block",
    "@wpmedia/mrss-feature-block",
    "@wpmedia/rss-feature-block",
    "@wpmedia/rss-fbia-feature-block",
    "@wpmedia/rss-flipboard-feature-block",
    "@wpmedia/rss-google-news-feature-block",
    "@wpmedia/rss-msn-feature-block",
    "@wpmedia/sitemap-news-feature-block",
    "@wpmedia/sitemap-video-feature-block",
    "@wpmedia/sitemap-feature-block",
    "@wpmedia/sitemap-index-feature-block",
    "@wpmedia/sitemap-section-index-feature-block",
    "@wpmedia/text-output-block",
    "@wpmedia/textfile-block",
    "@wpmedia/ans-feature-block",
    "@wpmedia/json-output-block"
  ],

Bug Fixes

1. Fixed OBF Content API Block to include taxonomy.section._website in Section Queries.

2. Fixed date formatting of number of days in sitemap feed.

Important Dates Ahead

September 15, 2021

November 30, 2021

Q: How do I start using the latest version of Outbound Feeds?

A: You need to redeploy your current bundle. Download the bundle, rename the zip file, and upload it. When you name the new bundle be sure to only include letters, numbers and dashes.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News, and Most Read feeds are not included in the initial offering. If you already have these feeds set-up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom built and maintained by you.

Welcome to Outbound Feeds.

We have a lot of new and exciting features to share with you. We’ve made many enhancements and added many new features. Here are the highlights:

Bug Fix

Update on Deactivation of Legacy Feeds

As of 1 March 2021, all clients were provisioned with Outboundfeeds Sandbox and Production environment in PB Fusion.

As of 15 March 2021, all clients have outbound feeds reports available. This report shows an inventory of the outbound feeds currently producing traffic in our legacy systems. Since this report is based on snapshot in time, it’s possible that not all feeds are listed. We recommend that you validate the information in the report against your internal systems to ensure all feeds are accounted for.

Important Dates Ahead

12 April 2021

After 12 April 2021, you will no longer be able to open ACS tickets to request changes to existing feeds. All previously submitted ACS feed changes currently in backlog as non-critical requests will be considered deferred for future roadmap consideration. Using custom feed blocks, you can develop new features in Outbound Feeds 1.x now.

15 September 2021

By 15 September 2021, these standard feeds will be deactivated in our legacy systems: Sitemap (Standard, Index, News, Video), RSS (Google News, Facebook Instant Articles, MSN, Flipboard, Standard RSS) and MRSS.

30 November 2021

By 30 November 2021, all remaining outbound feed configurations will be removed from our legacy systems if it’s now supported with the Outbound Feeds 1.x product.

Q. How do I get the latest Outbound Feeds blocks and start using these new features?

A. You need to update your blocks.json and generate and deploy a new bundle.

Q: Which feed types are not included in the initial Arc Outbound Feeds offering?

A: Apple News, Most Read, and Arc Native Spec (ANS) feeds are not included in the initial offering. If you already have these feeds set-up, they will continue to run on the legacy architecture. All Inbound Feeds will also persist on the legacy architecture. Additionally, mobile feeds and Amazon feeds will always be custom built and maintained by you.