[tbworld]

Originally Posted by pityocamptes

1)Ok, I overwrote the admincp files with the new 4.2.2 files - it still says 4.2.1 in admincp

Strange, I am looking into this. I do not have v4.2.2 loaded up on a development station. I am only looking at the source and so far cannot find why that would be.

Originally Posted by pityocamptes

1)
2) I changed the folder name of the modcp to XXXXX. Should I manually update the files in the"modcp" to the new files in the upgrade?

If you changed the name in the config.php, then upgrade the files from v4.2.2 source files to your chosen directory.

--------------- Added [DATE]1385113347[/DATE] at [TIME]1385113347[/TIME] ---------------

Originally Posted by tbworld

Strange, I am looking into this. I do not have v4.2.2 loaded up on a development station. I am only looking at the source and so far cannot find why that would be.

If it is still showing V4.2.1 then something is not write. Clear your cache in your browser to start with just in case.

As I expected the version number for the admincp is derived from 'class_core.php. It is then used in the admincp via the following php statement.

    define('ADMIN_VERSION_VBULLETIN', FILE_VERSION_VBULLETIN);

The constant 'FILE_VERSION_VBULLETIN' is defined in 'class_core'. So the question is what '/includes/class_core.php' file is your 'admincp' reading from. Something funky there...