Joomla! Discussion Forums

I can't add a section to my site. The following error pops up in an IE Warning box.

mossection::store failed
Field 'params' doesn't have a default value SQL=INSERT INTO jos_sections('id','title','image','scope','image_position','description','published','ordering','access')VALUES('0','asdf','asdf','','content','left','asdfasdfasdf','1','','0')

I'm using PHP 5.1.1, MySQL 5.0.17-nt

I get a similar error when trying to create a category.

Trying to set a menu item to unpublished is producing the following error to appear in the area right above the menu manager table.

mosmenu::store failed Incorrect integer value: \\\'\\\' for column \\\'published\\\' at row 1 SQL=UPDATE jos_menu SET `menutype`=\\\'topmenu\\\',`name`=\\\'Contact Us\\\',`link`=\\\'index.php?option=com_contact

Using
PHP 5.1.1
MySQL 5.0.17-nt

U are using MySQL 5.0, Joomla 1.0.x is not compatible with MySQL 5.0 at the moment. We are working on a solution.

What is the time frame for such solution?  I know that 1.0.5 is due in the near future; will it be there?  Or will we have to wait until 1.1?  I do not care as much about making optimal use of new features, query optimization, etc., but more about it actually working.  There are many issues that I have encountered.  Most of them can be fixed by setting a column type from not null to null.  However, I have also encountered other issues, such as a problem with User check-in and another issue with user management - I can only see admin in the user list, and not other users.

Thanks for all your work,

Kyle Lady

This will probably be in Joomla 1.1. The roadmap is here: http://www.joomla.org/content/view/14/28/

I've run out of time to slip some experimentation into 1.0.5.  I should have a chance to get it ready for the next maintenance release within January though.

Hang tight.  The solution seems to be working.  Just need some more rigourous testing.

Is there a tracker artifact for this bug? I have a bug report on this for a component I made and I want to redirect him to the Joomla! tracker.

I'll send him here instead, for now

Regards,
Matthijs

Here is a prototype driver for MySQL for Joomla 1.0.5+

First backup your old /includes/database.php file

Then rename the one attached to database.php and copy it over the existing one.

I've not done exhaustive testing on it yet.  Please turn on site debugging and set error reporting to maximum if you come across any problems.

For those who know a little more about php set up, can you write your php error to a log file and monitor it as well.

Let me know how it goes.

This is strange,

I have sent in patches for all of my bugs I have encountered with mysql 5 and the have been accepted.

The I have six sites using mysql5 and It has been a while since I have had an sql issue. (1.0.2 was the last bug mysql bug I encountered if i recall correctly)

Looking at your errors this does not look to me to be a mysql 5 issue.

Ths last time I had this bug was in some python code in 2001. The problem was that the mysql database was set to an oddball default language. so the magic quotes became very confused, resulting in data corruption in the form of back slashes.

you may have magic_quotes_sybase or magic_quotes_runtime turned on, If either of those are on turn them off, and see if your problem goes away, also make sure that magic_quotes_gpc is on.

As I posted, I my patches to get Joomla working with mysql5 have been accepted long ago (mostly left joins) MySQL 5.0.11 caused a fair amount of pain, but that was dealt with a while ago.

I should clarify, this file is to support MySQL5 in strict mode, which is the default setting.

Interesting, I am using the FreeBSD port in it's default version with no extra options. (I have considered compiling it with BUILD_STATIC=Yes but otherwise this is a very default usage of MySQL5) And my only issue was a few joins.

the "\\\\" showing up in errors suggests to me a php problem not a mysql problem. At least It has never been a database problem when my previous mistakes created that. Sending the wrong character set, or not sending a character set has done it to me in the past.

After fighting with this for the past 6 hours[1], my solution is: comment out STRICT_TRANS_TABLES in my.ini

I've tried the patch posted above with no joy, error message follows:

Fatal error: Call to undefined method mosSession::_setSchema() in C:\Program Files\Apache Group\Apache2\htdocs\joomla\includes\database.php on line 757

This is on Win2K, Apache 2.0.52, PHP 5.1.1, MySQL 5.0.18 (win32 binary, not compiled from source).

