I encountered this problem, too, and had to also manually create the table to solve it. Evidently some of the code in wp-content/plugins/wp-subdomains-revisited/plugin/install.php is causing WordPress to ignore creating the table when you install the plugin, perhaps only under certain conditions (it could possibly be due to the if statements governing whether this is an upgrade or a fresh install), but I’m too lazy to investigate.
For those who need to manually create the table to get this plugin to work, you will have to log in to phpmyadmin, fire up the mysql command line, or whatever tool you use to work with your database. This is the code that I entered to create the needed database myself (your situation may be different):
CREATE TABLE wp_category_subdomains (
cat_ID bigint(20) NOT NULL,
is_subdomain tinyint(1) NOT NULL DEFAULT 0,
not_subdomain tinyint(1) NOT NULL DEFAULT 0,
cat_theme TEXT NOT NULL,
filter_pages tinyint(1) NOT NULL DEFAULT 0,
cat_link_title varchar(255) NULL,
UNIQUE KEY id (cat_ID)
);
PLEASE NOTE: DO THIS AT YOUR OWN RISK. BACK UP YOUR DATABASE FIRST! ETC! ETC!
Note that the table name needs to have the table prefix set for your WordPress installation. I believe the default prefix is “wp_”. See the other tables in your WordPress database to verify.
If this is successful, a new table, “wp_category_subdomains”, should be added to your database, and then you will be able to change the plugin settings in your admin panel and have them correctly recorded. I created the database after installing and activating the plugin, but I don’t think it matters whether you create the table first or last in the process.