|
akademie bios
|
July 27, 2018 at 5:08 am
I am aware that currently there is no official Woocommerce integration available. I read about a third party offering a service to do such an integration (plugin):
“The folks at Wisdmlabs have built and offer to build WooCommerce Integrations to their client’s specifications. You can find out more and request a quote here:
https://wisdmlabs.com/portfolio/event-espresso-ee4-woocommerce-integration/”
So I contacted them and they told me, they would need to rebuild the code they developed for one client to be up to date, and that would cost USD 1600.-
As I don’t want to pay that alone, I would like to ask the EE4 community, if there are others around who are willing to participate in funding such a development.
They would make an EE4 addon plugin to install easily and it would be open source, so future adoptions to WP core changes can be implemented by others as well.
Any one interested?
I will wait about 3-4 weeks for your replies and – if there are some others interested – manage the development.
regards
Clemens
|
|
akademie bios
|
July 27, 2018 at 5:09 am
I am willing to pay about 300 to 400 USD for this myself.
|
|
akademie bios
|
July 28, 2018 at 2:56 pm
@admin: you can delete this thread as I have posted the message in the EE4 roadmap board on Trello.
|
|
Tony
|
July 30, 2018 at 2:59 am
Rather than delete the thread, I’ll include the link to the Trello board thread:
https://trello.com/c/KEcG4rLB/15-woocommerce-integration-or-shopping-cart-features
That may give you a little more coverage from users that my be interested.
Good luck with your crowdfunding approach 🙂
|
|
ardiaful
|
July 30, 2018 at 11:19 am
Dear EE support team, there are threads in this forum since 2013 asking for an integration of Woocommerce and EE4 workflows. I really get surprised today when I read this thread and EE4 users are asked to pay a company for its own “R&D” and develop a piece of code that they will sell thereafter hundreds of times as a market plugin. I don’t think this is the right approach.
|
|
Josh
|
July 30, 2018 at 1:25 pm
@ardiaful,
Thank you for your concern, but that is not at all what’s happening here. No one is asking to pay a company for its own R&D to develop a piece of code, and Event Espresso has no intentions of selling or marketing a WooCommerce plugin that was developed by a third party.
What has happened is Wisdmlabs (a developer) made a custom integration for one of their clients. Other folks have expressed interest in a similar integration, and Wisdmlabs has offered to develop a plugin for a price. Event Espresso and Wisdmlabs are not affiliated.
|
|
ardiaful
|
July 30, 2018 at 2:21 pm
My apologies if I misunderstood your arguments. Nevertheless, I cannot agree with the approach to pay a developer a price to develop a commercial plugin for his own sake. Deliver us the plugin and we will pay for it.
|
|
Josh
|
July 30, 2018 at 3:04 pm
I don’t think that’s what’s being offered there either. No where does it say a commercial plugin will be developed.
|
|
Tony
|
July 30, 2018 at 3:20 pm
My apologies if I misunderstood your arguments. Nevertheless, I cannot agree with the approach to pay a developer a price to develop a commercial plugin for his own sake.
May I ask, why you believe hiring a developer to create a plugin/integration with a specific purpose is out of the question?
If a user (or multiple users) have a need for a specific workflow, feature, customizations, whatever that is not currently supported by ourselves, or maybe not even on our agenda (I’m talking in general, not specifically about a WooCommerce integration), why not look into hiring a developer to add that functionality?
If the choice is to move to a different plugin (if there even is one) that possibly doesn’t have the same feature set EE has but maybe has the 1 feature requested, or hire a developer to create that feature, your choice would be to completely abandon the current plugin and start fresh with another, regardless of your current registration data and/or customizations?
Even if so that’s the case for yourself, it’s not always as clear cut as that and users may be just as heavily invested into EE as we ourselves are, meaning changing to a different plugin would be incredibly difficult for those users.
So let’s say I, as a user, can not change plugins without significant disruption to my business but I need a Woocommerce integration. I find a developer who prices the job a X, I can either pay X in full myself if the project allows or see if there are maybe a few other users in the same situation that may want to split the cost and discuss the feature set of the integration with them.
That choice I mentioned is what is happening above, a user has a need for a custom integration with Woocommerce (which we don’t have) and is looking for any interested parties to join in creating/paying for said integration with them (and a developer).
Deliver us the plugin and we will pay for it.
If you mean for us, EE.com, to supply a Woocommerce integration and users will pay for it, that may well be so but simply put, we can’t have every feature, right now (as much as we’d love to).
We juggle the many various feature requests from users and use those feature requests to prioritize our developments but we simply can’t just jump straight on every single request right away for various reasons.
|
