Buying an add-on: how many licenses?
Permalink 1 user found helpful
If I buy the blog add-on, for example, can I use and reuse it on all of my concrete5 websites? I haven't purchased a single add-on yet, so I have no idea how it works. I'm guessing it's probably just a zip file with some php files I can use and reuse til my heart's content, but I have no idea.
the standard license is good for one website.
thanks!
Every add-on has its own license agreement. If you visit an add-on in the marketplace, you will see a License link on the right-hand side.
If the add-on is free, you obviously are able to use it without charge. Although some may vary, the majority of paid add-ons adopt the standard Marketplace license, which reads at the top:
"In English
You own your copy for use on one (1) site and the development environment for it. Use it on another site, you should buy it again. Don't sue us."
Unfortunately for developers, I'm not sure how many people respect the license of the add-ons they purchase. The license is for one project -- if you develop a new site for a different client, you should purchase another license.
Once you purchase an add-on, you can go to Dashboard > Add Functionality and log-in to concrete5.org. You will then receive a list of all the add-ons you have purchased, which you then can download and install directly from the web interface. You also have the option of downloading a zip file and uploading it yourself, but the online feature is obviously easier, and integrates more completely with the update feature in most versions of Concrete.
While I'm on the topic, to update an add-on, visit Dashboard > Add Functionality again and there should be a tab for updating add-ons. You will then be able to update add-ons you have purchased to their newest version, again, without downloading or uploading yourself.
There are discussions in play for bulk licenses and other ideas for providing more licensing options for add-ons. Please feel free to share if you have any ideas.
I, for one, would never have considered purchasing add-ons before. However, when I've considered the practical cost to my clients, comparing the cost of my time and services with the cost of purchasing a ready-made add-on, I've come to realize that buying add-ons helps make things better for both myself and my client. For one, if there is an issue, I can rely on the add-on developer to handle it for me. Secondly, of course, it can be dramatically cheaper to purchase a license than do it over again myself.
Lastly, purchasing add-ons is one of the best ways to directly support the core team, as 25% of each sale goes back to Concrete, and 75% goes to the add-on developer.
If the add-on is free, you obviously are able to use it without charge. Although some may vary, the majority of paid add-ons adopt the standard Marketplace license, which reads at the top:
"In English
You own your copy for use on one (1) site and the development environment for it. Use it on another site, you should buy it again. Don't sue us."
Unfortunately for developers, I'm not sure how many people respect the license of the add-ons they purchase. The license is for one project -- if you develop a new site for a different client, you should purchase another license.
Once you purchase an add-on, you can go to Dashboard > Add Functionality and log-in to concrete5.org. You will then receive a list of all the add-ons you have purchased, which you then can download and install directly from the web interface. You also have the option of downloading a zip file and uploading it yourself, but the online feature is obviously easier, and integrates more completely with the update feature in most versions of Concrete.
While I'm on the topic, to update an add-on, visit Dashboard > Add Functionality again and there should be a tab for updating add-ons. You will then be able to update add-ons you have purchased to their newest version, again, without downloading or uploading yourself.
There are discussions in play for bulk licenses and other ideas for providing more licensing options for add-ons. Please feel free to share if you have any ideas.
I, for one, would never have considered purchasing add-ons before. However, when I've considered the practical cost to my clients, comparing the cost of my time and services with the cost of purchasing a ready-made add-on, I've come to realize that buying add-ons helps make things better for both myself and my client. For one, if there is an issue, I can rely on the add-on developer to handle it for me. Secondly, of course, it can be dramatically cheaper to purchase a license than do it over again myself.
Lastly, purchasing add-ons is one of the best ways to directly support the core team, as 25% of each sale goes back to Concrete, and 75% goes to the add-on developer.
