Upgrade site clone availability on EOL versions
Just wondering whether anyone has come across an issue of not being able to clone their site for upgrade because it was EOL? E.g. let's say site X is currently on version August '14, would anything stop me from logging into https://hms.custhelp.com/cgi-bin/ssm-login.py and requesting an upgrade?
One detail is that it is possible that there was an upgrade clone site created over a year ago. So that old clone site would need to be overwritten, it is not feasible to upgrade the outdated clone site and then try and apply all the config, dev, content and other changes accumulated over this time.