[m0rgulvale]

Hi, when I try deleting a style "vB3 Mobile Skin" I get following error on vbulletin 3.8.7 pl5.

Could not find style with styleid = 0.

I think the problem might involve my style table not having 'styleid' set to auto_increment.. it appears most other vbulletin tables have that.

mysql> describe style;
+---------------+----------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+----------------------+------+-----+---------+-------+
| styleid | smallint(5) unsigned | NO | PRI | 0 | |
| title | varchar(250) | NO | | | |
| parentid | smallint(6) | NO | | 0 | |
| parentlist | varchar(250) | NO | | | |
| templatelist | mediumtext | YES | | NULL | |
| csscolors | mediumtext | YES | | NULL | |
| css | mediumtext | YES | | NULL | |
| stylevars | mediumtext | YES | | NULL | |
| replacements | mediumtext | YES | | NULL | |
| editorstyles | mediumtext | YES | | NULL | |
| userselect | smallint(5) unsigned | NO | | 1 | |
| displayorder | smallint(5) unsigned | NO | | 0 | |
| importstyleid | bigint(20) | NO | | 0 | |
+---------------+----------------------+------+-----+---------+-------+
13 rows in set (0.00 sec)

Info from style table:

mysql> select styleid, title,parentlist from style;
+---------+------------------------+------------+
| styleid | title | parentlist |
+---------+------------------------+------------+
| 1 | Default Style | 1,-1 |
| 5 | Skilltest - No Sidebar | 5,-1 |
| 13 | DarkShadows V5 | 13,-1 |
| 0 | vB3 Mobile Skin | 0,-1 |
+---------+------------------------+------------+
4 rows in set (0.00 sec)

If needed, I can pay someone for help fixing this via paypal.

Any idea what is wrong and how to fix?

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

update:

I ran the following query (safely against a test backup):

ALTER TABLE `style` CHANGE `styleid` `styleid` SMALLINT( 5 ) UNSIGNED NOT NULL AUTO_INCREMENT;

After that I am able to delete vb3 mobile skin which previously had the styleid=0

Everything appears to work after that . no database errors or anything

Is this a complete fix or do I also need to modify other tables?