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
I've been experimenting a weird behaviour likely related to this and #6
Basically, fields with the translate: false option stop displaying values in the translated page. This is an issue in the website as well as in the panel, where the fields with the translate: false options appear empty. Since these fields are also required, this basically blocks editors from saving pages in the translated versions...
When I set to debug: false;, the problem dissappear. Also, when I set 'bnomei.boost.cache' => false, the problem also stops. So I guess it must be from the cache?
Of course, not using the translate: false option could solve the issue, as well as making a page model that would overwrite the field values that should not be translated (since they would then be hard-coded within the content files). So far I set off the boost cache, but I'm unsure this should be the best long-term solution as I do see very pleasant performance gains by using the (sqlite) cache!
I've seen a wontfix tag on #6 and was curious about the issue, is there a lot of complexity into making this work with translate: false? I guess it's another layer of complexity on top?
Originally posted by @francois-gm in #11 (comment)
The text was updated successfully, but these errors were encountered: