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

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?

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

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!

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?

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.

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.

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!

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 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] ---------------

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.

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

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.

Ok, well then, what do I need to do to get the version in admincp to show correctly? I already copied the upgrade files to the admincp and modcp folders, and nothing changed. Thanks.

run the upgrade

Ok, thanks. I was not sure if re-running the upgrade would screw anything up.

One more question, actually two more, will I need to change the folder names back to the vanilla names - ie, admincp/modcp, or can I just leave them as is, since I upgraded the files with the new vb version in these folders?

Also, for E360, I'm having issues with your username mod after upgrade, I posted in your mod thread. Thanks.

you should not need to change if you have custom "admincp or modcp" as long as you have the custom directory in the config.php file and upload the new vb version content of the admincp and modcp to your custom directory

the username markup is not compatible with 4.2.2 the next version is

Ok, thanks! on the usermark up, not being compatible, will I need to remove the template coding specified in the readme.txt, or how will the new version address the code from the older version of the usermark in the templates that were manually installed? Thanks again.

for support about my mods or any mods will have to be ask on that mod thread we are getting of topic here

Ok, posted in your mod... thanks

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

Ran the update again, no change, admincp still shows 4.2.1!!!!!!!!! While rest of board shows 4.2.2...... need some help on how to get this corrected...

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

I'm showing this for quite a few files when running suspect files in admincp:

File version mismatch: found 4.2.2, expected 4.2.1

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

I thought it might have been because I copied the original config file into the upload folder and replaced the new one, but after looking at both files I don't think was the problem...

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

I assume this is how you are supposed to do an upgrade:

I did NOT overwrite my existing folders and files with the new files through FTP, as I'm afraid I will lose my mods. I basically uploaded the UPLOAD folder to the root with all of the contents of the 4.2.2 version inside. I then pointed my browser to WWW.XXXXXXX.com/upload/install/upgrade.php and it ran. I assume this is how you are supposed to do it? Thanks.

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

OK, reading up and it looks like you have to overwrite the files. Now I am receiving these errors:

Warning: Declaration of vB_Database_Alter_MySQL::add_index() should be compatible with that of vB_Database_Alter::add_index() in ..../includes/class_dbalter.php on line 882

Warning: Declaration of vB_Database_Alter_MySQL::add_field() should be compatible with that of vB_Database_Alter::add_field() in ..../includes/class_dbalter.php on line 882

Warning: Declaration of vB_Database_Alter_MySQL::drop_field() should be compatible with that of vB_Database_Alter::drop_field() in ..../includes/class_dbalter.php on line 882

Warning: Declaration of vB_Database_Alter_MySQL::query() should be compatible with that of vB_Database_Alter::query() in ..../includes/class_dbalter.php on line 882

Warning: Declaration of vBCms_Item_Content::setItemId() should be compatible with that of vB_Model::setItemId() in ..../packages/vbcms/item/content.php on line 26

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

Does this have anything to do with the php version I am running?

php 5.2.17