nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Custom content types and Cloud Sync

billerby

As I understand it, Alfresco Cloud does not support custom content types or custom aspects yet. If we enable Alfresco Cloud Sync for a folder in a 4.1 installation and this folder contains nodes with custom content types or custom aspects applied, how does this affect the sync process? Is the content synched anyway? Or do we have to ensure no custom stuff is applied to the content we are marking for synchronization?

Regards
/Erik

Find more posts tagged with

Comments

janv

Yes, custom content types should still get synced. When pushed to the cloud, any custom metadata should be ignored so it will appear as 'vanilla' content in the cloud (sync target). If updated in the cloud then it should get sync'ed back with any custom metadata preserved on-premise (sync source). If you see any issues, please let us know via Alfresco (Enterprise) Support, many thanks.

Regards,
Jan

billerby

Thanks Jan,

I will contact support since I only is successful in syncing custom aspects and not types.

/Erik

janv

OK, many thanks for the feedback. It does look like a bug that slipped through with respect to custom (content) types. I'm working on an initial fix as we speak.

Regards,
Jan

ps. ultimately, if and when we introduce custom metadata to the cloud platform then you may also have the option to sync more (at least to those networks/tenants that support it).