Modifying Existing Blocks
Permalink
Hi All,
I was wondering if there is a way to make a package that can be sold through the Marketplace as an add-on that would modify an existing block. Specifically, I am interested in modifying the Form block. I want to add a feature to the Form block, and I want to be able to sell it.
Please ask me if you have any questions.
I was wondering if there is a way to make a package that can be sold through the Marketplace as an add-on that would modify an existing block. Specifically, I am interested in modifying the Form block. I want to add a feature to the Form block, and I want to be able to sell it.
Please ask me if you have any questions.
The original developer released the block under MIT license. Does anyone know if this is possible though?
No you can't.
It's not allowed to sell add-ons for which need you to buy a different one first.
You might be able to modify the entire block though and sell it as a whole.
See the rules for it here:http://www.concrete5.org/developers/marketplace-submission-rules/...
It's not allowed to sell add-ons for which need you to buy a different one first.
You might be able to modify the entire block though and sell it as a whole.
See the rules for it here:http://www.concrete5.org/developers/marketplace-submission-rules/...
This is not entirely true. There are several addons for eCommerce that require eCommerce to be installed, it just needs to be made clear that this is the case in regard to the dependency.
You can check for a package being installed in your own package and return out without installing yours if your dependent add-on isn't installed, but at that point the end user has already purchased your addon(hopefully!), so you already failed them there.
So it just needs to be clear that the package you are depending on is spelled out in the description, otherwise you wouldn't see the various shipping addons or gateways for ecommerce.
You can check for a package being installed in your own package and return out without installing yours if your dependent add-on isn't installed, but at that point the end user has already purchased your addon(hopefully!), so you already failed them there.
So it just needs to be clear that the package you are depending on is spelled out in the description, otherwise you wouldn't see the various shipping addons or gateways for ecommerce.
I think it's more of a challenge of "How" rather than "Can". There are lots
of packages for sale which extend existing core blocks (which are available
for free w/the MIT license.) The trouble is how to extend them in a way that
doesn't fork them or make upgrades impossible. Right now the form block is,
unfortunately, not the most extendable add-on. It's view template is mostly
useless - it really ought to have far more view logic contained in view.php
than in controller.php. That's something we'll be working on. Also, adding
options to the form block is going to be difficult to do given the way it's
currently build. However, in the future (if we go with using attributes with
the form block, it might be easier to do this.)
of packages for sale which extend existing core blocks (which are available
for free w/the MIT license.) The trouble is how to extend them in a way that
doesn't fork them or make upgrades impossible. Right now the form block is,
unfortunately, not the most extendable add-on. It's view template is mostly
useless - it really ought to have far more view logic contained in view.php
than in controller.php. That's something we'll be working on. Also, adding
options to the form block is going to be difficult to do given the way it's
currently build. However, in the future (if we go with using attributes with
the form block, it might be easier to do this.)
Just my initial thoughts.