Yes, this is for better control for developers, it makes it so that an addon can only be added to 1 site and for example if you use your account (dojodesign) you can have all the addons but only allow to install/update specific ones.

OK... so I already have purchased eCommerce for a website so to use it on another site I have to purchase a second copy?

What happens to sites that I have built before 5.4 which does not let me associate an add-on?

All market place addons/themes can only be used on 1 live site and 1 dev site per purchase of the addon

I did not know that. There is nothing stating this on the Concrete site as I can see. Looking in the add-on section nothing explains this too.

For example, whats to stop users downloading the add-on and adding this to various sites? The add-on do not link to a specific site pre 5.4.

If I can't associate them to a site will they just stop working? I need clarification on this as clients will go spare if there sites suddenly stop working.

Sorry just found the licence about the one copy... sorry.

But the pre5.4 question I need clarification as I say.

Thanks for all the advice.

Just another point... even the free add-ons do not show in the admin section of 5.4 once logged in.

Yes.

licenses for commercial add-ons have always been one per "instance" with an instance defined as your live site plus whatever development stages and backups you need. Every add-on has always had this license listed in its pages in the marketplace, we haven't changed a word in there as part of this release (just to get that out there.)

support for add-ons is now private to people who have bought the add-on or are part of a project team (through the project pages) that is using the add-on. This makes it far easier for 3rd party developers to understand what the environment they're providing support for is from ticket to ticket.

You still should be able to install your add-ons by connecting to the community from a 5.3.3.1 site. You can still also "save for later" on a free add-on and install it on your 5.3.3.1 site or a 5.4 site using the add functionality, so I'm not sure what you're describing with the last post as not working but I need some screenshots and clarification.

You can also still install things by hand through the /packages directory. If you are unable or uninterested in connecting your site to the community, or perhaps you're working with your own add-ons that need to be installed, everything that behaved before by using the /packages directory works the same.

Nothing will ever stop working because an add-on has been installed on more than one site. The worst that will happen to your client is they will go to hit "get updates" on an add-on and be informed that the add-on doesn't seem to be licensed to this project page. Nothing will break.

We're trying to create a system where there's value to the site developer, site owner, and add-on developer to all do "the right thing." This means buy a copy of an add-on for every new project you use it on so the 3rd party developer can actually afford to keep working on it. This also means 3rd party developers have to provide quality support, or sales will be refunded. You're going to see us continue to buff out the project pages and concrete5.org architecture to support these various relationships without enforcing our will on the system.

The idea here is concrete5 is your car, we're never going to weld the hood shut or tell you what you can and can't do with YOUR car. However, if you're buying accessories for it and getting help making them work, its quite reasonable for the people who make a living designing and supporting those accessories to know which car they're trying to make them work in.

thanks for the clarification :) I noticed under Profile--> My Downloads that there's a Unassigned note under each Add-on. How is does this wind up Assigned? Do I do it by updating or is it done automatically in some manner? It would be nice to be able to shift the license from site to site, as something purchased for one site might not be necessary in the future and would be better used on another site.

Thanks for enabling this. I know it might seem like a pain for people, but it actually becomes annoying to try to remember what license was purchased for what site, so it can help in that regard.

You can assign licenses to projects once you've connected the site to the community from your site's dashboard. That will make a page here for you site with the tools you need..

Yes releasing a license from one project so it can be used on another, as well as "gift" licenses that our 3rd party developers can grant to repeat customers who they feel need support but deserve a kickback are both on our to-do list.

understood. thanks!

I completely agree with having to purchase the add-ons every time you use them... Concrete is free so its the least we can do to keep it that way! ;-D

I was only concerned that if a site built pre 5.4, because it does not give you the option within the dashboard to associate an add-on, that it would stop working because it can't see the licence. From what you are saying this is not a problem.

As for the add-ons not showing up I have attached a screenshot. I have just installed 5.4 on my server, not altered anything, logged in with my account and no add-ons show (I have a few free ones in there so they should at least show?)

Hope you can help.

Cheers and thanks again,

Chris

In order for them to show up you must first connect your site to the community and than assign licenses to that particular site. Then they will begin showing up.

Alternatively you can always upload them via ftp, in the /packages directory. Remember that sometimes when uploading the folder is placed within a folder to prevent unzipping issues, so when your uploading make sure it has a controller.php file.

Hope that helps!

Cheers,

Thomas