Just installed vbAdvanced, and I think I screwed things up!

[SCH]

Hi everyone,

This is my first post here, so please go easy on me. I should also mention I'm a real vBulletin novice too.

I've just finished going through the installation process for vbAdvanced, and I think I've screwed things up a bit. I just realized that I didn't chmod the modules folder to 777. The reason? There are two:

1. I missed it in the instructions.
2. I DON'T KNOW HOW TO!!!

So, my question is simple: How do I chmod the modules folder to 777 and what do I do after I do this (in other words, do I perform a reinstall?)

I also have another question.

During the final step of the installation, I was instructed to "Delete this file otherwise it could pose a serious security risk". The only problem is that it didn't tell me which file it was referring to. Is it the install file (vbacmps_install.php)?

Thanks very much in advance.

[SCH]

OK, I've just figured out how to chmod the modules folder (I did it through cPanel) to 777.

But I still don't know whether I should re-install the vbAdvanced software again. Should I perform an uninstall first then reinstall? Or just a reinstall?

The only reason why I ask is because I didn't receive any error messages (regarding the incorrect folder permission) during the initial installation, so I'm curious as to whether I even need to perform a second install.

[SCH]

Found the answer to my question about which file to delete. Turns out it is the install file (vbacmps_install.php) that should be deleted once it's complete.

Of course, I don't want to do that if I have to reinstall vbA (because of the incorrect modules folder permission during the initial installation).

So my only remaining question is: now that I've set the permissions of the modules folder to 777 (as per the instructions) do I perform a reinstall (ie. re-run the installation process) of the vbAdvanced software, or should I uninstall first then reinstall?

Thanks in advance, again.

[SCH]

Alright, just went through the uninstall and reinstall process(es), and deleted the vbacmps_install.php file as per the instructions.

Everything seems to be working OK... so far.