Skip to main content
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
added 25 characters in body
Source Link
Chris Auer
  • 13.2k
  • 1
  • 30
  • 87

I have a page that is completely component based. All images, html, etc are individual components with datasources in a grid system. The datasources are in a folder under the page called pagedata or in a site level folder called sitedata.

What I want to accomplish is to have the components follow the same publishing date restrictions as the parent page. Right now if I want an image to switch out on June 1, I have to version and add publishing restrictions on the image datasource item and add publishing restrictions to it. Or I can make a new image item (separate from the current oneimage datasource item). Then the presentation details of the parentpage item, in the June 1 version, will switch out the image itemdatasource on June 1st.

If I had a page with 10 images and 3 html components, it would be difficult to create 13 new items and then update the datasources for all the components. Or go to all 13 datasource items and set publishing restrictions on them all.

Anyone have a simpler pipeline that allows adding publishing restrictions to a component based page? I have not researched how SXA does it yet.

I have a page that is completely component based. All images, html, etc are individual components with datasources in a grid system. The datasources are in a folder under the page called pagedata or in a site level folder called sitedata.

What I want to accomplish is to have the components follow the same publishing date restrictions as the parent page. Right now if I want an image to switch out on June 1, I have to version and add publishing restrictions on the image datasource item. Or I can make a new image item (separate from the current one). Then the presentation details of the parent item, in the June 1 version, will switch out the image item on June 1st.

If I had a page with 10 images and 3 html components, it would be difficult to create 13 new items and then update the datasources for all the components. Or go to all 13 datasource items and set publishing restrictions on them all.

Anyone have a simpler pipeline that allows adding publishing restrictions to a component based page? I have not researched how SXA does it yet.

I have a page that is completely component based. All images, html, etc are individual components with datasources in a grid system. The datasources are in a folder under the page called pagedata or in a site level folder called sitedata.

What I want to accomplish is to have the components follow the same publishing date restrictions as the parent page. Right now if I want an image to switch out on June 1, I have to version the image datasource item and add publishing restrictions to it. Or I can make a new image item (separate from the current image datasource item). Then the presentation details of the page item, in the June 1 version, will switch out the image datasource on June 1st.

If I had a page with 10 images and 3 html components, it would be difficult to create 13 new items and then update the datasources for all the components. Or go to all 13 datasource items and set publishing restrictions on them all.

Anyone have a simpler pipeline that allows adding publishing restrictions to a component based page? I have not researched how SXA does it yet.

Source Link
Chris Auer
  • 13.2k
  • 1
  • 30
  • 87

Publishing restrictions for components in page

I have a page that is completely component based. All images, html, etc are individual components with datasources in a grid system. The datasources are in a folder under the page called pagedata or in a site level folder called sitedata.

What I want to accomplish is to have the components follow the same publishing date restrictions as the parent page. Right now if I want an image to switch out on June 1, I have to version and add publishing restrictions on the image datasource item. Or I can make a new image item (separate from the current one). Then the presentation details of the parent item, in the June 1 version, will switch out the image item on June 1st.

If I had a page with 10 images and 3 html components, it would be difficult to create 13 new items and then update the datasources for all the components. Or go to all 13 datasource items and set publishing restrictions on them all.

Anyone have a simpler pipeline that allows adding publishing restrictions to a component based page? I have not researched how SXA does it yet.