Conflict with Docman

Hi Georges,
On J4, last version of Flexicontent, I have also Docman.
I have contacted the Docman team and they have found an issue with Flexicontent code, I paste their answer here :
**************************************
Hello Xavier,

Thanks for the FTP access. I've performed a search inside your installed components and found this =>

drops.arunasmazeika.com/Screen-Shot-2023-11-27-12-16-48.42.png

The Flexicontent component is responsible for the issue you are experiencing ... as I've said, they are defining their own JEventDispatcher class which is a big NO NO NO ... you don't do this unless you have absolute control of the environment where the code is running. I understand why they've done it but you do not define a Framework class like this, knowing that there might be code relying on checks against it.

I encourage you to contact them and ask them if they are willing to fix it ... this in no case a problem with DOCman itself.

You can test that all works perfectly if you disable all of the flexicontent extensions (plugins, etc.) in the extensions manager.
**************************************
This cause an issue in backend when I'm trying to change information in a Docman document.

Can you help me or tell me if this code can be changed in Flexicontent ?

Thank you Georges
Xavier

hello sorry to understand it but i am disapointed by reply.. flexicontent works with many many component that the only one that say this ... without any explain about the error or the problem difficult to help you
we works on new code working with joomla5 with compatibility plugin but need time ..
maybe we can check if we can change this

Hi,
Sure, Flexicontent works with many extensions, but I encounter an issue with Docman.

On changing a category or access rights on an existing document in Docman (in backend), I have an issue shown :

0 Call to undefined method JEventDispatcher::trigger()

I ask then to the Docman team to check what is wrong and they found this issue and told me this is on the Flexicontent code and show me the file administrator/components/com_flexicontent/defineconstants.php where at line 105 - 115 there is the JEventDispatcher possible issue.

My question for Georges is then if there is a possibility to have a workaround to avoid this issue.

For the record : Joomla 4 last version, Flexicontent last version, PHP 8.0

Best,
Xavier

Hello
Without edocman impossible to débug this

Docman, not Edocman.

Georges ?

Sorry docman
About georgios as i know hé IS fully if works
We need this extension to understand or ask to they an ex of solution

Georges,
I give you the answer from the developper to help you understand the issue :

****************************
DOCman runs on Joomla 3 and 4, compatibility for Joomla 5 is already finished and about to be released. This means that our code sometimes makes version checks, and sometimes it looks for precise classes to decide and act upon ... the problem introduced by Flexicontent is that since they say ... well JEventDispatcher is no longer available since Joomla 4, let's define it again for our convenience ... the BIG problem is that they are changing the API by making it implement a different interface. JEventDispatcher is now effectively an alias class from the current Joomla\Event\Dispatcher class because of the code I've pointed out. This is very bad practice in an environment where you have code running from different vendors and also providing compatibility for different Joomla versions. If there's code looking for JEventDispatcher and ends up finding it ... the code assumes that JEventDispatcher should in fact behave as JEventDispatcher ... instead JEventDispatcher is now behaving as Joomla\Event\Dispatcher because of Flexicontent.

I hope this helps clarifying things.
****************************

So, so far, the JEventDispatcher is not existing in J4 or J5 and still declared in Flexicontent, this causing this issue ?

Sorry Micker, but this is a coding issue from Flexicontent using a class not used anymore if I understand well and maybe Georges will understand more this issue.

Xavier

Jrequest update IS planned in next version but not sure that the solution for this issue
Need more Time to investigate
Regards