Install Errors (INSERT INTO pp_categories)
 

I'm getting the errors below. Can't figure out what the problem is. I created a database named photopost with no problems.

Any suggestions?

Step 3: MySQL error reported: [INSERT INTO pp_categories (id,catname,description,catorder,thumbs,parent,children) VALUES (1,'Main','',2,'no',0,'2')]
Result: Field 'theme' doesn't have a default value
Database: photopost

Step 3: MySQL error reported: [INSERT INTO pp_categories (id,catname,description,catorder,thumbs,parent,children) VALUES (2,'A Category','Photos of a particular subject',1,'yes',1,'')]
Result: Field 'theme' doesn't have a default value
Database: photopost

Step 3: MySQL error reported: [INSERT INTO pp_categories (id,catname,description,catorder,thumbs,parent,children) VALUES (500,'Member Galleries','Individual user galleries - any photo category',1,'yes',0,'')]
Result: Field 'theme' doesn't have a default value
Database: photopost

Step 3: MySQL error reported: [INSERT INTO pp_settings VALUES (169,'GMT Offset', 'gmtoffset', 'If you are running VB and want the server to display the time as an offset of GMT (for example, to the timezone where your server is located), enter the offset here.', '0', 25, 1)]
Result: Data too long for column 'description' at row 1
Database: photopost

Step 3: MySQL error reported: [INSERT INTO pp_settings VALUES (208,'Orignial Image storage directory server path','origfull','Typically this path matches your DATA directory server path, unless you want to store your original images seperatly from your thumbnails/medium images.','/path/to/your/photopost/data',35,1)]
Result: Data too long for column 'description' at row 1
Database: photopost

What version of mysql is on your server?

I have done probally 1500-2000 Photopost installs and never seen an error such as these?

Your not by chance running the new MYSQL 5

Yes, I just downloaded it and installed it yesturday.

There you go thats the issue. If you go back to mysql 4 bet things work without a hitch

No one is using mysql5 that I know of nor have we even tested the differences and compatibility

Hosting servicers on the internet use mysql 3 and mysql 4

Ok thanks. I will start over with 4.x

I un-installed MySQL 5.x and installed 4.1. Deleted all the Photopost files an unzipped them again. Ran the install with no errors no problems.

When I enter the username and password to go to the admin screen after the install (adm-index.php it goes to another website www.domain.com

I did enter my domain on the line "URL to PhotoPost main script directory".

What am I missing?

TIA

Looks to me like the domain did not take HMM if it is going to domain.com

Try rerunning install and double check all entries. I know sometimes when PHP is installed as a CGI alot of people have issues cause paths get messed up

No go. Did an new install and it still goes to www.domain.com

Just to confirm the "URL to PhotoPost main script directory" directory would be where the install.php file is?

This looks easy enough but it will not take it.

Any other ideas?

HMM interesting I have done many installs on PHP5. I run it on my site.

You can always go in through phpmyadmin and edit the settings table directly. The first say 30 settings you shall see which ones have www.domain.com just replace with your domain name. Somehow your setup is not allowing the domain name weird indeed

I went in and edit the table and so far so good. Looks like I don't have the correct permissions though as I don't see how to log into the admin panel.

Is this set in the column usergroupid in users? If so what should I enter here?

Is there a user entered in the user's table?

Is there usergroup entries in the usergroups table?

If you want to email me info to look at this go for it

I have the same errors like Danny49.

Why Photopost531 doesn't work with Mysql5?

Other scripts work well with Mysql5, as vBulletin.

OK. ;)

I found this:

http://www.photopost.com/forum/photopost-product-faqs/123261-mysql-5-compatibility.html

My host have just emailed me to say they will be changing to MySQL 5 on October 3rd. This is on a Linux server - does that problem in Chuck's post only apply to Windows servers?

It is more an issue as noted with STRICT MODE