Need to pay again for 5.7 add-ons?
Permalink
First, let me apologize if this has been discussed elsewhere. I couldn't find it with how I searched.
I also thought about posting it as a reply to this related thread:http://www.concrete5.org/community/forums/5-7-discussion/backward-c... but thought the topic could merit its own thread.
My question: if one has purchased a paid add-on for 5.6, what will happen when the add-on is developed and released for 5.7? Once I port my site over to 5.7, will I have access to the 5.70-compatible theme at no extra charge, or will it need to be purchased again? Will this be a site wide policy or up to each individual developer to determine how they will handle this?
Thanks for any help and insight!
Best,
Jim H.
I also thought about posting it as a reply to this related thread:http://www.concrete5.org/community/forums/5-7-discussion/backward-c... but thought the topic could merit its own thread.
My question: if one has purchased a paid add-on for 5.6, what will happen when the add-on is developed and released for 5.7? Once I port my site over to 5.7, will I have access to the 5.70-compatible theme at no extra charge, or will it need to be purchased again? Will this be a site wide policy or up to each individual developer to determine how they will handle this?
Thanks for any help and insight!
Best,
Jim H.
I too am a bit curious of this. Especially since package "upgrades" won't be backward compatible to 5.6 so package developers will be forced to either maintain 2 separate releases for every package or stop maintaining their < 5.6.x revision.
Has there been any information on how the marketplace is going to work with 5.7? Will it be a separate marketplace altogether?
Has there been any information on how the marketplace is going to work with 5.7? Will it be a separate marketplace altogether?
What wagdi said above is correct. Any purchase you make of any theme or addon is covered for all future versions of C5.
However, it is up to the developer of those addons / themes to make sure they are kept up-to-date with the latest.
The 5.7 release will be a major change from previous versions, so it may be a while before all themes and addons are compatible with 5.7. That being said, I would advise to wait a while to upgrade to 5.7, even after the official version is released.
However, it is up to the developer of those addons / themes to make sure they are kept up-to-date with the latest.
The 5.7 release will be a major change from previous versions, so it may be a while before all themes and addons are compatible with 5.7. That being said, I would advise to wait a while to upgrade to 5.7, even after the official version is released.
As far as I know there is no way to "upgrade" from 5.6 to 5.7 and as of right now I don't think anything is planned for this aside from speculated migration stuff potentially.
I also think that many developers may be reluctant to go through all their packages and maintain a 5.6 version (which is still receiving updates alongside 5.7) and a 5.7 version (which can't be backward compatible with 5.6). Would be interesting to hear what the plans are here.
I also think that many developers may be reluctant to go through all their packages and maintain a 5.6 version (which is still receiving updates alongside 5.7) and a 5.7 version (which can't be backward compatible with 5.6). Would be interesting to hear what the plans are here.
My understanding is that there will have to be two version of an add-on or theme, 'namespacing' seems to be the issue.
None of my add-ons or themes work with 5.7, I've tried locally and they just fail.
For the most part my updates are tweaks to the CSS files, so maintaining two versions, once I've got my around 'namespacing' should not be to much of an issue?
Releasing add-ons or themes from a 5.6 project will not load into a 5.7 project.
None of my add-ons or themes work with 5.7, I've tried locally and they just fail.
For the most part my updates are tweaks to the CSS files, so maintaining two versions, once I've got my around 'namespacing' should not be to much of an issue?
Releasing add-ons or themes from a 5.6 project will not load into a 5.7 project.
Thanks for the clarification, and the advice regarding migrating a site from 5.6 to 5.7.
I don't believe that's a promise we ever asked you guys to make. Updates to add-ons have been free in the past, but that's because there's no infrastructure to sell them not because there's some legal requirement.
As 5.7 will not be backwards compatible with 5.6, it wouldn't shock me at all if you had to pay for an upgrade or buy a new license.
As 5.7 will not be backwards compatible with 5.6, it wouldn't shock me at all if you had to pay for an upgrade or buy a new license.
However, if you like the theme or add-on so much that you would like to use it again for another website, you would need to purchase a new licence for the new site. (unless you disconnect/release the licence from a previous project and use/reconnect/reassign the same licence for the new project)
Basically you are allowed one licence per site but once you bought it, you own it, all updates are included! (Hope I got that right!)