Thread

I’ve unhidden the post you refer to, Blair, at your request.  We hide posts from support threads that do not contribute towards the resolution of the issue.  It’s not so much censoring as it is helping to keep the threads on track; the content is still there for all to read if desired.  You posed this question after our support staff three times asked you to upgrade from 2.1.2 to 2.1.3.  It is a required update for sites on 2.1.2 to receive support.  If you need assistance in upgrading, please do let us know and we will be happy to help you through that step.

Thanks, and now we can move on.  Yes, it does sound like 2.1.3 upgrade would solve everything, but there are conflicting messages.  I was able to confirm 2.1.2 does not have this bug fixed.  The change log does not cite this as a fixed issue in 2.1.3, and the bug report is still on “confirmed.” (https://support.ellislab.com/bugs/detail/13150/)  However the support staff say its fixed on 2.1.3…. so what is correct, the documentation or the support staff?  If the latest releases were better and easier I would simply jump to it, but EE’s track record of latest releases isn’t exactly trustworthy and the upgrade process is time consuming.  If I’m making the time investment to test for upgrading I want to be sure it will solve more issues than creates.

My site is live on 2.1, and I’m testing 2.1.2/2.1.3.  2.1.2 did not have this issue fixed, and was not in the change log of 2.1.3 so I asked the code line of the hotfix for either as I was looking into the difficulty level of an upgrade.  Since the support staff has been generous in helping with the suggestion of upgrading I would be happy to give the logins to perform the process and verify it’s condition.

Can you confirm if the bug is fixed, or if the documentation is correct?  If the bug is not fixed can you cite a hotfix?

Blair ,

My site is live on 2.1, and I’m testing 2.1.2/2.1.3.

To confirm. You have a 2.1.3 testing site?

At the moment I don’t have a codeline of a hotfix for you. I can confirm as before that this issue does not happen on my own install of EE 2.1.3 and has not been reported since the release of EE2.1.3

Can you at least test on your install of EE2.1.3 please?

I asked the code line of the hotfix for either as I was looking into the difficulty level of an upgrade.

The difficulty level does not change between upgrades. The version upgrade docs remain the same. We recommend a full version or build upgrade in any circumstance rather than line changes except in unique cases