You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
We have 40+ sites in cascade. Would I be able to count all the websites then list them in the social media directory. Then edit them from there?
Rather than just manually adding all the websites into the directory could I loop through all the websites then post them to the directory page then add social media they belong to?
Great, thank you for confirming @gjs1985. I've added issues to this issue so we can better handle questions rather than comments on specific commits. Can you confirm if you see a green New Issue button at the top of the page when viewing this issue in the browser?
Assuming you are referring to the Social Media Directory example site, what you can do is the following:
Create a Configuration Set and Content Type in a shared/common Site
Create a "hidden" page in each of your Sites that uses this new Content Type
Create a Content Type Index Block in this shared/common Site pointing to the new Content Type
Adjust the provided Format to properly handle content coming from an Index Block as opposed to coming directly from a block or page
This will work because a Content Type Index Block will index all pages across the system that use the selected Content Type, regardless of the Site they are in.
Please let me know if you have any questions.
Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have 40+ sites in cascade. Would I be able to count all the websites then list them in the social media directory. Then edit them from there?
Rather than just manually adding all the websites into the directory could I loop through all the websites then post them to the directory page then add social media they belong to?
Thanks,
@gjs1985
The text was updated successfully, but these errors were encountered: