I'm wondering if it's possible to have two installations on the same live site...I want to keep the current production of 2.5.9 up while spinning up a new version 2.6.6 or 2.7 on the same site. Most com_s can do this by renaming the new com_ files, but has anyone been successful in doing so with dtregister?
My situation is the current version (2.5.9) has live registrations occurring and I can not create a new Discount Code in the admin - simply won't save.
There are other features I want from the newer versions, but I can not risk migration to the newer version until I can validate it without breaking the current version.
As with any component, you can NOT run two versions at the same time UNLESS you rename EVERY file, make a copy version of every database table for the component, then modify every file to change all database references to point to the copied tables. Lots of work... and not necessary. You should just make a copy of your whole site on a test location and install the other version there.
You won't find any support for 2.5.9 since it is extremely old. Any version you upgrade to will be better than what you have. 2.6 was a major jump in development from 2.5. Now 2.7 is an even bigger jump. Thanks.
Thanks for info...I was going to the clone the site, etc but hoping to avoid that - although you make a good argument on level of effort.
I notice 2.5.9 is "old" in terms of the current build; however, it was only purchased and installed in January of 2010 (the latest build as of that time)...while 13 months is a while ago...I would argue that DTRegister goes through a bit too many MAJOR builds in short time periods. While the feature and functionality improvements are GREAT...doing upgrades every other month is a bit high maintenance. It's just the delicate balance of product road mapping and getting new features to market.
just my $.02
Thanks for the quick solution idea for me to spin up and test.