[kallu]

Hi,

I ran across the following issue while working with the 9.9.5 release-

When trying to create a new category (by clicking 'Add A New Category' in admin_categories.php), the page simply refreshes without any new category being added.

I found that the query issued
"insert into `pligg_categories` (`category_name`) VALUES ('new category');"
throws the error
"no default value set for field category_desc".

After setting a default value manually, the error came up as
"no default value set for field category_keywords"

Setting a default value for this field rectified the problem and a new category finally appeared.

A look at the installtables.php used to create the tables at installation reveals that the sql used to create the categories table is
`category_desc` varchar(255) NOT NULL,
`category_keywords` varchar(255) NOT NULL,

It should have been
`category_desc` varchar(255) NOT NULL default '',
`category_keywords` varchar(255) NOT NULL default '',

Not sure if this bug has been reported before.
Anyways, hope it helps someone.

Regards

[Yankidank]

I haven't experienced any problems with this due to the current version of installtables.php. I've been able to generate new categories without a problem on two servers, not sure if your code is necessary or if this is just a fluke.

[chuckroast]

Hi Kallu

I can't reproduce his either, We will need a proper big report before this can be considered an issue and escalated.

When submitting a bug report please provide the server environment, OS, php version, sql version, Pligg Version, Template name. Etc...

Thanks

[kallu]

Hi chuckroast and Yankidank,

I am not surprised you could not reproduce the error I reported.
It would have been hard for me to believe that this version of pligg could have shipped with such a blatant bug.

Nevertheless, I did experience it. So I can assume that it appeared due to a specific combination of OS/ Web Server/ MySQL version, the stars etc.

I am on a WAMP setup. My server's configuration is-
WindowsXP running Apache/2.2.8 (Win32) with PHP/5.2.5 and MySQL 5.0.51a.
Pligg version is Beta 9.9.5 and the error was template agnostic (occurred in all templates I tried).

I suspect that "W" in the WAMP has got something to do with this bug
Anyways, if I encountered it, somebody else might very well encounter it too.

Taking a look at the installtables.php, I can see that most of the varchar fields defined as NOT NULL also have the clause that the default value is ''.
IMHO, and you guys know better of course, it would be better if we follow this practice and explicitly define a default value for every NOT NULL field, instead of banking on the sql installation to be smart enough and provide one by itself, where one is not provided.

Keep up the good work. Pligg rocks!

Regards
KK

[Yankidank]

I'm testing with WAMP on a Win XP computer right now. It worked fine for me. Were you working from an upgrade, or new install?

PHP: 5.2.6
MySQL: 5.0.51b
Apache: 2.2.8

[kallu]

Hi Yankidank,

I am working with a fresh install using the zip file downloaded from
Pligg Beta 9.9.5

[Yankidank]

I think I will still add it to the Pligg source, but its odd that this has only happened to you.

[kallu]

Hi Yankidank,

I think I found the answer to the problem.

MySQL in my setup is configured to run under "Strict Mode".
In this mode, MySQL 5.0.2 onwards will throw an error on INSERT/UPDATE if the column definition includes no explicit DEFAULT value and we do not provide one in the sql statement.
Please see
MySQL :: MySQL 5.0 Reference Manual :: 10.1.4 Data Type Default Values

Strict mode happens to be the default mode, I think, for default installations of MySQL on Windows.
I am sure a lot of Windows users are bound to run across this problem.

I am happy you have taken note of this problem.

Regards

[Yankidank]

Thanks for looking into what was causing your error, it's good to have some clarification. We've added the changes to SVN revision, you can see the update on the Twitter feed.

[neo2cold]

hi , I also have this problem , and I downloaded the latest svn ( the one titled "svn alpha release") and nothing has changed the problem still exist , but when I disabled mysql Strict Mode the problem was solved , but when Yankidank said that he has solved the problem what did you mean , and if you did please provide us with the files changes so that we can update >>> thanks

environment : win xp , mysql 5 , apache