Old version# on 2.2.14?

Is anyone else seeing "Version 2.2.13" after upgrading to 2.2.14?

I went at the upgrade in an odd way, since I had a traditional 2.2.13 install with a moved core and renamed manager.

• I downloaded the advanced distro of 2.2.14, zipped up the core and setup dirs, uploaded, and extracted them.
• Setup wanted to do a clean install, so I edited the setup/includes/config.core.php file to point to my moved core (+ the "advanced" line).
• Setup looked normal. Never asked me anything and showed all the correct paths in the check. Completed with no errors
• I deleted the setup and core directories and cleared the core/cache dir.

Everything seems fine front and back except that I'm seeing MODX Revolution 2.2.13 (Traditional) in the dashboard. Setup also showed me 2.2.13 as I installed, though I definitely downloaded and used modx-2.2.14-pl-advanced.zip.

I do have updated directories in both the manager and core directories, so I'm assuming that I've got the bug fix.

Not sure where to go from here.

It's showing 2.2.14 for me properly.

I'd suggest running the upgrade again as it does sound like it didn't update properly. I tend to simply get the traditional zip and upload the files to the right (moved/renamed) folders and then run setup, works every time.

What I did was *way* easier than copying the various sets of files to the correct directories, so I was hoping to find a way to make it work.

I was hoping to avoid copying the files but it looks like the next step. I've run Setup several times. Strangely, the target dirs. shown during Setup are all correct and I do have directories in them that were updated today.

I was just wondering if maybe they forgot to update the version number on the Advanced distro.

I ran into this on an advanced upgrade two days ago. Re-placing the setup folder and re-running setup fixed it though. This was a 2.2.13 to 2.2.14 upgrade.

FWIW this also occurred on one of my standard installs while updating to 2.2.13 about a month ago (just after release of 2.2.13). Had to re-run setup that time as well, but that one required a fresh manual version of the 2.2.13 zip file and full upgrade process.