CMS Made Simple Forums

I went into phpadmin to check that field. There was this error:

'Warning PRIMARY and INDEX keys should not both be set for column `content_id`'

I thought something must have got scrambled in my install, so I just said to hell with it and deleted my database and created a new one (I've made copies of all css, etc.), reinstalled cmsms, then rechecked the database. The same exact error message is there. Did it all again, a third time: same results. Is this something I should ignore? Is it a bug? Some lack of my server? 

Edit :In fact, there's little exclamation symbols all over the cmsms db... I've got 8 MySQL databases installed presently, this is the only db install of them that's showing errors, so I'm kind of doubting it's an issue with my server. Man, I'll get back to this later. 

So....just wondering, has anyone else taken the time to actually look at their databases created by the latest beta? Is this just an aberration on my end, and everyone else's installs are fine?

Running:

PHP version  4.4.2
MySQL version 4.0.22-standard-log

Anyone? Anyone? Bueller?

Ok, some more research.  Text fields in mysql are 65535.  There is also mediumtext and longtext.  I've a feeling that the 20k limit might be comeing from FCK, because there is no checking at alll for length on the cmsms side.  Try pasting all of that stuff without FCK on.

I did try that, wishy - read up several posts.

Any ideas on the db errors I mentioned? They are there on every fresh db creation so it obviously has nothing to do with me tinkering with the script afterwards....

Thanks Patricia. I set the field to longtext so we'll see what happens, I might not get to play with it tonight. Here's the warning message I see, though:

Keyname  Type  Cardinality  Action  Field
PRIMARY PRIMARY 29  Edit Drop content_id
prop_name
content_id INDEX None  Edit Drop content_id
prop_name
Warning PRIMARY and INDEX keys should not both be set for column `content_id`

Those warnings are on all the content fields, a couple of the admin ones, a css or two, etc., most just say:

Warning No index defined!


I'll check them out after I've build up a few pages, etc.

Thanks again.

Okay, the good news is that setting that field to longtext allowed me to finally paste that entire table on the page and everything's in the right place, so that's all it was. Thank you.

The bad news is the db warnings, doesn't look like there gonna go away by themselves. However, since I haven't seen yet that they're actually adversely affecting anything, maybe I can just ignore them.