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