Quote:
In fact, we notice that in the configuration you sent the <use_enriched_content_type> is N.
So, can we assume that, by moving from 5.1.1 to 5.1.2 (which is straightforward) and setting <use_enriched_content_type> to Y, you have fixed your issue, as far as your operativity is concerned?
Locally yes. I'm trying to avoid server upgrades because our deployment scripts are ... less than fully understood.
Quote:
According to the logs included in your testcase, we see that the testcase still involves an OSX client library 2.0.1 trying to connect to a Server 5.1.2, which is not supported.
Is this the extension to 5.1.2 that you would like to be applied?
That's the behaviour I would like to test, yes, thanks.