-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Florent Guillaume wrote: |> | Use: |> | |> | [default] |> | content_type = text/foobar |> |> No, this doesn't work either :( | | | Well it should, there are unit tests in CMFCore that explicitely test | this kind of .metadata file. | No, I had a look and there's a strange test with a FSPT which explicitly sets the REQUEST content-type. There's no test which checks this from a .metadata file. There is a test which checks the title in a .properties file. I extended these tests (test_DirectoryView.py) and indeed setting content_type as a property does pass the test. I also added a .metadata test and it actually does pass this test too, although .metadata and .properties files do appear mutually exclusive. I've attached the patch of these tests if you want to apply it. So, now I can't explain why my real-world .metadata content_type is being ignored! Cheers, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFByaZvCfroLk4EZpkRAkibAKCOHPMge3kaoT9nqDJMiDnc75g2+wCfTjK1 aFEDZCvkqQ8oiCi+oFrD7sc= =wgyp -----END PGP SIGNATURE-----