Purus copied a couple of files from the standard events plugin. These files were changed in one of the updates. 

So the only thing that Purus should do is to keep the copied files up-to-date. So he should merge the old versions of this files from his plugin with the new ones from the standard Events plugin. And he should check the files all times when new Events update is released.

I cant fix the issue on my side. Purus should do it.

Regards

Sergey

Matt

Quote from Sergey Kambalin Purus copied a couple of files from the standard events plugin. These files were changed in one of the updates.

So how do we move forward from here? You guys both have great plugins, that we need and would like to work together?

What can be done?

Sergey - can you help?

Kindest,

Matt

Presumable this is where we need to make adjustments.

So if I adjust 

 public function isActive()    {        return OW::getPluginManager()->isPluginActive("event");    }

and add the x to event - I can get the check box to appear in the admin of compose message.

Briefly looking over Purus code - he seems to have extended the events classes..

eg 

class EVENTX_BOL_EventDao extends OW_BaseDao

So we need to figure out what classes are extended or added by eventx and adjuist the bridge to match?

Matt

Hello matt,

Thanks for your time in looking at the problem

And as I mentioned on the other thread. What will Oxwall look like if popular and quality 3rd party plugins cannot/do not co-operate together?

As you are a Oxwall Core developer & Oxwall Foundation member might you not work on our behalf (your customers) to ensure that a platform standard is set in place so that third party developers can ensure that plugins will work together?

I mean what will oxwall look like, as a project? - you can have these great features, but not these or these......

So great, you say "The special version of "Compose Message" have to be developed."

How will that work, can we do anything to help make that happen?

Kind regards,

Matt

Matt,

As a core developer I would say that it would be better if Purus develop plugin that adds all these extended features to standard Oxwall Events plugin using its programming API. In this case there would not be such conflicts. And it is best practice for plugin developers.

But Extended Events plugin has developed using another approach - "Copy & Paste", then adds all the new features. In this case all new features added to standard Oxwall Event will not be added to Extended Events.

As a third party plugin developer - Unfortunately, I do not have enough time to develop different version of the plugin to work with Extended Events plugin. 

You can try to replace all entries of "events" string to "eventx" in Compose Message source and replace all "EVENT_" class prefixes. 

But as a customer, I don't really care.  There are plugins with features available to buy. And I have paid for them. And they don't work together. Perhaps Puru's plugin, with great features should be rejected from the store? 

But like I said, I am the customer. And I tend to prefer that my service providers, provide me service. And with respect, not listen to the supplier complain about their difficulty. 

If I do that, in my work, I loose customers.

This is a sad situation, for the whole community.

But thanks for your advice, I will try to fix it myself. 

With kind regards, but frustrated feelings,

Matt