Why can some entries be enabled on one site but not another?
In a multi-site CMS there are a few different reasons why an entry might be available to enable on one site but not another. This is generally intentional behaviour rather than an error.
The section is not configured for that site
Each section in the CMS is configured to operate on one or more specific sites. If a section has not been set up for a particular site, entries within it will simply not be available there- the site will not appear as an option in the site selector when editing those entries. This is a configuration decision made at the point the site is built and reflects which content types are intended to appear on each site. If you believe a section should be available on an additional site, contact your site administrator.
The section uses per-site propagation
Some sections are configured so that entries are only propagated to specific sites rather than all sites automatically. This is typically used for sections where content is intentionally different across sites- for example, a blog or business directory that is tailored to each site's audience. An entry created on one site in these sections will not automatically exist on another site unless it is explicitly enabled for that site within the entry itself.
The entry has been manually disabled on a specific site
Even when an entry exists across all sites, it can be enabled or disabled independently on each one. An entry that is live on one site may have been deliberately disabled on another- for example, if a piece of content is relevant to one audience but not another. To check this, open the entry, switch between sites using the site selector, and review the enabled status on each.
Business Login: package tier restrictions
If you are managing content through the Business Login portal, the sites available to you are also controlled by your business's package tier. If your package does not include access to a particular site, you will not be able to enable entries on that site regardless of the section configuration. Contact your site administrator if you believe your package needs to be updated.
The section is not configured for that site
Each section in the CMS is configured to operate on one or more specific sites. If a section has not been set up for a particular site, entries within it will simply not be available there- the site will not appear as an option in the site selector when editing those entries. This is a configuration decision made at the point the site is built and reflects which content types are intended to appear on each site. If you believe a section should be available on an additional site, contact your site administrator.
The section uses per-site propagation
Some sections are configured so that entries are only propagated to specific sites rather than all sites automatically. This is typically used for sections where content is intentionally different across sites- for example, a blog or business directory that is tailored to each site's audience. An entry created on one site in these sections will not automatically exist on another site unless it is explicitly enabled for that site within the entry itself.
The entry has been manually disabled on a specific site
Even when an entry exists across all sites, it can be enabled or disabled independently on each one. An entry that is live on one site may have been deliberately disabled on another- for example, if a piece of content is relevant to one audience but not another. To check this, open the entry, switch between sites using the site selector, and review the enabled status on each.
Business Login: package tier restrictions
If you are managing content through the Business Login portal, the sites available to you are also controlled by your business's package tier. If your package does not include access to a particular site, you will not be able to enable entries on that site regardless of the section configuration. Contact your site administrator if you believe your package needs to be updated.