Intégration de Flexicontent avec d'autres extensions

Bonjour,
...désolé de revenir sur le sujet.
J'ai contacté ACL Manager, le developpeur m'a dit qu'il a déjà signalé le problème au team de Flexicontent sur comment procéder pour résoudre le souci de la compatibilité .
Il serait bien de comprendre à quel niveau ça coince car j'ai deux sons de cloches différents quant à la modification du code: ACL Manager dit que c'est Flexicontent qui doit modifier le code pour rendre le composant compatible et vice versa vous dites que c'est à ACL Manager de faire l'effort pour modifier le code... so what? :roll:

je transmet a georgios on va voir ce que l'on peut faire

... c'est sympa, merci

Hello,

having compatibility with ACL manager (and any similar extension not willing to do little to support FLEXIcontent) and loosing compatibility with hundrends or thousands other extensions is not a viable solution

In short, changing FLEXIcontent to be "compatible" with ACL manager,

will not happen

-- not only because of being asked to do 10x or 100x work on our part instead of 1x work on the other part

-- but also because we will win too little and loose too much

Hello,
... I totally understand, so apparently it's rather on ACL Manager side that it gets stuck ...and if I choose to use FLEXIcontent I'll have to give up ACL Manager … :roll:

...bon je reporte la réponse du développeur d'ACL Manager qui laisse tout de même entendre que c'est FLEXIcontent qui touche aux fichiers core de Joomla :roll:

Hello,

I understand it is difficult to decide who to believe.

But as I am saying in the linked forum post Flexicontent is manipulating the Joomla data in the assets table of database by replacing "com_content.category.81" with "com_flexicontent.category.81". This is simply not correct, the asset is related to an category that belongs to "com_content", not "com_flexicontent" Flexicontent should not touch the naming of assets in the table that don't belong to their extension. They are indeed using the category as base for their extension, but they should not manipulate the data of the Joomla core extensions. This will result in conflicts with my, but possible other 3rd party extensions as well.