[TYPO3-dev] Detecting XCLASS conflicts

[Tapio Markula]

Dimitri Tarassenko wrote:
> Urghhhh....
> 
> Spent about 2 hours today troubleshooting a very interesting glitch
> that turned out to be an XCLASSing conflict of two extensions, so two
> sites with exactly the same set of extensions were behaving
> differently based on which one of the two was loaded first. Yikes.

Well known problem. In this issue it was suprice for me that the XLASS 
for *last* loaded extension take precedence - I thought that the order 
is opposite.

I don' know any way to detectect conflicts.

I have just tried to avoid conflicts so much as possible.
My extension tm_contentaccess has detections for some other plugins and 
it has some extra (conditional) code, which makes for example
tm_contentaccess compatible with erotea2cal and smile_categorization.
In addition my plugin has build in implementation of several plugins.

Sometimes it is not very big task to make extension to work together
but you must do changes yourself. IMO people should try more avoid 
conflicts - at least conflicts between *own* extensions.

XCLASS-implementations should build so that they work at least in all 
own plugins if that is just possible. It was once extremely irritating 
to find that author of two plugins didn't care at all conflicts between 
his own extension. That author fixed however later this issuea and made 
XCLASSing compatible at least so that loading with certain order both 
extensions worked.

In general we should just hope that people, who use XCLASSes would
take better account possible conflicts.