I noticed that a freelancer workspace plan has a limit of 50 CMS fields per collection. If I were to transfer the site or host it myself with a CMS plan Hosting, would the amount of CMS fields decrease? I am wondering this because a CMS hosting plan has a limit of 30 fields per collection, and not 50 like the freelance workspace.
Hey Grant,
I think you may have misread something- I’ve not heard of any 50 in relation to CMS fields. There’s 30 for CMS hosting plans, and 60 for Business/Enterprise hosting plans.
The Workspace plan you’re using only affects unhosted sites. When a site is hosted, the site’s plan governs what that site can do. The workspace has no relevance.
So usually you’d build the site using whatever workspace plan you need, and then you’d setup hosting based on what you built. In the case of collection fields, if you built the site on a freelancer plan using 60 fields/collection, then yes you’d have to host it using the business plan to support that.
Our team found the site / workspace plans difficult to decode as well, so we have a guide and a lot of notes that we use here;
1 Like
I noticed the same thing and I don’t know how to work around it. In a Freelancer workspace website with a CMS plan has a limit of 60 items, and in a free workspace website with a CMS plan has only a limit of 30 items. It probably was done to allow freelancer web developers to develop websites that will have Business plan when transferred to client.
That doesn’t sound right.
In a Freelancer workspace, when you’re building a site ( unhosted ), you’ll have access to the full range of capabilities, e.g. up to 60 fields per CMS collection, etc. However once you add a site plan to that site, e.g. “CMS plan”, that now dictates what the site is capable of.
If an unhosted site has a collection with 31 fields, you likely wouldn’t be able to purchase a CMS plan, you’d need Business instead. and in a hosted CMS-plan, you wouldn’t be able to add a 31st field, even if you’re in a Freelancer workspace.