I believe users who expect a plugin's compatibility with their third party items installed, are less technically skilled. They just would like an item to work well on their sites, and don't want to sort out why it could be incompatible with tons of other installed plugins.
This is a sign of increasing number of less technically-minded users among the Oxwall community. And I think it is a good tendency, which should compel developers to write more compatible plugins and themes. Furthermore, Oxwall provides all necessary options for this in its core.
Rob R and OxwallAcessories, this isn't a right place for personal support issues. Please, use reviews and plugin's forums for this.
I registered after I have purchased approximately 45 plugin, again, those who create the various plugins should cooperate more and exalt this 3rd party support. But often it seems so again it's just too easy and flush problems onto others who create plugins! One was strengthened and closer collaboration between all producers plugin and themes are absolutely necessary, as I see it.
So there is no choice but to hire someone to do the work - therefore either paying for plugin development and having to become a plugin retailer (when really one only wanted to be a customer) or simply swallow the cost - which is often not possible on lower budget jobs in this (global) recession.
Edit - so unlike the above posters (towards the top) buying a plugin and then have to fork it? - It means I need a team of oxwall experienced engineers, maintaining my suite of custom code, to support my clients - rather than handing over to their generalist IT admin.
So it rather illuminates the idea of store plugins having much of any value - when they don't inter operate. You may cuss the others systems all you like (and all suffer from plugin conflicts etc, its the name of teh game) but competition and a friendly community of developers takes care of business.
When a feature is only available in one plugin, from one developer, and is not compatible with other popular and good quality plugins - the market is a developers market. And the customer/client loses out. And therefore the community, and therefore the developers and everybody concerned.
For those of us, like me, who are trying to build the oxwall brand, and are responsible for many plugin and theme sales - we find our selves looking at other platforms for clients - simply because we cannot offer a full feature set without custom development costs that price us out of the job, using oxwall. So we use a different platform.
I try really hard to use oxwall when a social script is needed. But it is a struggle because of the lack of choice in the store.
With oxwall looking at CMS now - well that is an interesting move. But assets will need to be secured. for any of us setting up websites which are monetised or need asset protections beyond simple hashing of file names - an asset security system is going to be a must for some.
I am getting old, tis true, but I remember the days when the customer was king - and service providers worked for the dollar.
Fact remains, my clients (via me) will pay more for plugins that work with the other popular third party plugins - because as yet - the whole store plugin feature set is still basic - and any decent community needs a good chunk of them to offer anything like comparable to other platforms. And so the plugin developers (who are sometimes also core developers) are still filling the gaps fleshing out oxwall to something approaching a fully fledged system - until we get competition, instead of mini monopoly going, we are stuck.
So here's a basic business lesson for you youngsters, from an old timer. When you make good quality product that works with core and the other well respected third party products. People will pay the premium. And then... when you have made some cash - others will try and compete for the money with you. And you know what - the best, most useful code will most often win out, even if it sells for a higher premium.
Kind regards,
Matt