Gaetano Giunta
Gaetano Giunta
Done, will be in upcoming release 6.1
That's correct. I think it is even documented: in a migration step either all fields must be multilingual, or none. Which means that your usecase of creating/updating in a single...
Note: I am sticking to ez5 nomenclature for clarity, so no 'attribute' anywhere in this post please, even if the yaml says `attributes` :-) There are Content, Field, ContentType, FieldType....
> Well, I think what really prevents this enhancement from working out is that the language code and the sub fields live in the same namespace. So it can be...
Let me sit on this for a couple of days... (atm I am busy with work, as well as the port of mig bundle to ezplatform 3...)
Side note: it might be that this PR works for the 90% scenario, ie. eZP connected to a single DB, but not for the case where one eZP install uses...
Fixed the problem with the case where multiple doctrine db connections are declared. Ready for review.
Anyone up for review ?
@pkamps it is true that this is a problem as well for some long-running scripts, however it is a hard problem to fix for the general case, as it is...