Can't Create Category "Bonk" Vanilla 2.0.1.8 (beta2), Error Screen Included

ckizer

1. GO TO HTTP:// forum/vanilla/settings/addcategory
2. Enter Category "test"
3. Click "SAVE"
4. ERROR

ERROR SCREENSHOT:
http://kzr.me/9ClZ


I have a brand new clean install of Vanilla forums using 2.0.18 (beta2). It has the default general category. Everything in my install works great, posting, configuration and setting it all up went smoothly.

The one thing I cannot do is create new categories. Everytime I try to create a new category, with normal permissions, or custom ones i get a "bonk" error.

Here is a screenshot of what the debugger outputs when I try to create a new category. Can someone help me with this? I really, really need the ability to create categories.

UnderDog

Real error message : "Duplicate entry for key PRIMARY" (and then a really big number for any integer)
I would think that MySQL ran out of numbers to give you a new primary key.
You could try to fix it by adjusting the field type, keeping it integer of course, or making the field bigger. For example change int(11) to int(22)

ckizer

Main line of the error is this for those who don't click the screenshot:

281: trigger_error(ErrorMessage($this->GetPDOErrorMessage($PDOStatement->errorInfo()), $this->ClassName, 'Query', $Sql), E_USER_ERROR);

UnderDog

Real error message : "Duplicate entry for key PRIMARY" (and then a really big number for any integer)
I would think that MySQL ran out of numbers to give you a new primary key.
You could try to fix it by adjusting the field type, keeping it integer of course, or making the field bigger. For example change int(11) to int(22)

ckizer

what? Is this something I can do with phpmyadmin? What exactly would I do? This is a brand new freaking database I created over a cluster server on media temple. Just please let me know what to do?

ckizer

Here's me on the GDN_Category under phpMyAdmin, what can I do in here to test what you are saying?

http://kzr.me/9FDJ

ckizer

I changed these ones and I still get the error:

CategoryID, ParentCategoryID. Nothing else, how can these be out when the entire list in the field is null?

ckizer

Again stil a fatal error, I even tried 225 for the size of categoryID and parent category ID, same EXACT error, can somebody please help me?

http://kzr.me/9Fgg

Why does everything else work fine except adding 1 category? I get that it's out of ids or whatever but how is that possible? I've got this database and ZERO categories.

ckizer

I've now tried everything, setting everything in that group to int(22), and I still get the same can't read the auto-increment, if I disable auto-increment I don't get a fatal error when I hit "Save" I get "category requires an ID", what can I do to fix this? I really need this asap

ckizer

Arrg I just reinstalled the entire thing with a brand new database, and the exact same errors, WHAT do I need to change why can't vanilla support categories with media temple grid server?

UnderDog

Both screenshots look the same. Show the categories table in phpMyAdmin again and the error message screenshot you keep getting (new screenshot)

tldr

I did a fresh install today, also on MediaTemple, and also I cannot create ANY categories.

I just get this error every time:
Bonk
Something funky happened. Please bear with us while we iron out the kinks.

I've been able to post and alter/save all other settings.

vrijvlinder

Please follow these steps to get behind the problem

http://vanillawiki.homebrewforums.net/index.php/Bonk_Errors

peregrine

@tldr

better not to necropost on a 2 year old discussion unless you are using Vanilla 2.0.1.8 (beta2). which is mentioned in title of discussion

which I recommend not using. 2.0.18.8 would be a vast improvement.

after you read the post by V read this and the associated links and start a new discussion if you still have problems.

http://vanillaforums.org/discussion/23130/forum-post-ettikett-etiquette

http://vanillaforums.org/discussion/17954/food-for-thought-forum-etiquette

P.S. Necroposting on the forum is best done on Halloween, on other days it's not good form