Does the October Team have a policy oh how they deal with unresponsive developers that have paid products available.
Whereas I completely understand that some are not an actual business, and have staff or a lot of free time to answer questions everyday. However after using many different means of communication for a month now without an answer is some cause for concern. My project has basically been on hold this entire time and Im now debating if I need to move in a different direction. If it wasn’t for the fact I have invested a huge amount of time and resources into October I would have already moved on. However I see a lot of potential in the product and want to see it through. To me there needs to be some kind of accountability towards developers that are allowed to distribute their products through your platform.
welcome. it may be concerning that plugin/theme is paid and there are no support for that. but let me ask you this. how exactly you will gain any information if developer will answer or may have a ticketing system, to ensure, that OC dev team can “approve” such developers?
what is exactly that questions that may be asked before publishing any plugin etc?
first of all, it is on each developer to take responsibility for work, right? not a “marketplace”
I dont think is a matter of what questions to ask a developer before allowing them to publish a plugin etc. Its a matter of the October Team setting exceptions that a developer must follow to have the privilege of having their products in the Marketplace.
The October Team is providing a direct conduit for a developer to sell and market the products they create. Yes, October redeems some benefit and value from this. However it can create some negative benefits and reduce its value add as well. Such as this case where I am trying to get some information. When I discovered October I was super excited because this was my direct replacement from DotNetNuke. Originally I thought I was going to stuck Wordpress after seeing the decline of DotNetNuke. However after diving deep into Wordpress I found out it wasn’t the solution I was looking for.
I see huge promise in October, I just need to get over its learning curve. This takes time due to my schedule.
This is a good question. Technically you are paying for delivery of the code, to help you complete your project faster. Where the code often represents a reference piece of work or is self-documenting.
The level of support provided is enough to get the product functional, then after that, it is up to the author. If the product is not functional, we will remove it from the marketplace.
It should be noted that in many cases, developers will treat the author as free technical/education support for October CMS, and in many cases the author will help. However, this isn’t really fair to them and we should recognise this.
There are also cases where the product ideally could be improved to better serve the customer. In other words, feature requests. This is entirely at the discretion of the author. If the author doesn’t add features you need, the license permits you to modify the plugin/theme yourself to achieve the required outcome.
I agree and disagree on your thought that as a enduser I am paying just for the delivery of code to produce my project faster.
October has provided the means for the developer to offer support and market the modules and themes. In addition this developer has taken advantage of the infrastructure provided to offer support.
In return the developer gets to continually benefit from selling his or hers products and October receives a cut for providing the platform and added exposure to make the product better.
If developer chooses to go off grid or stops providing basic support for his or her product. In addition if October doesn’t police this is some form or fashion by continuing to allow the products to be showcased Its creates a negative image for both parties.
October should be presenting what expectations are required as a developer to allow them to sell through there platform. One being that you have to remain active and provide some level of support for the product. If your inactive for a period of time this information should be reflected to the consumer and presented as purchase at your own risk, or the product in question should be pulled making it no longer available. This way the developer doesn’t continue to profit through the October Market. In my case have been waiting months for what should be a very quick answer. I have managed to figure some of the issues out myself and I have provided updates showing this. However a couple of items are still present. So at this point the product is not 100% functional becasue I have followed the instructions and cross checked myself several times to make sure it wasn’t operator error. In addition I dont seem to have a way to re down the theme module to compare my changes to the original code. Based on the way the marketplace pushes the modules to your site its like a one way trip. So I am frustrated that I have put a lot of time into this and haven’t made any progress to move forward. Im sticking with it because I see the value in October