You don't. Admin is basically never used again. You should have mapped a VB usergroup to administrator. That user should have admin privis. If not, deactivate the plugin (just rename the plugin file), login as admin, rename the plugin to the original name, turn off integration, and remap the usergroups correctly.

Well that's not going to work because only the original WordPress admin has a level 10 access! All other WP admins are only level 8 :(

So basically what you're saying is that by installing this hack that the main Wordpress admin (level 10) is removed? :confused:

From what I understand, version 2.x does not use user levels, it only uses roles:

http://codex.wordpress.org/User_Levels


So being an 8 or a 10 is not relevant.

Further information follows:

http://codex.wordpress.org/Roles_and_Capabilities

That would be incorrect. Firstly, they still describe using both roles and user levels on their site for the current version.


The admin that this hack imported is a level 8, not a level 10. There needs to be at least one level 10 admin in control at all times. We cannot just effectively delete the level 10 admin as you suggested that this hack does. We'd love to use this hack, but not at the expense of losing our level 10 admin account :(

Secondly, we tried to install another plugin the other day and we received the error: "Sorry, a user level 8 cannot make this change" so we know levels are still being used. We are also using a fresh install of their latest version (2.1.1).

You failed to read further down that page:

"Maintained for backward compatibility for Plugins"

The error you are getting is most likely from the plugin you are trying to install, not WP. The plugin needs to be updated.

I can install/uninstall any plugin on three different fresh installs of the latest version of WP. User levels are now deprecated.

The page clearly states:

Does anyone have this working with VB3.5.x ? If so, were there any modifications involved?

It has been a while since I have used 3.5.x, so I cannot be a 100% sure. From what I know of the VB code, I see no reason why it will not work, but please report any problems.

2.1.2 is a mandatory upgrade, as a cracker has altered 2.1.1's files. However when we went to upgrade and tried to activate this plugin we received this error:


How should we fix this? :confused:

Also, we came up with a great feature idea if you'd like to include it in the next version. Since vB members are now automatically being subscribed to the sites blog, it would be great if their avatar also carried over. This way when they post a comment, their vb Avatar would also be displayed :)

All that error means is the column already exists. The plugin should be enabled at that point. If it really bothers you, delete the vb_threadid column from the wp_posts table.

can I use subdomain? like blog.flunkme.com for the blog? also do I have to change usergroup? can I use default vb name? like registered group?

thx.