[1] Fighting defined as 3 clean installs of Joomla (didn't have mambo, or joomla, or anyother CMS prior to this); clean re-install of MySQL (thought it might be their crazy latin1_swedish_ci default setting, before realizing it could be changed in my.ini).

Oh well.

If you're having problems and the above patch doesn't work, AND you have control over your MySQL server, edit my.ini. Duplicate the line beginning "sql-mode=". Comment the original out. Delete "STRICT_TRANS_TABLES" from the copy and restart MySQL.

HTH.

/mike

Mike,

deleting the STRICT_TRANS_TABLES has solved my problem and Joomla is now running on my test server. Thanks.

It's a shame it took three days for me to find this thread.

Ted

Ted,

I can't really blame the Joomla folks. I'd upgraded to PHP5.1.1 the previous week which broke a number of my internal sites (strtodate() seems to have b0rked or changed). And installed MySQL 5.0 which, while working, has some miserable online documentation... I can't even find the page on their site which references the "strict" as related to dates that clued me to suspect that php5.1.1 might be passing problem dates to MySQL via Joomla (seemed to be the error Joomla was reporting).

Living on the edge. Oh well.

/mike

Hi Mike,

I have PHP5 1.1 and mysql 5.018 loaded and all my other PHPBB and PHPNuke sites were working fine.

I found Joomla and decided to give it a try only to get the bug. I naturally thought (I should not think so hard) the issue was Joomla related and posted a note here in a subject related to mysql problems. I BUMPed it the next day and never received a response.

I searched again today and thankfully found you post. No big deal and I'm not upset  at all. I just thought that a bug of this nature would have a higher profile on the site.

OK, now what happens to the Joomla users that do not run their own serve and may not have the ability or can't get their ISP to change the my.ini?

Nothing worse then installing a new package that won't run. My usual action would be the delete key.

Ted

Hello Ted,

With regards the bug's low profile, it seems to require the latest MySQL (alright, 5.0, I haven't tried 5.1), PHP and Joomla to bite. Not may ISPs are going to be running those versions. Yet. The support issues would be a nightmare. And most Joomla sites are probably hosted by service providers, not an individual's PC.

I'm still not sure what changed in PHP5.1.1 that caused my problems. PHPmyAdmin seemed to have no problems with MySQL5.0.18.

Our company's installed SharePoint Portal Server. On IIS. I'm one of the few interested in open source here. But I have got a couple of Apache servers up and PHP/perl driving SQL Server databases. I was hoping to find something to compete with SharePoint. I'd been reading a lot about Ruby on Rails, but getting it up and running and learning a new language has been a slog. A site I follow had been running a discussion of CMS packages and Joomla/Mambo was mentioned. Looked easy enough to test. And it probably would have been if I'd followed the advice and stuck to MySQL 4.

And at least the boards here, while not easy to navigate[1], don't seem to delete posts they don't like[2]. And the email notification is a nice touch.

/mike

[1] not easy = not familiar. If you've ever been to Apple's discussion boards you've probably seen [2].

Please also read this thread. Mysql 5 support is not totally there yet, but it's getting there: http://forum.joomla.org/index.php/topic,23659.0.html.

I commented out the 'STRICT' clause in my.ini and got the user registration for Joomla 1.0.7 to work.  However, Administrator cannot login...some problem with that piece.

I desperately would like to see Joomla work with MYSQL 5.0 as that RDBMS rocks....and so does Joomla and the combo would be awesome!

What version of MySql are you try to use.

My local development server utilises
Apache2
MySql 5.0.17
PHP 5.11
&
PHP 4.4.2

and everything works correctly

Would you happen to be using windows?

It seems that the defaults of MySQL5 on windows are more problematic, If you are I will look at the windows config files from MySQL.com to see if I can tell what is going on.

Well as it happens I develop on Windows and the server environement is a WAMP and I have not noticed any problems in my development and testing.

I am glad I found this thread. I came across a similar error when I was testing/developing on

1) Joomla 1.0.7, PHP 5.12, MySQL 5.0.18, Apache 2.0.55 on Windows
2) Joomla 1.1 Alpha, PHP 5.12, MySQL 5.0.18, Apache 2.0.55 on Windows

That means I was able to duplicate the problem as well. Stingrey, maybe you can have someone do additional testing outside of your development/testing environment and see if they can duplicate it.

I had to delete "STRICT_TRANS_TABLES" from my.ini for MySQL as well to be able to move forward. My error was when I was trying to create a new frontpage menu component.

Thanks.


RedBox

Thank you all for your ideas. I just came to this forum to look for solutions since this mosuser::store failed problem annoyed me for many days. When I comment out the line STRICT_TRANS_TABLES from my my.ini everything works now!! Great!! Thank you all.

There is reported bug in 1.0.7 that affects the core when running in MySQL under strict mode.
Hopefully the upcoming 1.0.8 release has solved this issue.

I encountered the same error as described in the first message of this thread after installing Joomla 1.0.8 yesterday.

System details:

Windows XP
Apache 1.3.23 (Win32) PHP/4.4.1
MySQL 5.0.19-nt



That worked for me. Thanks a lot, Mike.

WAMP5 does NOT have this so-called line in the my.ini for me to comment out!!!

I have googled for a solution to turning off strict mode in WAMP5 but no good.

Please can anyone help me.  I have WAMP5 on a SERVER2003 platform

Try add following to my.ini

sql-mode=MYSQL40

Should set DB to run in MYSQL 4 comapatability mode.



However, it should be noted that WAMP5 shouldnt be running in strict mode by default, at least it hasnt on my version I user for development purposes.

Is there anyway to do this through myPhpAdmin? 

I don't have access to the my.ini file with my host.