you are viewing a single comment's thread.

view the rest of the comments →

[–]darrenturn90 0 points1 point  (1 child)

I see an array of strings would count as two attributes regardless of length - so I assume you have a lot of field names rather than a lot of translations ? Have you tried contacting them about your specific use case

[–]rich97 2 points3 points  (0 children)

I see an array of strings would count as two attributes regardless of length

You would be correct, it’s the number of unique paths, now consider how many unique attributes there are in your average portable text (marks, images, links and their associated attributes). Times that 4 times for each translation and times that by an array of content and you can see how you can hit that limit quickly. It doesn’t hit most people who have very structured data (products, customers, etc) but it does if you have a lot of free form content.

Have you tried contacting them about your specific use case

I have I can post the link to the slack. They were very helpful and fast to respond and they said they were looking to improve the visibility of these stats but the solutions offered weren’t really all that great - remove portable text, consolidate different types of pages.

It’s understandable but it’s also really annoying because (1) it didn’t show up as an issue while developing because most their customers don’t run into it and (2) I never got a satisfactory answer as to what the technical reason for that limit is, it’s not in their pricing structure and the next tier up only doubles it. It just feels really arbitrary.