NamelessCoder
commented
11 years ago Hi Florian,
I can confirm that this problem exists. It is caused by one of the override classes - the good news is that I managed to get a fix rushed into the TYPO3 core which should make it possible to finally drop the override classes completely, thus solving the issue (or at least moving it back into the TYPO3 core; it's caused by some refactoring so I assume they have taken care of that in the core class). The bad news is that the fix will not be available until the next bugfix release of TYPO3 core which in your case will be 6.1.2 which I assume should be out in a few weeks or so.
Now, there's a fairly good chance that you will be able to fix this on your site by (temporarily) commenting out lines 76 through 83 in ext_localconf.php of Flux. This may have a negative impact on some aspects of Flux (and by proxy, fluidpages and fluidcontent too) but you won't necessarily have problems in doing so. It's worth a try.
If you experience problems with that solution you can in addition to that fix use the git master of the TYPO3 core (and checkout the 6.1 branch so you don't get 6.2-dev changes); this also contains the fix now.
I apologise for the convoluted solution but unfortunately it has proven more problematic than expected, to override the core class in question. It was not scheduled for any major changes but even so it would appear some refactoring has made my version incompatible - and since it's no longer possible/reasonable to have a version that's compatible with 6.2 and lower 6.x versions it's time to drop the overrides and instead depend on a yet-to-be-released TYPO3 core to fix the issue. But, all things being equal that involves a bit of waiting or some manual fixes.
I will take the liberty of closing this issue; the explanation is here for history and come the next bugfix releases for TYPO3 this all goes away by itself :) but as always, feel free to reopen the issue or add comments, I'm still watching.
Cheers, Claus
Problem
Editing of content type media not possible (insertion throws error).
Test case
When inserting an element of content type "media", on my local installation following error is thrown:
Fatal error: Call to undefined method TYPO3\CMS\Backend\Form\ElementConditionMatcher::setRecord() in [...]/typo3_src-6.1.1/typo3/sysext/backend/Classes/Form/FormEngine.php on line 5954
The element is inserted, but the form seems to load not properly. Editing is not possible. TYPO3 6.1.1, flux 6.0.0, fluidcontent 3.0.0, fluidpages 2.0.1, latest git version of vhs.
After experiencing this failure, I tried insertion on official demo installation (Bootstrap with flux - http://bootstrap.typo3cms.demo.typo3.org/typo3) -> blank page in backend by insertion/editing attempt
I tried insertion on official demo installation (Introduction Package without flux - http://demo.typo3.org/introduction/typo3) -> everything works fine.