Yea, no issues with update to 4.2.2 but I have a question about admincp version

[pityocamptes]

Admincp version still says 4.2.1 but board shows 4.2.2. Is that normal?

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

Oh, one more thing, do I delete the entire install folder after done?

[tbworld]

Originally Posted by pityocamptes

Admincp version still says 4.2.1 but board shows 4.2.2. Is that normal?

No.
Did you alter your default admincp directory in 'config.php'?

Oh, one more thing, do I delete the entire install folder after done?

Yes

[pityocamptes]

Originally Posted by tbworld

No.
Did you alter your default admincp directory in 'config.php'?

Yes

Yes, I did. How do I fix this? I changed the default file name to another for security.


I also changed the modcp file name to another, if that makes a difference... in the update...

[tbworld]

Just upload the v4.2.2 admincp files to the new directory you created. You can also just copy them over from the default directory if you know that it is clean. Best practice is to reupload the files to the right directory. You should delete the directories you are not using after you have made a backup. Always make a backup!

[pityocamptes]

I wonder if the mods I have would affect the admincp? I'm hesitant to overwrite with the vanilla upgrade copy...

Also, would the modcp file have been altered?

What happens if I change the file names back to the original names and rerun the update? Then change them back to what I have in the config file?

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

Ok,changed the files to the 4.2.2 but it still shows 4.2.1 in the admincp. Also, do I need to change the modcp files?

[tbworld]

Originally Posted by pityocamptes

I wonder if the mods I have would affect the admincp? I'm hesitant to overwrite with the vanilla upgrade copy...

First backup ... always, always.
You are just writing over the directory like you were doing an upgrade. Your database should have already updated when you did the original update process to v4.2.2. Your 'mods' usually do not directly modify the vbulletin files. It would be rare.

Originally Posted by pityocamptes

What happens if I change the file names back to the original names and rerun the update? Then change them back to what I have in the config file?

I am not sure why you would have to do any of this. What names would you be changing? You do not need to run the update again.

[pityocamptes]

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

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?

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

Plus. I don't know if this is an issue but both the "admincp" and "modcp" are password protected... any help appreciated. Thanks!

[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...

[pityocamptes]

What happens if I un pw protect the file, change the name back to its vanilla name, and rerun the upgrade?

[Elite_360_]

Originally Posted by pityocamptes

What happens if I un pw protect the file, change the name back to its vanilla name, and rerun the upgrade?

if you are talking about the config.php file then i would use password protect for dir "includes" instead that would be more secure.