Issues with Content Availability added in January 2025 update

SMiller7
Giga Expert

We just installed the January 2025 update. Within content publishing it has now added a new Content Availability section within the Publish portion. It requires a start date for accessing as well as an audience. This has created a couple of big issues.

1. Our 800+ previous news articles no longer were visible to users. They could see it on All News, but when they click to view the individual article, it gave an error message that the article wasn't available.

2. After you add the availability, the publish plans are pushed way down to the bottom and very unreadable. This has been the experience in both Edge and Chrome.

 

Has anyone else experienced this? What is even the purpose of content availability as it seems redundant to the publish plans?

1 ACCEPTED SOLUTION

SMiller7
Giga Expert

We found out that this was an issue with the January release and they fixed it as part of the May release.

 

Most Probable Cause:
It looks like you were experiencing PRB1862224 which impacted your version of Content Publishing on upgrade.
On upgrade, an internal fix script was supposed to migrate the 'News Start/End Dates" to the the Scheduled Content's "Avaliability Start/End Date", however, there was an issue with the script and not all News Contents were updated correctly

Solution Proposed:
This was fixed in the May release of Content Experiences and Content Publishing plugins. To resolve this issue, please update the plugins below to most recent versions.

https://ecommunity.service-now.com/now/app-manager/home/app/id/bde72a4753710300d901a7e6a11c0838/v/32...

 

https://ecommunity.service-now.com/now/app-manager/home/app/id/b26210490b7203008cd6e7ae37673a6a/v/35...



You can read more about this issue in this kb article:

KB1967696 - Issue with missing "Content availability" for News on upgrade to Jan version Content Pub... - Perma Link [Internal, Customer]

View solution in original post

1 REPLY 1

SMiller7
Giga Expert

We found out that this was an issue with the January release and they fixed it as part of the May release.

 

Most Probable Cause:
It looks like you were experiencing PRB1862224 which impacted your version of Content Publishing on upgrade.
On upgrade, an internal fix script was supposed to migrate the 'News Start/End Dates" to the the Scheduled Content's "Avaliability Start/End Date", however, there was an issue with the script and not all News Contents were updated correctly

Solution Proposed:
This was fixed in the May release of Content Experiences and Content Publishing plugins. To resolve this issue, please update the plugins below to most recent versions.

https://ecommunity.service-now.com/now/app-manager/home/app/id/bde72a4753710300d901a7e6a11c0838/v/32...

 

https://ecommunity.service-now.com/now/app-manager/home/app/id/b26210490b7203008cd6e7ae37673a6a/v/35...



You can read more about this issue in this kb article:

KB1967696 - Issue with missing "Content availability" for News on upgrade to Jan version Content Pub... - Perma Link [Internal, Customer]