TYPO3 Core

I referenced this issue here:

http://forge.typo3.org/issues/12385

I could not reproduce the issue with the current trunk version of TYPO3 and linkvalidator. But it's still not good that they should use variable names shared by other tasks. I'll add a not to the issue opened by Ernesto.

Yes, then we should change the variable name in linkvalidator.

But @ Francois: The basic problem still stays. We cannot be sure that noone will in any extension call his field the way we already have a field in the Core. This general problem still needs to be addressed somehow.

solved in http://forge.typo3.org/issues/12385

Committed revision 42413. in linkvalidator trunk

@Michael: thanks

@Christopher: yes, I know. As I said in the related Forge issue, we are aware of this potential for problems, but we couldn't find a good solution. The least we could do was to add a warning in the manual. If you think about it, there's the same problem in the Core, if you use "user"-type fields in TCA. TCEforms will pass you a name for the field, but you are perfectly free to ignore it. We would have to change the whole system so that the generation of the form field itself is handled by some library, so that users wouldn't even have the choice of name.

maybe it's possible to use some ExtJS magic ?
click on save and extjs send only "visible" inputFields or delete all hidden fields and send the form ?
it's only an idea, i don't know if this is possible with extjs

Sven, can you confirm that this specific issue is fixed for you? It certainly is for me.

The more general discussion is interesting, but should not take place here. Rather in the typo3.projects.v4 mailing list.

Hey Francois,

yes, this issue is fixed for me, so this entry can be marked as solved.

Issue fixed thanks to the changes in the linkvalidator sysext.