kolohe
17th of July 2008 (Thu), 15:46
First, a little background....
I do most of my EE "uploading" on my desktop machine. It's running Apache 2.2, MySQL 5.1.25rc and PHP 5.2.6. When I finish working with the photos locally, I FTP the files to the online server, and unload the database locally and reload it on the online server. It's been working well for a few years now.
It had been a while since I had added any new photos to the database, and I encountered a problem. EE would say that the photo uploaded fine, but there would be no corresponding entries in the ee_photo_size table for any of the photos that I added. Attempting to add a path in the photo editor would fail (with no error message). The photos were in the proper directory, so it was basically a database problem.
Getting it to work required changing a MySQL server option. 5.1 defaulted to STRICT_TRANS_TABLES when it installed. This option causes MySQL to reject SQL statements with values that are not valid for the column definition. I'm guessing (and this is only a guess) that the problem is occuring with some columns that appear to be defined as NOT NULL but with a default value of NULL. When I removed the STRICT_TRANS_TABLES option, everything started working correctly. This was simple for me, but it might be more problematic when you can't change the server options.
Pekka, can you put this on the list for the next update?
Thanks,
Paul
I do most of my EE "uploading" on my desktop machine. It's running Apache 2.2, MySQL 5.1.25rc and PHP 5.2.6. When I finish working with the photos locally, I FTP the files to the online server, and unload the database locally and reload it on the online server. It's been working well for a few years now.
It had been a while since I had added any new photos to the database, and I encountered a problem. EE would say that the photo uploaded fine, but there would be no corresponding entries in the ee_photo_size table for any of the photos that I added. Attempting to add a path in the photo editor would fail (with no error message). The photos were in the proper directory, so it was basically a database problem.
Getting it to work required changing a MySQL server option. 5.1 defaulted to STRICT_TRANS_TABLES when it installed. This option causes MySQL to reject SQL statements with values that are not valid for the column definition. I'm guessing (and this is only a guess) that the problem is occuring with some columns that appear to be defined as NOT NULL but with a default value of NULL. When I removed the STRICT_TRANS_TABLES option, everything started working correctly. This was simple for me, but it might be more problematic when you can't change the server options.
Pekka, can you put this on the list for the next update?
Thanks,
Paul